From: Peter Stephenson <p.stephenson@samsung.com>
To: undisclosed-recipients: ;
Cc: zsh-workers@zsh.org
Subject: Re: implicit previous command, only state what should change
Date: Wed, 16 Jul 2014 14:54:33 +0100 [thread overview]
Message-ID: <20140716145433.073fda81@pwslap01u.europe.root.pri> (raw)
In-Reply-To: <87bnsq9m30.fsf@debian.uxu>
On Wed, 16 Jul 2014 02:36:03 +0200
Emanuel Berg <embe8573@student.uu.se> wrote:
> Peter Stephenson <p.stephenson@samsung.com> writes:
>
> >> Let's say I write: $ grep user-home-directory *.el
> >> After that, I realize that it should have been
> >> user-emacs-directory'. Is there a way to tell zsh
> >> to "execute the previous command again, only
> >> substitute the first argument for
> >> user-emacs-directory"?
> >
> > The read-from-minibufer change is a bug fix: NUMERIC
> > was being propagated down to the first command read
> > within the recursive edit. I suspect that might be
> > regarded as a bug in recursive-edit.
>
> ???
The bit you quote is a reference to the details of the patch, which you
can ignore unless you're particularly interested in the implementation.
What I should have said but didn't was, here's a new function called
replace-argument that does that. That was in the body of the patch, but
unless you're programmed to look at zsh code patches when a new message
arrives you wouldn't notice.
I'll commit it when I have a couple of minutes spare.
pws
next prev parent reply other threads:[~2014-07-16 14:04 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-13 22:06 Emanuel Berg
2014-07-13 22:24 ` Frank Terbeck
2014-07-13 22:50 ` Emanuel Berg
2014-07-14 2:08 ` Mikael Magnusson
2014-07-14 13:09 ` Emanuel Berg
2014-07-15 6:46 ` Bart Schaefer
2014-07-15 15:42 ` Emanuel Berg
2014-07-15 16:58 ` Peter Stephenson
2014-07-16 0:36 ` Emanuel Berg
2014-07-16 13:54 ` Peter Stephenson [this message]
2014-07-16 20:45 ` Emanuel Berg
2014-07-16 20:53 ` Bart Schaefer
2014-07-16 21:08 ` Emanuel Berg
2014-07-17 8:17 ` Peter Stephenson
2014-07-17 13:01 ` Emanuel Berg
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=20140716145433.073fda81@pwslap01u.europe.root.pri \
--to=p.stephenson@samsung.com \
--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).