zsh-workers
 help / color / mirror / code / Atom feed
From: Vincent Lefevre <vincent@vinc17.net>
To: zsh-workers@zsh.org
Subject: Re: completion for "info -f" does not work
Date: Fri, 18 Mar 2022 15:09:08 +0100	[thread overview]
Message-ID: <20220318140908.GB35304@zira.vinc17.org> (raw)
In-Reply-To: <20220318135953.GA35304@zira.vinc17.org>

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
zira% info -f for-test-only.info
info: for-test-only.info: No such file or directory
zira% info -f ./for-test-only
zira% info -f ./for-test-only.info
zira% info for-test-only
info: No menu item 'for-test-only' in node '(dir)Top'
zira% info for-test-only.info
info: No menu item 'for-test-only.info' in node '(dir)Top'
zira% info ./for-test-only
zira% info ./for-test-only.info
zira% 

An absence of error means that the file was opened.

Without "-f", the rules seem to be the same, except that info also
checks menu items.

-- 
Vincent Lefèvre <vincent@vinc17.net> - Web: <https://www.vinc17.net/>
100% accessible validated (X)HTML - Blog: <https://www.vinc17.net/blog/>
Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)


  reply	other threads:[~2022-03-18 14:09 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 [this message]
2022-03-22  9:46         ` Jun T
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=20220318140908.GB35304@zira.vinc17.org \
    --to=vincent@vinc17.net \
    --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).