help / color / mirror / code / Atom feed
From: Bart Schaefer <schaefer@brasslantern.com>
To: Roman Neuhauser <neuhauser@sigpipe.cz>
Cc: Zach Riggle <zachriggle@gmail.com>, Zsh Users <zsh-users@zsh.org>
Subject: Re: Silly question on :h and = expansion
Date: Tue, 17 Aug 2021 14:49:53 -0700	[thread overview]
Message-ID: <CAH+w=7a5eybKqGC1ia-Pzq_Ru1521bNmS5G3_uDWDcVxBrrtFw@mail.gmail.com> (raw)
In-Reply-To: <YRwrmlzbKMv8vVAE@isis.sigpipe.cz>

On Tue, Aug 17, 2021 at 2:35 PM Roman Neuhauser <neuhauser@sigpipe.cz> wrote:
> btw how long has :c been there?  i only noticed it a few weeks ago.

2009-03-23 it looks like.

Sadly (?) although you can write foo(:c:h) without getting "illegal
modifier" or "modifier failed", "foo" has to be a file in the current
directory before :c can tell you whether it's also somewhere in the
command path.

  reply	other threads:[~2021-08-17 21:51 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-08-17 17:39 Zach Riggle
2021-08-17 17:59 ` Bart Schaefer
2021-08-17 21:35   ` Roman Neuhauser
2021-08-17 21:49     ` Bart Schaefer [this message]
2021-08-17 23:27       ` Zach Riggle
2021-08-18  0:12         ` Bart Schaefer
2021-08-18  2:55           ` Mikael Magnusson
2021-08-18  3:25             ` Bart Schaefer
2021-08-17 21:31 ` Paul
2021-08-17 21:39   ` Roman Neuhauser

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='CAH+w=7a5eybKqGC1ia-Pzq_Ru1521bNmS5G3_uDWDcVxBrrtFw@mail.gmail.com' \
    --to=schaefer@brasslantern.com \
    --cc=neuhauser@sigpipe.cz \
    --cc=zachriggle@gmail.com \
    --cc=zsh-users@zsh.org \


* 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


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).