Kirill Likhodedov <kirill.likhode...@jetbrains.com> writes: > My motivation is the following: I'm improving the Git client > inside of IntelliJ IDEA IDE and I would like to provide only the > plain commit message text to the user (any hints can be shown > separately, not inside the editor).
Who is running "git commit --amend" and "git rebase -i" in the workflow of a user of your tool? Is it the end user who types these commands to the shell command prompt, or does your tool formulate the command line and does an equivalent of system(3) to run it? I am assuming that the answer is the latter in my response. > If there is no way to do it now, do you think it makes sense to > provide a configuration variable for this, e.g. to introduce more > advice.* config variables in addition to existing ones? Not at all interested, as that would mean your tool will tell its users to set such a configuration variable and their interactive use of Git outside your tool will behave differently from other people who use vanilla Git, and they will complain to us. But I do not think adding a new command line option that only is passed by a tool like yours when it runs "git rebase -i" via system(3) equivalent would introduce such an issue, so that may be workable. But stepping back a bit, as you said in the parentheses, your tool would need to grab these "hints" from Git, instead of having a separate hardcoded hints that will go stale while the underlying Git command improves, to be able to show them "separately". Which means to me that you would need to get the output Git would normally show to the end user and do your own splitting and parsing anyway. Which in turn would mean that a configuration or a command line option to squelch these, which would rob your tool the ability to read what Git would have told to your users, would be a bad idea and not a useful addition to the overall system. So...
