Re: multi-line commands in the history get split when bash is quit

2011-02-07 Thread Dennis Williamson
On Sun, Feb 6, 2011 at 5:14 PM, Slevin McGuigan wrote: > Hi all, > > wow, that was much very much information. Thanks for all the hints and the > discussion. Please apologize when I missed something in one of your > comments... > > My ideas/comments on what some of you wrote > > Michael Witten wro

Re: multi-line commands in the history get split when bash is quit

2011-02-07 Thread Chet Ramey
On 2/5/11 10:49 PM, Michael Witten wrote: > On Sat, Feb 5, 2011 at 20:09, Jon Seymour wrote: >> I guess the point is that in versions of bash that do store the >> timestamp in the .bash_history file > > To clarify, the timestamp is stored whenever HISTTIMEFORMAT has a > non-null value; the bash v

Re: multi-line commands in the history get split when bash is quit

2011-02-07 Thread Slevin McGuigan
Hi all, wow, that was much very much information. Thanks for all the hints and the discussion. Please apologize when I missed something in one of your comments... My ideas/comments on what some of you wrote Michael Witten wrote: .. > When you quit bash, the history is stored very naively in

Re: help's blank lines have four spaces appended

2011-02-07 Thread Chet Ramey
On 2/6/11 2:01 AM, jida...@jidanni.org wrote: > Why add the four spaces? Because all lines are prefixed by four spaces to separate the text from the usage synopsis. -- ``The lyf so short, the craft so long to lerne.'' - Chaucer ``Ars longa, vita brevis'' - Hippocrates Chet Ramey,

Re: help's blank lines have four spaces appended

2011-02-07 Thread Davide Brini
On Sun, 06 Feb 2011 15:01:24 +0800 jida...@jidanni.org wrote: > Why add the four spaces? > $ help read|perl -nwle 's/ $/ \$/ && print' > $ > $ > $ > $ > $ > $ > $ > $ > $ > And? -- D.