Re: strange 'delayed' aliases

2009-12-29 Thread Chet Ramey
On 12/23/09 10:06 AM, Jonathan wrote: > On Dec 23, 7:34 am, Chet Ramey wrote: >> I would think so, since you've inserted a command continuation (the escaped >> newline) into the command via the alias. It's the same as if you had typed >> >> *$* echo \ >> *>* Hello, World! >> >> The only unexpecte

Re: local variable escapes into trap

2009-12-29 Thread Chet Ramey
On 12/29/09 11:55 AM, Akim Demaille wrote: >> I believe that bash is correct. When the `exit' builtin is invoked, and >> the trap is executed, the shell is still executing in the function's >> context. There was no `return', and running exit or a trap does not >> implicitly call it. > > I figur

Re: local variable escapes into trap

2009-12-29 Thread Akim Demaille
Le 29 déc. 09 à 17:35, Chet Ramey a écrit : On 12/29/09 4:19 AM, Akim Demaille wrote: Hi! Hi Chet! On the following script, the local variable $name of bar() hides the global $name when entering the trap. I have observed that with several versions of Bash, including GNU bash, version

Re: command_not_found_handle not called if "command" includes a slash

2009-12-29 Thread Ken Irving
On Tue, Dec 29, 2009 at 12:33:25PM -0900, Ken Irving wrote: > On Mon, Dec 28, 2009 at 03:24:33PM -0900, Ken Irving wrote: > > On Sat, Dec 26, 2009 at 12:54:47PM -0900, Ken Irving wrote: > > > Description: > > > I'm not sure this is a bug, but I notice that the > > > command_not_found_handle

Re: command_not_found_handle not called if "command" includes a slash

2009-12-29 Thread Jan Schampera
Ken Irving schrieb: > That's up to that function to determine, since bash passes control over > to it. It should be able to handle whatever it gets. My use case is > to take things that look like 'object.method' -- which are not likely > to collide with normal executables -- and run them under a

Re: command_not_found_handle not called if "command" includes a slash

2009-12-29 Thread Ken Irving
On Tue, Dec 29, 2009 at 10:40:04PM +0100, Jan Schampera wrote: > Ken Irving schrieb: > > >> This patch is not sufficient, as it leaves the error message, but it > >> does call the hook function in the problem cases: > > I'm just not sure if it makes sense. I mean, if the user requests the

Re: command_not_found_handle not called if "command" includes a slash

2009-12-29 Thread Jan Schampera
Ken Irving schrieb: >> This patch is not sufficient, as it leaves the error message, but it >> does call the hook function in the problem cases: I'm just not sure if it makes sense. I mean, if the user requests the execution of a *specific file*, what should the hook function do if it fai

Re: command_not_found_handle not called if "command" includes a slash

2009-12-29 Thread Ken Irving
On Mon, Dec 28, 2009 at 03:24:33PM -0900, Ken Irving wrote: > On Sat, Dec 26, 2009 at 12:54:47PM -0900, Ken Irving wrote: > > Description: > > I'm not sure this is a bug, but I notice that the > > command_not_found_handle function is not called if the "command" has a > > slash in it. I

Re: local variable escapes into trap

2009-12-29 Thread Chet Ramey
On 12/29/09 4:19 AM, Akim Demaille wrote: > Hi! > > On the following script, the local variable $name of bar() hides the > global $name when entering the trap. I have observed that with several > versions of Bash, including > >> GNU bash, version 4.0.33(1)-release (i486-pc-linux-gnu) I believe

local variable escapes into trap

2009-12-29 Thread Akim Demaille
Hi! On the following script, the local variable $name of bar() hides the global $name when entering the trap. I have observed that with several versions of Bash, including GNU bash, version 4.0.33(1)-release (i486-pc-linux-gnu) FWIW, Zsh and Dash behave as I expected. % cat /tmp/foo.