[Top][All Lists]

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

Re: bash 4.2 breaks source finding libs in lib/filename...

From: Linda Walsh
Subject: Re: bash 4.2 breaks source finding libs in lib/filename...
Date: Wed, 29 Feb 2012 11:26:06 -0800
User-agent: Mozilla/5.0 (Windows; U; Windows NT 6.0; en-US; rv: Gecko/20100228 Lightning/0.9 Thunderbird/ Mnenhy/

Greg Wooledge wrote:

On Tue, Feb 28, 2012 at 05:34:21PM -0800, Linda Walsh wrote:
How can one get the same behavior as before and look up files
relative to PATH regardless of them having a '/' in them?

What?  That sounds like it WAS a bug before, and you had somehow
interpreted it as a feature.  And now you're asking to have the bug

Any pathname that contains a / should not be subject to PATH searching.

You are alone in this opinion -- as most application don't follow that rule.

Pathnames that *start* with '/' are called an "absolute" pathnames,

while paths not starting with '/' are relative.

This is fundamental to the OS.

Try 'C', if you include a include file with "/", it scans for it in each
.h root.

Try Perl -- same thing.

Try 'vim' -- same thing.

Almost all normal utils take their 'paths to be the 'roots' of
trees that contain files.  Why should bash be different?

It goes against 'common sense' and least surprise -- given it's the
norm in so many other applications.

reply via email to

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