On Fri, Nov 19, 2010 at 20:49, Jonathan Nieder <jrnieder@xxxxxxxxx> wrote:
> [resending to list; sorry for the noise]
No problem.
>
> Bert Wesarg wrote:
>
>> Could we settle on a name space for such variables? GIT_EDITOR_* makes
>> it obvious that it is for the editor started from git.
>
> Sounds good to me.
>
> If the choice of variables ends up looking especially good, maybe
> we can pass it along to the Portland group and call it xdg-editor for
> use by other apps, too. :)
>
Interesting idea.
There is one more thing to discuss before starting collecting the
variables. Has each flag its own env-variable, or do we put flags into
one variable named GIT_EDITOR_FLAGS? They could be space or comma
separated.
The second option sounds a little bit more future prove to me.
For non-flag arguments, there is the obvious LINENUMBER. But how do we
pass columns or even a character range to the editor. They would be
good for compiler output. Sure its out of score for git, but a little
future-thinking will not hurt. We could add it to the LINENUMBER with
a syntax like:
<line>[:<column-start[-<column-end>]]
Bert
--
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html