zsh-users
 help / color / mirror / code / Atom feed
From: Peter Stephenson <pws@csr.com>
To: zsh-users@sunsite.dk
Subject: Re: print -s and History Expansion
Date: Fri, 05 May 2006 09:55:42 +0100	[thread overview]
Message-ID: <EXCHANGE03IEAOeIiGX00000e9c@exchange03.csr.com> (raw)
In-Reply-To: <20060504190631.GA29447@namib.cs.utk.edu>

Chris Johnson wrote:
>    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
>    }
>    zle -N commit-to-history
>    bindkey "^X^H" commit-to-history
> 
> I tried using ${(qq){$(z)BUFFER}} but that didn't work.

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.

> Perhaps I could have stuck with the simpler bind, but it seems that
> somehow I need to get the command into a parameter before I can split
> it.  Is there any way to expand literals?

There's no way to avoid using a parameter without doing worse things.  Zle
widgets are anyway more readable and predictable than bindkey -s tricks.

-- 
Peter Stephenson <pws@csr.com>                  Software Engineer
CSR PLC, Churchill House, Cambridge Business Park, Cowley Road
Cambridge, CB4 0WZ, UK                          Tel: +44 (0)1223 692070


To access the latest news from CSR copy this link into a web browser:  http://www.csr.com/email_sig.php


  reply	other threads:[~2006-05-05  8:56 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 [this message]
2006-05-05 18:05       ` Chris Johnson

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=EXCHANGE03IEAOeIiGX00000e9c@exchange03.csr.com \
    --to=pws@csr.com \
    --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).