-
Notifications
You must be signed in to change notification settings - Fork 612
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
Default main view / jump to "Staged/Unstaged changes" #1329
Comments
There is already a default binding to jump to HEAD ( |
Right. But ATM there's nothing like the 'HEAD' ref for staged/unstaged, or is it? I see e.g. LINE_STAT_UNSTAGED in the code, but can't figure out anything that could be used as ":goto xyz". Or you mean some hack with that "/^@@"? I don't see how to put anything like that into goto_id()... |
It's not a hack, |
Cool, that works, as does just simply '/Unstaged changes', any specific reason why use ':/...'? Last thing, it seems that I'd need something like #1328 , to do the following :/Unstaged changes ; :enter but it seems that (if I'm looking at the right code) run_prompt_command() / exec_run_request() doesn't have a way to split the command and/or terminate the search string. E.g. something like: :/Unstaged changes/ ; :enter I'm just asking, it's probably just a minor usecase, so if it's not possible, no problem... |
Copy-paste from |
An (via tigrc or bindable command) option to jump to one of the "Staged changes", "Unstaged changes", "HEAD" in the main view would be handy.
The text was updated successfully, but these errors were encountered: