Pesquisar no site de suporte

Evite golpes de suporte. Nunca pedimos que você ligue ou envie uma mensagem de texto para um número de telefone, ou compartilhe informações pessoais. Denuncie atividades suspeitas usando a opção “Denunciar abuso”.

Learn More

Can't enter minus sign in Google Docs spreadsheet

  • 4 respostas
  • 36 têm este problema
  • 218 visualizações
  • Última resposta de Beanfield

more options

In a Google Docs spreadsheet, I can't enter a minus sign (hyphen) in a cell until I've typed in a number, then I can go back and enter the minus sign. I think this started with Firefox 15.0, and I have replicated it on another Mac, both running OS 10.7.4.

In a Google Docs spreadsheet, I can't enter a minus sign (hyphen) in a cell until I've typed in a number, then I can go back and enter the minus sign. I think this started with Firefox 15.0, and I have replicated it on another Mac, both running OS 10.7.4.

Solução escolhida

I have this issue too. When I enter a negative number I start with = before I enter the minus sign!

Ler esta resposta 👍 3

Todas as respostas (4)

more options

Solução escolhida

I have this issue too. When I enter a negative number I start with = before I enter the minus sign!

more options

Thanks graendal -- an imperfect solution to a problem that only started recently. Still, better than the routine I was going through.

more options

This is not just Mozilla problem, but same for all browsers. You can use the minus key on the numpad of your keyboard, but not the dash key. Unfortunately, if you are not using full-size keyboard, you can't easily access the numpad minus.

I have been using this method myself on my laptop: hit any number/letter, then quickly hit backspace and then dash. This for some reason lets the dash key to enter as a minus sign.

Graendal's way is much better, but still, I don't understand why Google decided not to allow the dash sign to be used as a minus sign.

more options

tigerleap wrote: This is not just Mozilla problem, but same for all browsers.

Well, it's not an issue on Google's Chrome browser! But it is on Firefox and Safari. Coincidence? I think not.