Prev: stdin problem.
Next: Where does gdb find source code to display and step through?
From: Scott Lurndal on 14 Mar 2010 13:46
Lew Pitcher <lpitcher(a)teksavvy.com> writes:
>On Mar 1, 2:12=A0pm, Ramon F Herrera <ra...(a)conexus.net> wrote:
>> On Mar 1, 2:08=A0am, markhob...(a)hotpop.donottypethisbit.com (Mark
>>
>> Hobley) wrote:
>> > In comp.unix.programmer Ramon F Herrera <ra...(a)conexus.net> wrote:
>>
>> > > An educated guess is that what you want is too specialized. The most
>> > > you could find is a path splitter.
>>
>> > I am shocked that there is no path walker. A path splitter would be of =
>some
>> > help, if there is one.
>>
>> > > I was about to suggest the OP to take a look at the program
>> > > "which.exe", Barry.
>>
>> =A0> On my system which is a shell script.
>>
>> On most systems it is a shell built-in.
>
>Maybe. But then again, the Linux bash(1) and builtins(7) manpages make
>no mention of it. Additionally, /bin/which and /usr/bin/which exist,
>and are (or claim to be) POSIX shell scripts.

I think Ramon confused 'which' with 'whence'.

$ type which
which is a tracked alias for /usr/bin/which
$ type type
type is an alias for 'whence -v'
$ type whence
whence is a shell builtin
$ whence which
/usr/bin/which
$ whence type
'whence -v'

scott
From: Lew Pitcher on 21 Mar 2010 03:43

Warning:

Lew Pitcher, who posts to this newsgroup, is a domain thief.

Read the full story at http://www.lpitcher.ca

First  |  Prev  | 
Pages: 1 2 3 4
Prev: stdin problem.
Next: Where does gdb find source code to display and step through?