Re: Add configuration options for some commonly used command-line options
- From
Brandon McCaig <bamccaig@gmail.com>
- Date
- Mar 31, 2017, 19:44 UTC
- Message-ID
- <20170331194414.GA22434@test-chamber-1.castopulence.org>
- In-Reply-To
- <20170320181801.fubiyufrsyenru4b@sigill.intra.peff.net>
On Mon, Mar 20, 2017 at 02:18:01PM -0400, Jeff King wrote:
> I think we've had similar proposals in the form of an > environment variable like "GIT_PLUMBING" (and your "command", > which I do like syntactically, would probably just end up > setting such an environment variable anyway).
For reference, Mercurial has long had HGPLAIN with a similar purpose. See `hg help scripting'. I think that this is a generally good idea to adopt. Albeit, I think that Mercurial considers its command line a scriptable API, and HGPLAIN skips over any customization of output. That may not be the exact intention of this, but something related nevertheless.
Instead of a subcommand I think that a command line --option would make better sense. It would only even save a few characters in *nix shells where the variable can be inlined, but could be more practical for MS Windows users that would need separate commands to manage the variable.
Regards,
--
Brandon McCaig <bamccaig@gmail.com> <bambams@castopulence.org>
Castopulence Software <https://www.castopulence.org/>
Blog <http://www.bambams.ca/>
perl -E '$_=q{V zrna gur orfg jvgu jung V fnl. }.
q{Vg qbrfa'\''g nyjnlf fbhaq gung jnl.};
tr/A-Ma-mN-Zn-z/N-Zn-zA-Ma-m/;say'