From: Chris Johnson <cjohnson@cs.utk.edu>
To: zsh-users@sunsite.dk
Subject: Re: print -s and History Expansion
Date: Fri, 5 May 2006 14:05:17 -0400 [thread overview]
Message-ID: <20060505180517.GA31544@namib.cs.utk.edu> (raw)
In-Reply-To: <EXCHANGE03IEAOeIiGX00000e9c@exchange03.csr.com>
Peter Stephenson sent me the following 1.4K:
> > commit-to-history() {
> > # zsplit current command, expand result to all its quoted fields
> > # ("f1" "f2" "f3"), prepend it with a command to make it written
> > # to history, and then execute it.
> > BUFFER=" print -s ${${(z)BUFFER}[@]}"
> > zle accept-line
> > }
>
> To avoid the extra command line execution I would use:
>
> commit-to-history() {
> print -s ${(z)BUFFER}
> BUFFER=
> zle accept-line
> }
>
> then there are no quoting problems. You still need the accept-line if
> you plan on using what you've just added to the history immediately,
> since otherwise the history isn't reread. However, it's now on an empty
> buffer.
I was able to get
commit-to-history() {
print -s ${(z)BUFFER}
zle send-break
}
zle -N commit-to-history
to work just fine. History expansion pulls in the split words of a just
committed-to-history line just fine, and the command line stays
displayed for reference. It's just like hitting ^C but adds the line to
history, which is exactly what I was looking for.
As far as your accept-line comment above, is the send-break widget not
supposed to behave the way it is? The line is immediately available for
history expansion (histverify is set):
[cjohnson@namib] ~: echo one two three
[cjohnson@namib] ~: echo !!:$
[cjohnson@namib] ~: echo three
three
--
Chris Johnson
cjohnson@cs.utk.edu
http://www.cs.utk.edu/~cjohnson
prev parent reply other threads:[~2006-05-05 18:05 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-02 19:10 Chris Johnson
2006-05-02 21:47 ` Peter Stephenson
2006-05-04 19:06 ` Chris Johnson
2006-05-05 8:55 ` Peter Stephenson
2006-05-05 18:05 ` Chris Johnson [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=20060505180517.GA31544@namib.cs.utk.edu \
--to=cjohnson@cs.utk.edu \
--cc=zsh-users@sunsite.dk \
/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).