Re: let's establish BASH_MINIMUM_TIME_BETWEEN_INTERACTIVE_COMMAND

2014-01-29 Thread Aharon Robbins
In article , wrote: >Gentlemen, I have once again come up with a million dollar idea for bash, >revolutionizing the shell world. > >As we all know, nobody in their right mind could type more than one >command per second into bash when in interactive mode. > >So let's establish BASH_MINIMUM_TIME_B

Re: let's establish BASH_MINIMUM_TIME_BETWEEN_INTERACTIVE_COMMAND

2014-01-29 Thread Chris Down
On 2014-01-29 21:03:12 -0700, Bob Proulx wrote: > Eduardo A. Bustamante López wrote: > > Chris Down wrote: > > > Well, you can do this with PROMPT_COMMAND='sleep 1'. I don't see the > > > need for another internal variable to do this. > > > > How would that work to avoid filling the prompt with the

Re: let's establish BASH_MINIMUM_TIME_BETWEEN_INTERACTIVE_COMMAND

2014-01-29 Thread Eduardo A . Bustamante López
On Wed, Jan 29, 2014 at 09:03:12PM -0700, Bob Proulx wrote: > Eduardo A. Bustamante López wrote: > > Chris Down wrote: > > > Well, you can do this with PROMPT_COMMAND='sleep 1'. I don't see the > > > need for another internal variable to do this. > > > > How would that work to avoid filling the pro

Re: let's establish BASH_MINIMUM_TIME_BETWEEN_INTERACTIVE_COMMAND

2014-01-29 Thread Bob Proulx
Eduardo A. Bustamante López wrote: > Chris Down wrote: > > Well, you can do this with PROMPT_COMMAND='sleep 1'. I don't see the > > need for another internal variable to do this. > > How would that work to avoid filling the prompt with the paste buffer > when I fat finger and paste a whole email to

Re: let's establish BASH_MINIMUM_TIME_BETWEEN_INTERACTIVE_COMMAND

2014-01-29 Thread Eduardo A . Bustamante López
On Thu, Jan 30, 2014 at 10:44:30AM +0800, Chris Down wrote: > On 2014-01-30 09:18:19 +0800, jida...@jidanni.org wrote: > > So let's establish BASH_MINIMUM_TIME_BETWEEN_INTERACTIVE_COMMAND=1.0 > > Well, you can do this with PROMPT_COMMAND='sleep 1'. I don't see the > need for another internal varia

Re: let's establish BASH_MINIMUM_TIME_BETWEEN_INTERACTIVE_COMMAND

2014-01-29 Thread Chris Down
On 2014-01-30 09:18:19 +0800, jida...@jidanni.org wrote: > So let's establish BASH_MINIMUM_TIME_BETWEEN_INTERACTIVE_COMMAND=1.0 Well, you can do this with PROMPT_COMMAND='sleep 1'. I don't see the need for another internal variable to do this. pgpTYMNSu6HsQ.pgp Description: PGP signature

let's establish BASH_MINIMUM_TIME_BETWEEN_INTERACTIVE_COMMAND

2014-01-29 Thread jidanni
Gentlemen, I have once again come up with a million dollar idea for bash, revolutionizing the shell world. As we all know, nobody in their right mind could type more than one command per second into bash when in interactive mode. So let's establish BASH_MINIMUM_TIME_BETWEEN_INTERACTIVE_COMMAND=1.

Re: bug in 4.2

2014-01-29 Thread Chet Ramey
On 1/29/14 6:53 AM, Csaba Toth wrote: > Hi, > > If you set PROMPT_DIRTRIM, in some cases strange output displayed in the > prompt. I found an issue inside the trim_pathname() function, that uses > memcpy() to copy head and tail together. That should not be used if the > memory is overlapped and me

bug in 4.2

2014-01-29 Thread Csaba Toth
Hi, If you set PROMPT_DIRTRIM, in some cases strange output displayed in the prompt. I found an issue inside the trim_pathname() function, that uses memcpy() to copy head and tail together. That should not be used if the memory is overlapped and memmove() shall be used instead. Please find m