Thread (3 messages) flat view 3 messages, 2 authors, 2016-06-15

Re: [PATCH v2 3/4] completion: cleanup __gitcomp*

From: Jonathan Nieder <hidden>
Date: 2016-06-15 22:52:53

SZEDER Gábor wrote:
On Mon, Jan 30, 2012 at 11:50:04AM -0600, Jonathan Nieder wrote:
quoted
I imagine it would have been enough to say something along the lines of
"The __gitcomp and __gitcomp_nl functions are unnecessarily verbose.
__gitcomp_nl sets IFS to " \t\n" unnecessarily
Yeah, that's unnecessary.  I'm not sure why I did that, perhaps just
blindly followed suit of gitcomp_1(), without realizing that I don't
do any word-splitting in __gitcomp_nl() except when invoking compgen.
quoted
before setting it to "\n"
by mistake.
But that is deliberate, that's why it's called __gitcomp_nl(), see
a31e6262 (completion: optimize refs completion, 2011-10-15), third
paragraph.
Yep, sorry for the ambiguity.  I meant that setting IFS to " \t\n"
(before setting it to "\n") was not done for any serious reason.
The explanation is definitely clearer with "by mistake" dropped.

Thanks,
Jonathan
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help