From: Ben Elliston <bje@wasabisystems.com>
To: Eli Zaretskii <eliz@elta.co.il>
Cc: gdb@sources.redhat.com
Subject: Re: makeinfo with gdb.texinfo
Date: Wed, 02 Apr 2003 11:46:00 -0000 [thread overview]
Message-ID: <3E8ACD85.7060900@wasabisystems.com> (raw)
In-Reply-To: <8011-Wed02Apr2003061800+0300-eliz@elta.co.il>
[-- Attachment #1: Type: text/plain, Size: 1012 bytes --]
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. In the context of a shell, it makes sense to
apply a search path to prevent users from accidentally executing the
wrong program. You will note that it is not necessary to run `gdb
./a.out' to debug a program of that name in the current working
directory. In the case of Info, the behaviour you describe creates, in
practice, more problems than it solves.
Cheers, Ben
[-- Attachment #2: S/MIME Cryptographic Signature --]
[-- Type: application/x-pkcs7-signature, Size: 3795 bytes --]
next prev parent reply other threads:[~2003-04-02 11:46 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 [this message]
2003-04-02 13:10 ` Andreas Schwab
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=3E8ACD85.7060900@wasabisystems.com \
--to=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