Holding down a key to get accent choices not working despite Terminal command set to "true"

Hi,


I use High Sierra 10.13.6 on a 2011 MBP.


I've come across this terminal command to enable accent choices:

defaults write NSGlobalDomain ApplePressAndHoldEnabled -bool true


I restart the MBP and type defaults read NSGlobalDomain ApplePressAndHoldEnabled and value "1" is displayed and I have access to accents choices (OK).


But after a while it no longer works. The keys are repeating instead of providing me with accents choices. On Terminal "read" command, the value is still "1" though. I've also set the key repeat to 0 in keyboard preferences menu, but that doesn't solve the issue.


How can I permanently keep the option working?


Thank you.

MacBook Pro, macOS High Sierra (10.13.6)

Posted on Sep 9, 2018 3:04 AM

Reply
Question marked as Top-ranking reply

Posted on Sep 23, 2018 12:54 PM

dialabrain's point was that the preference should not exist for normal behavior.

Delete the preference setting and try it out. Don't recreate the thing that is not needed.


If it goes back to not working, then something is interfering with it. Whatever it is might be revealed in an Etrecheck report, but it won't be glaring warning like, "this app is preventing use of ApplePressAndHold." It will just be something you have installed that probably serves no useful purpose, but is somehow related to the keyboard entry.


Early on, there were problems with this feature. One solution was to just add another latin-based language (French, Spanish, etc) to the list of input sources. You don't have to use it, just put it in the list in Keyboard System Prefs > Input Sources. Note that when you add an input source, it will automatically check the box to show it in the menu bar. You can disable that setting so you don't have to see it. I don't know if you even have to keep it in the list. Possibly adding the language and removing could trigger the fix.

Similar questions

13 replies
Question marked as Top-ranking reply

Sep 23, 2018 12:54 PM in response to yoms

dialabrain's point was that the preference should not exist for normal behavior.

Delete the preference setting and try it out. Don't recreate the thing that is not needed.


If it goes back to not working, then something is interfering with it. Whatever it is might be revealed in an Etrecheck report, but it won't be glaring warning like, "this app is preventing use of ApplePressAndHold." It will just be something you have installed that probably serves no useful purpose, but is somehow related to the keyboard entry.


Early on, there were problems with this feature. One solution was to just add another latin-based language (French, Spanish, etc) to the list of input sources. You don't have to use it, just put it in the list in Keyboard System Prefs > Input Sources. Note that when you add an input source, it will automatically check the box to show it in the menu bar. You can disable that setting so you don't have to see it. I don't know if you even have to keep it in the list. Possibly adding the language and removing could trigger the fix.

Sep 9, 2018 3:14 AM in response to yoms

How long is “after a while”? If it is a short and predictable period of time you can do two simple tests: 1) use a different account and see if the problem also occurs; 2) boot in Safe Mode and see if the problem occurs.

Of course this not practical if the problem manifests after several hours.


When you detect it has started happening, try logging out and back in. Does it fix it? I am guessing it will.


In order for us to know more and hopefully detect what may be causing it, please run Etrecheck and post its report here.

Sep 9, 2018 4:17 AM in response to Luis Sequeira1

Thanks for replying.


Unfortunately, only logging out then in does not fix it. I've just restarted my mbp.

In Terminal:

defaults read NSGlobalDomain ApplePressAndHoldEnabled

1

So it's enabled but still doesn't work. I have to re-enter the "write" command again, then log out/in.


As for "after a while", it's impossible for me to tell because I'm not writing foreign characters every day.

Sep 9, 2018 6:14 AM in response to dialabrain

It is perfectly normal to get a “does not exist” reply to the defaults read command. That just mean there is no value set for this property, either because it has not been set or because it was deleted ( with a defaults delete command).


I believe that actually was my situation before I started testing for this thread. But as I said, the setting does work for me.

Sep 9, 2018 8:50 AM in response to yoms

Thanks to both of you for your aswers.


So I did all these steps again:

1) Delete (OK)

2) Read (error, but it's normal since property was deleted)

3) Write enabled = true (OK)

4) Read (OK) => value is 1 (i.e. true)

5) Restart computer

6) I have the accents on key hold again (OK)


But, these steps have always worked fine. My problem is that it no longer works after some time although the read command still results in "1" (enabled) 😕. When I face the issue, restarting or log out/in is not enough. I systematically have to go through those steps. And the cycle repeats itself (it works for some time... until it no longer does)

This thread has been closed by the system or the community team. You may vote for any posts you find helpful, or search the Community for additional answers.

Holding down a key to get accent choices not working despite Terminal command set to "true"

Welcome to Apple Support Community
A forum where Apple customers help each other with their products. Get started with your Apple Account.