Skip to content
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

Dired motions gg and G #4104

Closed
darkfeline opened this issue Dec 8, 2015 · 5 comments
Closed

Dired motions gg and G #4104

darkfeline opened this issue Dec 8, 2015 · 5 comments
Labels
- Bug tracker - stale marked as a stale issue/pr (usually by a bot) To be reproduced

Comments

@darkfeline
Copy link
Contributor

In Dired, the Vim motions gg and G are overridden with Dired commands.

This is problematic as 1. Dired is in Normal state and 2. a user who instinctively uses those motions is frustrated by unexpected behavior.

@mahinshaw
Copy link
Contributor

The afoermentioned motions work for me. @darkfeline is this still an issue for you?

@darkfeline
Copy link
Contributor Author

Still experiencing it, although I've gotten used to using M-<, M->. I've stopped using Spacemacs as of late, so getting a reproduction and debug is not high on my list. If no one else can reproduce, maybe we should close this.

@ajrouvoet
Copy link

I have the same problem on develop. "G" motion open a ChGrp helm menu. "gg" seems to do nothing.

@darkfeline
Copy link
Contributor Author

That sounds like the behavior I was experiencing. I suspect "gg" is running the default dired refresh command (which is bound to "g") twice.

@github-actions
Copy link

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Please let us know if this issue is still valid!

@github-actions github-actions bot added the stale marked as a stale issue/pr (usually by a bot) label Feb 29, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
- Bug tracker - stale marked as a stale issue/pr (usually by a bot) To be reproduced
Projects
None yet
Development

No branches or pull requests

4 participants