Skip to content
This repository has been archived by the owner on Mar 3, 2023. It is now read-only.

command-left and command-right feel slow I use the #1253

Closed
atom-bot opened this issue Dec 6, 2013 · 7 comments · Fixed by #1329
Closed

command-left and command-right feel slow I use the #1253

atom-bot opened this issue Dec 6, 2013 · 7 comments · Fixed by #1329
Assignees

Comments

@atom-bot
Copy link

atom-bot commented Dec 6, 2013

command-left and command-right feel slow

I use them a lot to move between words and they make the "Movement" menu bar flicker and feel like they take much longer than I would expect them to on OS X.

User: @eric
Atom Version: 0.41.0
User Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_9_0) AppleWebKit/537.36 (KHTML, like Gecko) Atom/0.42.0 Safari/537.36

@ghost ghost assigned probablycorey Dec 6, 2013
@probablycorey
Copy link

This pull Removes the movement menu command

@probablycorey
Copy link

I also think you meant alt-left and alt-right (not cmd-left and cmd-right). But you're right, they do feel slow. I think it is because it is treating spaces as word boundaries and the default OS X behavior doesn't do this. Once that is fixed it should 'feel' much faster.

@benogle
Copy link
Contributor

benogle commented Dec 17, 2013

The word boundary thing is deliberate. There is another word boundary command you can use instead of the default if you want: editor:move-to-beginning-of-word and editor:move-to-beginning-of-next-word. I dont want to change the current word boundary behavior.

@nathansobo
Copy link
Contributor

Someday in the distant future (like not any time soon), a nice interface for configuring word boundary behavior could be a nice-to-have.

@eric
Copy link

eric commented Dec 17, 2013

Apparently I was using a different key than I thought I was. You're right it is alt-left and alt-right.

@probablycorey
Copy link

@benogle do you think the behavior of alt-left and alt-right should match to default behavior of OS X, Sublime and Textmate? Or should it behave as it does now?

@lock
Copy link

lock bot commented Jan 27, 2019

This issue has been automatically locked since there has not been any recent activity after it was closed. If you can still reproduce this issue in Safe Mode then please open a new issue and fill out the entire issue template to ensure that we have enough information to address your issue. Thanks!

@lock lock bot locked as resolved and limited conversation to collaborators Jan 27, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

5 participants