From: Junio C Hamano Date: Tue, 14 May 2013 18:47:16 GMT Subject: Re: [PATCH] diffcore-pickaxe doc: document -S and -G properly Message-ID: <7v8v3hjt57.fsf@alter.siamese.dyndns.org> In-Reply-To: Ramkumar Ramachandra writes: > Junio C Hamano wrote: >> Any time you say "This means that", "More precisely", etc. please >> check if you can rewrite it to lose everything before them (i.e. a >> vague sentence that needs to be clarified may not have to be there >> at all). > > Right. I thought both are necessary in this case: the first sentence > gives easy information to a first-timer. For someone who has played > with it a bit, and wants to know more: the second line. > >>> ++ >>> +It is often useful when you're looking for an exact string (like a >>> +function prototype), and want to know the history of that string since >>> +it first came into being. >> >> I think you should remind that the most useful case (and indeed the >> intended one) is for "an exact string" to be a multi-line "block of >> text". People often get a (wrong) impression from the word "string" >> that it is meant to be used with a single-liner. > > Yes, I've been meaning to discuss that. I've been having some trouble > with multi-line strings: zsh doesn't insert a TAB in the next line. > The workaround I have is to write a shell script and execute that. > How do you do it? I do not use zsh but with bash+readline the old tradition lnext can be used (see "stty -a" output and it typically is set to ^V), i.e. \C-v followed by \C-i should give you a literal HT.