16

Command + C does not always work on first try on any of my four Macs. I often highlight text, press Command + C, head to another window, press Command + V only to find that the original text did not copy.

I recently installed a fresh copy of macOS High Sierra and I continue to run into this issue, particularly in RStudio.* The issue never occurs on my PCs.

Do others have this issue? How can I resolve this?

*I use bettersnaptool and enable three finger dragging, but the issue still appears when I disable them.

RTS
  • 261

4 Answers4

9

I think it's possible for Apple's Continuity Universal Clipboard feature to cause something like this, depending on the quality of the signal connection with any nearby iOS devices.

Perhaps try turning off "Allow Handoff between this Mac and your iCloud devices" in System Preferences > General and see if that helps.

Ashley
  • 4,187
3

I've found a cause of the same problem. An app may use it as a hotkey. In my case, I use a dictionary app (Eudic), which will read the clipboard if cmd+c is pressed twice.

An easy way to check whether it is caused by an app is to activate the Guest account, which usually has few autostart apps, and to check whether the problem still exists.

S Yi
  • 31
0

I've noticed this for a long time too and I thought it was because that my laptop was old, but apparently not.

I found that if I slow down a little bit, like hold the command key for 1 about 1 second, and then hit C, it would work.

However, I don't know the cause behind or a real fix.

-2

This issue is real and I think every mac user experience it on a weekly basis, but likely people continue to doubt themselves over if they actually command c or not properly.

The fix. If you are using Karabiner like real hacker should:

Just add this to your karabiner complex configurations:

[
    {
        "from": {
            "key_code": "c",
            "modifiers": {
                "mandatory": [
                    "left_command"
                ]
            }
        },
        "to": [
            {
                "key_code": "c",
                "modifiers": [
                    "left_command"
                ]
            },
            {
                "key_code": "c",
                "modifiers": [
                    "left_command"
                ]
            },
            {
                "key_code": "c",
                "modifiers": [
                    "left_command"
                ]
            }
        ],
        "type": "basic"
    }
]

Now that should make the copy flash a few times in the menu.

You can increase or decrease as much as you want. Personally I have a few more.

mjs
  • 258
  • 1
    Does this actually „fix“ the problem, or rather spare the user to press cmd-c several times to compensate for it? – nohillside May 16 '21 at 11:55
  • I am not sure, I have not really put it into action to notice it yet. However, the user might not be aware the command-c was picked up, hence the reason why it is repeated to ensure it is. Often times, the command-c is done. A switch to another window, some clicking, editing, and then command-v not to be seen. If the user knew command-c was not picked up, no it is not required as as he can reinvoke it (which is not the same), this just invokes it a bunch of times to make sure the os picks it up. – mjs May 16 '21 at 15:37
  • 1
    Being an early adopter of Mac OS X, I did never experience this in all the years, not even a single time. And if this happened to a lot of users regulary, it would be discussed widely everywhere. But it‘s not, so your introduction is at least misleading. If the problem is real, only a tiny minority of users can be affected, and it‘s neccessary to find out some configuration as common cause (like the other answers did) instead of trying a hack as workaround … – Philippos May 16 '21 at 16:20
  • Well, the problem is most people think it is due to them. I noticed it within 1 week of being exposed to others that it is very real. It happens to all. They also confirmed it. That it is not reported is not relevant. I am allowed to state whatever I want, and it is reported quite a lot as well. I simply always figured maybe i was not pressing hard enough. – mjs May 17 '21 at 13:59
  • Also, it could be due to some setting or handsoff. Perhaps you are not using that. Pboard? Keyboard maestro, perhaps. Who knows. It does happen though. It is kind of difficult to pin down though cause it does not happen all the time. – mjs May 17 '21 at 14:01