From: Jun T <takimoto-j@kba.biglobe.ne.jp>
To: zsh-workers@zsh.org
Subject: Re: completion for "info -f" does not work
Date: Tue, 22 Mar 2022 18:46:13 +0900 [thread overview]
Message-ID: <420E9029-D5DB-4621-80E2-3BF7A86997B0@kba.biglobe.ne.jp> (raw)
In-Reply-To: <20220318140908.GB35304@zira.vinc17.org>
> 2022/03/18 23:09, Vincent Lefevre <vincent@vinc17.net> wrote:
>
> On 2022-03-18 14:59:53 +0100, Vincent Lefevre wrote:
>> On 2022-03-16 17:46:28 +0900, Jun T wrote:
>>> 'info -f' accept any (relative or absolute) pathnames.
>>
>> Well, not exactly. It seems that the rule for "info -f" is that
>> if the argument does not have a slash, then the usual info path
>> is used (with no fallback if nothing is found, i.e. an existing
>> pathname in the current directory will be ignored), otherwise
>> the argument is regarded as a pathname.
>
> This can be tested as follows:
>
> zira% touch for-test-only.info
> zira% info -f for-test-only
> info: for-test-only: No such file or directory
I can't reproduce this. Which version of info are you using?
% info --version
info (GNU texinfo) 6.7
% touch for-test-only.info
% info -w -f for-test-only
././for-test-only.info
info command has an (undocumented) option -x for setting the
debug level.
% info -x 1 -f for-test-only # use -x 2 for more verbose output
info: looking for file "for-test-only"
info: looking for file for-test-only in /usr/share/info
info: looking for file for-test-only in /home/takimoto/.local/share/info
info: looking for file for-test-only in .
info: found file ./for-test-only.info
PS
I've surprised that 'info for-test-only' (without -f) also gives the
same result. So I wonder what is the difference between 'info foo ...'
and 'info -f foo ...' ?
next prev parent reply other threads:[~2022-03-22 9:46 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-15 17:13 Vincent Lefevre
2022-03-15 18:05 ` Peter Stephenson
2022-03-16 8:46 ` Jun T
2022-03-16 15:06 ` Peter Stephenson
2022-03-16 15:13 ` Bart Schaefer
2022-03-16 15:28 ` Jun. T
2022-03-17 16:29 ` Peter Stephenson
2022-03-18 13:59 ` Vincent Lefevre
2022-03-18 14:09 ` Vincent Lefevre
2022-03-22 9:46 ` Jun T [this message]
2022-03-22 13:32 ` Vincent Lefevre
2022-03-22 9:35 ` Peter Stephenson
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=420E9029-D5DB-4621-80E2-3BF7A86997B0@kba.biglobe.ne.jp \
--to=takimoto-j@kba.biglobe.ne.jp \
--cc=zsh-workers@zsh.org \
/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.
Code repositories for project(s) associated with this public inbox
https://git.vuxu.org/mirror/zsh/
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).