Re: tab expansion of $HOME/ to \$HOME/

2014-01-15 Thread Diggory Hardy
Sorry Chet, for some reason I didn't see your reply until after I'd replied to Chris. On Wednesday 15 January 2014 07:50:09 Chet Ramey wrote: > On 1/15/14 5:07 AM, Diggory Hardy wrote: > > Thanks Chris. > > > > So the way I read it is that many people

Re: tab expansion of $HOME/ to \$HOME/

2014-01-15 Thread Diggory Hardy
On Tuesday 14 January 2014 10:57:46 Chris Down wrote: > On 2014-01-13 20:42:39 -0500, Chet Ramey wrote: > > You can set the `direxpand' option and probably get around most of this, > > with the change that variables will be expanded upon completion, as in > > bash-4.1. > > Er, somehow I missed thi

Re: tab expansion of $HOME/ to \$HOME/

2014-01-15 Thread Diggory Hardy
7:03 Chris Down wrote: > On 2014-01-13 11:00:09 +0100, Diggory Hardy wrote: > > If I enter > > > > $ ls $HOME/Do > > > > and press the Tab key, bash expands to > > > > $ ls \$HOME/Documents > > See this older thread[0]. > > If you bash &g

tab expansion of $HOME/ to \$HOME/

2014-01-13 Thread Diggory Hardy
remove the escaping back-slash. What's going on? I should state that the only reason I noticed this is that I don't have a ~ on my current keyboard, but still this seems like a valid bug report to me. Best regards, Diggory Hardy signature.asc Description: This is a digitally signed message part.

Re: Recursively calling a bash script goes undetected and eats all system memory

2010-12-10 Thread Diggory Hardy
On Friday 10 December 2010 Greg Wooledge wrote: > On Fri, Dec 10, 2010 at 03:23:46PM +0100, Diggory Hardy wrote: > > What if bash were only to allow scripts to call themselves with exec? > > You can't prevent programmers from writing horrible code. At some point, > it isn&

Re: Recursively calling a bash script goes undetected and eats all system memory

2010-12-10 Thread Diggory Hardy
On Friday 10 December 2010 Pierre Gaston wrote: > On Fri, Dec 10, 2010 at 11:25 AM, Diggory Hardy > wrote: > > On Thursday 09 December 2010 Pierre Gaston wrote: > >> On Wed, Dec 8, 2010 at 11:15 AM, Diggory Hardy > >> wrote: > >> > Hello, > >&g

Re: Recursively calling a bash script goes undetected and eats all system memory

2010-12-10 Thread Diggory Hardy
On Thursday 09 December 2010 Pierre Gaston wrote: > On Wed, Dec 8, 2010 at 11:15 AM, Diggory Hardy > wrote: > > Hello, > > > > With a simple script such as that below, bash can enter an infinite loop of > > eating memory until the system is rendered unusable

Recursively calling a bash script goes undetected and eats all system memory

2010-12-09 Thread Diggory Hardy
Hello, With a simple script such as that below, bash can enter an infinite loop of eating memory until the system is rendered unusable: #!/bin/bash PATH=~ infinitely-recurse Save this as infinitely-recurse in your home directory and run - and make sure you kill it pretty quick. OK, so an obvio