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
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
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
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
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
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 can't find anywhere in the bash source producing the
> "No such f
On 12/27/09 4:30 AM, Jan Schampera wrote:
> From what I can see, the hook function is only triggered when a PATH
> search returns no result. A given relative or absolute filename doesn't
> trigger a PATH search.
Quite true.
--
``The lyf so short, the craft so long to lerne.'' - Chaucer
Ken Irving schrieb:
> 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 can't find anywhere in the bash source producing the
> "No such file ..." error message, so I guess thi
Configuration Information [Automatically generated, do not change]:
Machine: i486
OS: linux-gnu
Compiler: gcc
Compilation CFLAGS: -DPROGRAM='bash' -DCONF_HOSTTYPE='i486'
-DCONF_OSTYPE='linux-gnu' -DCONF_MACHTYPE='i486-pc-linux-gnu'
-DCONF_VENDOR='pc' -DLOCALEDIR='/usr/share/locale' -DPACKAGE='ba
