From: Yuri D'Elia <wavexx@thregr.org>
To: zsh-users@zsh.org
Subject: Re: "Edit" files names
Date: Tue, 05 Sep 2017 23:17:13 +0200 [thread overview]
Message-ID: <87lglsu9pi.fsf@wavexx.thregr.org> (raw)
In-Reply-To: <CAHYJk3SrK8vScmtZ-bPyPLSJByCAMVJu2rnSvHi2iYPVWyWzJQ@mail.gmail.com>
On Tue, Sep 05 2017, Mikael Magnusson wrote:
>> It's not hard to implement, but does anybody know of a tool which
>> already does that (or something very similar)?
>
> Have you tried the edit-command-line widget?
How would you use it efficiently in the above scenario?
The only way I can think of, is by pre-composing
$ mv *exp* *exp*
thus expand the filename twice, then edit the command (which would then
be escaped in the current style).
Inefficient.
next prev parent reply other threads:[~2017-09-05 21:18 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-05 17:56 Yuri D'Elia
2017-09-05 21:04 ` Mikael Magnusson
2017-09-05 21:17 ` Yuri D'Elia [this message]
2017-09-06 4:10 ` Bart Schaefer
2017-09-06 9:17 ` Simon Ruderich
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=87lglsu9pi.fsf@wavexx.thregr.org \
--to=wavexx@thregr.org \
--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).