[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: command_not_found_handle not run when PATH is empty

From: Chet Ramey
Subject: Re: command_not_found_handle not run when PATH is empty
Date: Thu, 16 Mar 2023 11:20:32 -0400
User-agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:102.0) Gecko/20100101 Thunderbird/102.8.0

On 3/8/23 1:33 PM, Moshe Looks wrote:

Bash Version: 5.1
Patch Level: 16
Release Status: release

When PATH is empty, the command_not_found_handle function is not
called when a command is not found.

I agree that bash should do a path search in the current directory when
PATH is the empty string, so I'll revert the change from 1994 and do that.

When PATH is unset, there's no path search, and no `not finding' the
command -- you just try to exec something in the current directory (or
you don't -- behavior varies among shells).

``The lyf so short, the craft so long to lerne.'' - Chaucer
                 ``Ars longa, vita brevis'' - Hippocrates
Chet Ramey, UTech, CWRU    chet@case.edu    http://tiswww.cwru.edu/~chet/

reply via email to

[Prev in Thread] Current Thread [Next in Thread]