From: Bart Schaefer <schaefer@brasslantern.com>
To: Oliver Kiddle <opk@zsh.org>
Cc: Marlon Richert <marlon.richert@gmail.com>,
Zsh hackers list <zsh-workers@zsh.org>
Subject: Re: [FEATURE][PATCH] Complete local executables with ./ prefix, if prefix-needed is false
Date: Wed, 8 Dec 2021 15:42:53 -0800 [thread overview]
Message-ID: <CAH+w=7YUBF0W+Sm+UQd8w4RjAofLZsFqnA2nUFaJ42eubWn2xA@mail.gmail.com> (raw)
In-Reply-To: <64846-1639005414.316056@22FL.WcIa.VGfN>
On Wed, Dec 8, 2021 at 3:18 PM Oliver Kiddle <opk@zsh.org> wrote:
>
> This is the type of thing which often can already be achieved with
> styles and, where not, a few tweaks may enable it. The nearest example
> from my own config involves using the fake style
Yeah, I was pretty sure there was a way to get here using the "fake"
style but couldn't put my finger on the argument Daniel found to argue
against changes to prefix-needed.
> The fake style is looked up in _description so a dummy call to it is one
> option. The patch below adds that but I'd be interested in any thoughts
> on that.
Is it going to matter that this happens before command-path is
consulted? And before the defs array is passed to _alternative?
> path=( $cmdpath:A ) when the command-path style is set. That resolves
> only the first of these issues and allows for relative paths in the
> command-path style to work as intended, even if that isn't especially
> useful.
Does that have any unexpected interaction with PATH_DIRS ?
next prev parent reply other threads:[~2021-12-08 23:43 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-07 19:15 Marlon Richert
2021-12-08 0:22 ` Aaron Schrab
2021-12-08 0:50 ` Bart Schaefer
2021-12-08 1:16 ` Aaron Schrab
2021-12-08 16:25 ` Daniel Shahaf
2021-12-08 17:07 ` Bart Schaefer
2021-12-08 19:13 ` Daniel Shahaf
2021-12-08 23:16 ` Oliver Kiddle
2021-12-08 23:42 ` Bart Schaefer [this message]
2021-12-09 21:19 ` Oliver Kiddle
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='CAH+w=7YUBF0W+Sm+UQd8w4RjAofLZsFqnA2nUFaJ42eubWn2xA@mail.gmail.com' \
--to=schaefer@brasslantern.com \
--cc=marlon.richert@gmail.com \
--cc=opk@zsh.org \
--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).