From: "Eli Zaretskii" <eliz@elta.co.il>
To: bje@wasabisystems.com
Cc: gdb@sources.redhat.com
Subject: Re: makeinfo with gdb.texinfo
Date: Wed, 02 Apr 2003 03:25:00 -0000 [thread overview]
Message-ID: <8011-Wed02Apr2003061800+0300-eliz@elta.co.il> (raw)
In-Reply-To: <m28yutwzhj.fsf@sashimi.local.> (message from Ben Elliston on 02 Apr 2003 09:48:40 +1000)
> From: Ben Elliston <bje@wasabisystems.com>
> Date: 02 Apr 2003 09:48:40 +1000
>
> > Yep. If it's like the "info" command
> > bash$ info -f gdb.info
> > gives you the installed version whereas
> > bash$ info -f ./gdb.info
> > gives you the version in the current directory.
>
> It's annoying behaviour and, IMHO, a bug.
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).
> Shouldn't info use copies in the local directory if they can be
> found, otherwise search the info path?
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.
next prev parent reply other threads:[~2003-04-02 3:25 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 [this message]
2003-04-02 11:46 ` Ben Elliston
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=8011-Wed02Apr2003061800+0300-eliz@elta.co.il \
--to=eliz@elta.co.il \
--cc=bje@wasabisystems.com \
--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