From: Andreas Schwab <schwab@suse.de>
To: Ben Elliston <bje@wasabisystems.com>
Cc: Eli Zaretskii <eliz@elta.co.il>, gdb@sources.redhat.com
Subject: Re: makeinfo with gdb.texinfo
Date: Wed, 02 Apr 2003 13:10:00 -0000 [thread overview]
Message-ID: <jeel4lt58d.fsf@sykes.suse.de> (raw)
In-Reply-To: <3E8ACD85.7060900@wasabisystems.com> (Ben Elliston's message of "Wed, 02 Apr 2003 21:46:13 +1000")
Ben Elliston <bje@wasabisystems.com> writes:
|> Eli Zaretskii wrote:
|>
|> >Actually, it's a deliberately programmed feature. It's even described
|> >in the manual: relative file names are interpreted as being relative
|> >to one of the directories mentioned in the INFOPATH environment
|> >variable (or in the default Info search path if INFOPATH is
|> >undefined).
|> >
|> >It mimics the behavior of a Unix shell when searching for executable
|> >programs: the current directory is never searched, unless you have "."
|> >in your PATH.
|> >
|> One could argue that there is a fundamental difference between a shell and
|> other programs: the shell executes programs; most others treat their
|> arguments as input files.
But most other programs don't use a search path for their input files.
Compare with the C preprocessor, which distinguishes between <...> and
"...".
Andreas.
--
Andreas Schwab, SuSE Labs, schwab@suse.de
SuSE Linux AG, Deutschherrnstr. 15-19, D-90429 Nürnberg
Key fingerprint = 58CA 54C7 6D53 942B 1756 01D3 44D5 214B 8276 4ED5
"And now for something completely different."
next prev parent reply other threads:[~2003-04-02 13:10 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-31 17:22 Bob Rossi
2003-03-31 17:42 ` Daniel Jacobowitz
2003-03-31 17:52 ` Bob Rossi
2003-03-31 18:12 ` Doug Evans
2003-03-31 18:22 ` Bob Rossi
2003-04-02 1:00 ` Ben Elliston
2003-04-02 3:25 ` Eli Zaretskii
2003-04-02 11:46 ` Ben Elliston
2003-04-02 13:10 ` Andreas Schwab [this message]
2003-04-02 15:48 ` Andrew Cagney
2003-04-03 2:57 ` Eli Zaretskii
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=jeel4lt58d.fsf@sykes.suse.de \
--to=schwab@suse.de \
--cc=bje@wasabisystems.com \
--cc=eliz@elta.co.il \
--cc=gdb@sources.redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox