zsh-workers
 help / color / mirror / code / Atom feed
From: Sven Wischnowsky <wischnow@informatik.hu-berlin.de>
To: zsh-workers@sunsite.auc.dk
Subject: PATCH: Re: zle -U
Date: Wed, 15 Mar 2000 10:38:16 +0100 (MET)	[thread overview]
Message-ID: <200003150938.KAA15656@beta.informatik.hu-berlin.de> (raw)
In-Reply-To: "Bart Schaefer"'s message of Tue, 14 Mar 2000 18:24:08 +0000


Bart Schaefer wrote:

> On Mar 11,  7:57am, Bart Schaefer wrote:
> }
> } 	zle -U frob
> } 
> } This results in "brof" being inserted onto the command line.
> 
> Sven sent a patch to fix that, but there's still a problem with this:
> 
> 	zle -U f
> 	zle -U r
> 	zle -U o
> 	zle -U b
> 
> Once again we get "brof".  Maybe we should just admit that there is no
> input "queue" (only a stack), as is done with "print -z"?

Right. I haven't changed the order in which the characters from one
string are pushed, hope that's ok for everyone.

Bye
 Sven

diff -ru ../z.old/Doc/Zsh/mod_zle.yo Doc/Zsh/mod_zle.yo
--- ../z.old/Doc/Zsh/mod_zle.yo	Wed Mar 15 10:32:54 2000
+++ Doc/Zsh/mod_zle.yo	Wed Mar 15 10:36:41 2000
@@ -258,9 +258,14 @@
 the widget returns (until it is overwritten by subsequent commands).
 )
 item(tt(-U) var(string))(
-This puts the characters in the var(string) in the input queue of
+This pushes the characters in the var(string) onto the input stack of
 ZLE. After the widget currently executed finishes ZLE will behave as
 if the characters in the var(string) were typed by the user.
+
+Note that since ZLE uses a stack, using tt(zle) with this option more
+than once will make the last string pushed be used first. The
+characters in each var(string) will be used in the order in which they
+appear in the string, though.
 )
 item(var(widget) tt([ -n) var(num) tt(]) tt([ -N ]) var(args) ...)(
 Invoke the specified widget.  This can only be done when ZLE is

--
Sven Wischnowsky                         wischnow@informatik.hu-berlin.de


                 reply	other threads:[~2000-03-15  9:38 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=200003150938.KAA15656@beta.informatik.hu-berlin.de \
    --to=wischnow@informatik.hu-berlin.de \
    --cc=zsh-workers@sunsite.auc.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).