Re: Quotes problem ?

2007-01-11 Thread Markos
Hello , Eric: Sorry, I forgot to mention the platform. It is a Sun 250 with Solaris 8.Thank you anyway. Paul: It worked with the changes you told me. Thank you very much.I still have a question anyway: You said that line cd $path should be better with quotes to avoid problems with dir names

bash-3.2 HISTTIMEFORMAT imported from environment does not cause timestamp saving

2007-01-11 Thread Ark Submedes
Enclosed is a patch to treat HISTTIMEFORMAT just like other HISTCONTROL and HISTIGNORE when imported. Also changes to the documentation are proposed to avoid the confusion I experienced. bash-3.2-histtime-patch Description: Binary data ___ Bug-bash

Re: bash-3.2 HISTTIMEFORMAT imported from environment does not cause timestamp saving

2007-01-11 Thread Ark Submedes
On 1/11/07, Ark Submedes [EMAIL PROTECTED] wrote: On 1/11/07, Ark Submedes [EMAIL PROTECTED] wrote: Enclosed is a patch to treat HISTTIMEFORMAT just like other HISTCONTROL and HISTIGNORE when imported. Also changes to the documentation are proposed to avoid the confusion I experienced. I

Re: Quotes problem ?

2007-01-11 Thread Paul Jarc
Markos [EMAIL PROTECTED] wrote: You said that line cd $path should be better with quotes to avoid problems with dir names containing spaces, so did you mean this? cd $path Yes. paul ___ Bug-bash mailing list Bug-bash@gnu.org

Re: bash-3.2 HISTTIMEFORMAT imported from environment does not cause timestamp saving

2007-01-11 Thread Ark Submedes
On 1/11/07, Ark Submedes [EMAIL PROTECTED] wrote: Enclosed is a patch to treat HISTTIMEFORMAT just like other HISTCONTROL and HISTIGNORE when imported. Also changes to the documentation are proposed to avoid the confusion I experienced. I renamed the patch with .txt so gmail sees it as