From: Peter Stephenson <p.stephenson@samsung.com>
To: Zsh Users <zsh-users@zsh.org>
Subject: Re: Dynamic named directories and completion
Date: Mon, 26 Feb 2018 17:55:28 +0000 [thread overview]
Message-ID: <20180226175528.4a422ec7@pwslap01u.europe.root.pri> (raw)
In-Reply-To: <CAHYJk3QAGHpp0YsGt8mtsrx384jFw8JCS6V895ubO3tnRNBWJw@mail.gmail.com>
On Mon, 26 Feb 2018 18:49:01 +0100
Mikael Magnusson <mikachu@gmail.com> wrote:
> > (Ideally, in fact, whether or not we expand ~[whatever] needs
> > configuring --- because this is dynamic completion you might decide to
> > expand it to freeze the path for future use. I'll look at that if I get
> > the chance. This is the sort of reason for using the expand completer
> > I'm talking about.)
>
> In this type of situation I usually explicitly press expand-word (^X*
> by default I believe).
Yep, ideally as far as the internal and therefore non-configurable
widgets are concerned, I think we want expand-word to expand this and
expand-or-complete not to. That's what happens with normal ~, so this
should be doable.
pws
prev parent reply other threads:[~2018-02-26 17:55 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-22 22:54 Scott Frazer
2018-02-23 0:29 ` [RFC PATCH] _path_files: teach zsh_directory_name Takeshi Banse
2018-02-23 1:19 ` _path_files: fix copy paste error Takeshi Banse
2018-02-23 1:30 ` _path_files: fix copy paste error (2/2) Takeshi Banse
2018-02-23 8:01 ` Dynamic named directories and completion Vincent Bernat
2018-02-23 14:41 ` Scott Frazer
2018-02-23 15:02 ` Takeshi Banse
2018-02-23 14:42 ` Scott Frazer
2018-02-24 19:34 ` Peter Stephenson
2018-02-24 19:49 ` Mikael Magnusson
2018-02-24 20:12 ` Peter Stephenson
2018-02-26 14:31 ` Scott Frazer
2018-02-26 13:53 ` Scott Frazer
2018-02-26 14:47 ` Peter Stephenson
2018-02-26 16:44 ` Scott Frazer
2018-02-26 20:08 ` Peter Stephenson
2018-02-26 21:22 ` Peter Stephenson
2018-02-26 17:49 ` Mikael Magnusson
2018-02-26 17:55 ` Peter Stephenson [this message]
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=20180226175528.4a422ec7@pwslap01u.europe.root.pri \
--to=p.stephenson@samsung.com \
--cc=zsh-users@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).