Hello community,
I would like to state about a small issue I face when I use the `git add
-i` command. I guess it's expressed easily with an example.
**** Start ****
Imagine a situation in which you accidentally made a reasonable amount
of change to your code from your last commit. You would like to put them
in separate commits and hence you go for the `git add -i` command and
choose the `patch` option. You choose the file which you want to update
as patches.
Unfortunately a hunk (of reasonable size) in the file seems to be having
changes that you would like to be in separate commits. So, you would
like to split the hunk into smaller parts but you forgot the correct
option for it and you use `?` option. In most cases you wouldn't see the
help menu completely. Moreover, if the hunk's size is reasonable enough
to take up the whole screen of the terminal you would be seeing the same
screen as before as the help menu is hidden above the hunk and you need
to scroll to see it (only if you knew it's up there in the first place!)
**** End ****
I guess it would be better to display the help menu in a separate flow,
like when the user click the `?` option in the `patch` flow then the
whole screen is cleared and the help menu is displayed in some
appropriate place and after the user has viewed the help menu he could
quit from the help screen (probably by using a key like `q`) to continue
where he left off. I think it would be better because, in general, a
user would want to see the help menu when he uses the `?` option in the
patch flow, not the hunk that gets displayed after it.
Is it a good suggestion or is there anything I missed?
Quote : "You don’t change the world by doing what you’re told.” — Joi Ito
Regards,
Kaartic
