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.

Sign up for GitHub

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

Jump to bottom

SPC m g vs. SPC j #7131

Closed
syl20bnr opened this issue Sep 16, 2016 · 2 comments
Closed

SPC m g vs. SPC j #7131

syl20bnr opened this issue Sep 16, 2016 · 2 comments
Labels
- Mailling list - Conventions Key Bindings stale marked as a stale issue/pr (usually by a bot)

Comments

@syl20bnr
Copy link
Owner

Since we now have a generic approach to jumping to definition, would it makes sense to move SPC m g to SPC j for all generic commands and move very specific commands to SPC m j ?
@syl20bnr syl20bnr mentioned this issue Sep 16, 2016
Closed
@jacktasia
Copy link

FWIW, I also recently added dumb-jump-go-other-window to dumb-jump. I find myself using this more than the traditional dumb-jump-go which uses the same window.

@gilbertw1 gilbertw1 mentioned this issue Oct 20, 2016
Closed
@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
Assignees
No one assigned
Labels
- Mailling list - Conventions Key Bindings stale marked as a stale issue/pr (usually by a bot)
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@jacktasia @syl20bnr