Ctrl+E started to be a shortcut of `quoting code`

When I wrote GitHub Issues, Pull Request Descriptions, and comments, I used Emacs-like keyboard shortcuts Ctrl+A, Ctrl+E, Ctrl+F, … supported by the Chrome browser by native.

But recently, GitHub’s browser Markdown editor started to interrupt my Ctrl+E, and to make it quoting code, not “Go to the end of the line”.

Can I disable this new shortcut? This is really irritating for me…

33 Likes

Completely agree–ctrl+e is very widely used as a shortcut to move to the end of a line across many applications and operating systems. Ever since the Github text editor started catching it (relatively recently I think?) I’ve been constantly quoting words with backticks by accident. What makes it even more frustrating is that undo doesn’t actually undo it because it’s not a keystroke but something inserted by javascript!

4 Likes

I am also annoyed by this new behavior. I don’t care about any custom shortcuts in the editor, so an option to disable them altogether would be okay by me.

1 Like

Is there plan to revert this shortcut, or that it will stay permanent? This is indeed very annoying during code review. Perhaps something like Ctrl+Shift+E can be considered. The current Ctrl shortcuts contradict most browser editors.

1 Like

+1

This shortcut appeared to go live for me today and it’s a pretty jarring interruption to my typing muscle memory.

control+` might more sense. Don’t see how “e” is related to code block or code highlighting.

1 Like

Gah, this is a really common shortcut that works in browsers, on the command line, etc. It’s not a feature. Please let us turn it off.

1 Like

I just noticed this start to happen on my account as well, I think this breaks a lot of text editing IDE / library conventions. Even this text editor I’m writing this comment in doesn’t quote when using Ctrl + E

1 Like

Also want to voice my support here, extremely frequently used shortcut for me.

2 Likes

I’m on a Mac and using Safari (15.0). The markdown editor is supposed to treat command + E as a shortcut for “code” (back tick enclosure). Currently, both command + E and ctrl + E are triggering code quoting. Only command + E should do this. As others have noted, ctrl + E is an important native command to navigate to the end of the line. Replacing it negatively impacts keyboard users and could also be a significant accessibility concern.

Noticing the number of new postings here after five months, it seems like something must have changed recently.

1 Like

+1 this change appears to have just gone into effect for me as well, and it’s extremely disruptive. I think it should either be bound to Command instead of Ctrl, or at least allow the shortcut to be disabled altogether.

1 Like

gaaah. +1 This is brutal and just came into effect for me today. Please, please turn it off. :pray: I’ve just become aware I use ctrl-E to jump to the end of the line about 50 times in any given PR-review :smile:

1 Like

+1 The override of ctrl-e for code formatting in comments also just came into effect for me. This is really disruptive :frowning: (but hey, it works properly in this text box! :laughing:)

2 Likes

Same here. i use control+e all the time (probably dates back to vt101 terminals!) and this new behaviour (starting today) is super disruptive. I think there might be an OSX confusion here, control is different from command. looks like this new shortcut hijacks control when it should be on command-E. BTW as others noted, this message box on github.community behaves perfectly (eg only command triggers the code formatting). please have the same behaviour on GitHub comments. thanks.

Hey all :wave:

I noticed the activity in this thread, and have reached out to the team that worked on updating our shortcuts on github.com:

Waiting to hear from them, and will update on the best next steps to make sure that your voices are heard, and by the appropriate folks for consideration.

Thanks so much for the feedback so far!

1 Like

All right, got some speedy assist from our dev teams, and I had some confusion here.

We will be adding a check for Mac users with this new shortcut behavior pushed earlier today. In addition we’ll assess whether we should reconsider the cmd+e shortcut in issues/ comments. The former should be seen soon :tm: and the latter is in consideration phases.

Thanks again for your patience and apologies for the frustration for those with that muscle memory getting tossed about.

4 Likes

Thanks for addressing this. In additon to Ctrl-E, I also rely on Ctrl-K to clear-to-end-of-line. Among the other changes, turning that into a link shortcut is infuriating.

3 Likes

I hear you @statico and I should further clarify: we’ll be adjusting the cmd versus ctrl behavior for Mac users, which should also address your ctrl+k woes.

6 Likes

Glorious. Thank you very much!

1 Like

Wow, yeah the new Ctrl-E shortcut override is horrifyingly bad/painful. It feels about the same as if my car’s right-turn signal were suddenly hardwired to slam on the brakes - incredibly jarring, and I’d never want to even try to get used to it - would rather buy a new car at that point. Glad to hear that it’s going to be fixed soon.

1 Like

I don’t understand the value proposition of mapping ctrl-e, two key presses, to adding backticks, which would also be two key presses. If this is about adding backticks around text that is selected, why not bind it to the back-tick key when text is highlighted, which is more intuitive?

4 Likes