-
Notifications
You must be signed in to change notification settings - Fork 609
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
stage single lines #21
Comments
Can git-apply(1) do single lines? |
To be honest.. i don't know exactly. I took a look at the man page and .. i But: From the "users point of view" i don't care about this. I did not even Best regards, 2011/12/6 Jonas Fonseca <
|
I would love to have this feature as well. I think that the tools that allow this use git-add -e in some form. |
Unstaging single lines from the index is not supported.
Initial support for staging of single lines is now available. [edited] Anyway, please test. It is bound to Ctrl-u by default. Hitting that combo after selecting a line in the stage view should do the trick. |
Use git-apply(1)s --unidiff-zero option to simplify how changes are expressed.
Any preferences regarding the default keybinding? |
ctrl-u is fine for me. I tested it and it works well! Thanks a lot! I just recognized that it does (obviously) not work on new files which are not added to git yet. But i think nobody needs that really. Again, many thanks! |
Good catch, I've added logic to catch those cases (untracked and newly added files) and display a message. |
I just tested it. Well done! |
Ctrl-u was conflicting with page up. Suggested by Heiko.
What might be the reason for the key binding to have stopped working? "1" doesn't do anything now and a quick search looks less than helpful. Edit: Can't quickly find where the key bindings went. |
@Giszmo Try to run Tig with TIGRC_USER=none set to not read any user config file. Also please create a new issue if this persists. |
The feature i miss most in tig is the ability to stage single lines (no hunks) from the stage view.
The text was updated successfully, but these errors were encountered: