Matthieu Moy wrote:
> That would mean executing SOMETEXTTOEXECUTE each time the config file is
> read. This raises two issues:
>
> * A security issue, as SOMETEXTTOEXECUTE could also be something
> dangerous. It would not be much worse than the current situation (if
> your config file is not t
Matthieu Moy writes:
> What I suggest instead is to edit/track/share template configuration
> files like
>
> ~/.gitconfig.in
> email = me@HOSTNAME@
>
> and then script something like sed -e "s/@HOSTNAME@/$(hostname)/" <
> ~/.gitconfig.in > ~/.gitconfig.
>
> You may also use the include.path func
Morgan McClure writes:
> I propose using something reminiscent of bash syntax, either:
> value = $(SOMETEXTTOEXECUTE)
>
> or
>
> value = `SOMETEXTTOEXECUTE`
That would mean executing SOMETEXTTOEXECUTE each time the config file is
read. This raises two issues:
* A security issue, as SOMETEXTTOEX
I sync all my dot files (including .gitconfig) among several machines
and it's currently not possible to put conditional logic in many
fields (any that aren't considered strings to be executed as shell
commands ie aliases, editor, etc).
My specific use case is the email address. Normally I want my
4 matches
Mail list logo
