-
Notifications
You must be signed in to change notification settings - Fork 0
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
auto-spellcheck must be disableable #25
Comments
+1 (on OS X 10.7) -- autocorrect is enabled, but the contextual menu required to disable it is... disabled. |
To disable auto-spellcheck, you need to have focus on a field and you will be able to disable it via the contextual menu (which won't be disabled). |
This autocorrects anything from "minify" ("magnify") to jQuery ("query"), etc. This should be an options in Preferences that is by default set to off. To disable it, I found I had to start typing into a text box, then right-click and disable it. Not something many users are likely to find. |
+1, autocorrect should not be on by default |
1 similar comment
+1, autocorrect should not be on by default |
Please consider making this an option, it's driving me batty! |
+1, should be off by default. Is anyone doing anything with this? I see this issue is over 3 years old and still exists |
another +1 more than a year after my last . . I'd like to add that disabling autocorrect on the field does not stick for me . . autocorrect manages to turn itself back on after a restart. |
i agree that disabling autocorrect doesn't stick. and put "fixup" in the dictionary! On Tue, Mar 31, 2015 at 10:33 AM, kybishop [email protected] wrote:
|
+1 still not disabled by default |
+1, super annoying |
👍 +1 |
As far as I can tell there's no way to disable it permanently. |
Yeah this is just really annoying and hard to understand. |
👍 +1 |
+1 |
2 similar comments
+1 |
+1 |
+1 incredibly annoying |
+1 The worst part is that it will autocorrect the last word after you press the commit button, so you can't even see what madness you have just committed. |
+1 |
1 similar comment
+1 |
+1 How is this still an issue? |
I've just tweeted to @github about this to see if we can get some traction on it: |
+1 |
+1 I can't believe this feature is still on by default for 4 years. It's never once corrected anything useful. It's only corrected the wrong stuff. Today's was "ctor" -> "actor" 😠 |
So the response I got from github bringing this up was
So that solution works for me. Sadly I'm not so sure about the excuse given that NONE of my other apps have this issue. In any case I turned it off at the OS level |
Works for me too! The red underline is still there, so you can still see potential misspellings, they are just not automatically corrected, which is perfect. And I agree that this behavior is not seen in many other apps. The overly-aggressive autocorrect in Apple's own Messages app is not fixed by this setting. |
|
+1 If you tally all of the shame-points in this thread and apply it to the programmer's stats then they are officially encumbered. -10 points to development ability. -10 geek cred. +10 depression. |
+1, cmon github, wtf. |
Thanks @greggman 1 - System preferences |
I love GitHub Desktop, but the autocorrect on by default is super annoying. It is also puzzling that I can disable it via the Edit->Spelling and Grammar menu, but then if I close and re-open GitHub, desktop autocorrect is back on. |
+1 fuuuuu |
+10 really annoying |
+1 |
wip -> rip |
on snow leopard anyway, i keep getting autocorrection of commit messages, which are at best hilarious and at worse just really annoying.
The text was updated successfully, but these errors were encountered: