Roman Rakus wrote:
You are badly using features of bash. Write a script which will do
things for you, or use any other language/shell.
---
Why?
Please, accept this response as a suggestion.
---
Seems to be a bit provincial.
command_not_found_handle is designed to do other things than you
On 8/20/13 11:02 AM, Greg Wooledge wrote:
> On Tue, Aug 20, 2013 at 05:48:12PM +0300, Aharon Robbins wrote:
>> In article you write:
>>> 1) PATH is used by the kernel (exec family) to determine how commands are
>>> executed. The way PATH is used by the kernel is not likely to change.
>>> Havi
On Tue, Aug 20, 2013 at 05:48:12PM +0300, Aharon Robbins wrote:
> In article you write:
> >1) PATH is used by the kernel (exec family) to determine how commands are
> > executed. The way PATH is used by the kernel is not likely to change.
> > Having the shell treat it differently would lead t
You are badly using features of bash. Write a script which will do
things for you, or use any other language/shell.
Please, accept this response as a suggestion.
command_not_found_handle is designed to do other things than you are
expecting.
RR
On 08/19/2013 10:29 PM, Andreas Gregor Frank
On Mon, Aug 19, 2013 at 08:02:39PM -0700, Linda Walsh wrote:
> Yes, I see what you mean. I guess I'm not real certain
> as to why, if "CDPATH=~/Documents", and I type "cd Pictures/family"
> and end up in ~/Documents/Pictures/family, then PATH shouldn't work
> the same way.
There are several
