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
On 12/24/09 3:35 PM, Krzysztof Oledzki wrote:
> Bash Version: 4.0
> Patch Level: 35
> Release Status: release
>
> Description:
> set -e (errexit) does not work in subfunctions when
> caller checks for a return result
>
> Repeat-By:
> ---cut here ---
> #!/bin/sh
>
> f() {
> set
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