From: Bart Schaefer <schaefer@brasslantern.com>
To: zsh-workers@zsh.org
Subject: Re: PATCH: highlight pasted text
Date: Thu, 23 Jul 2015 22:21:52 -0700 [thread overview]
Message-ID: <150723222152.ZM18547@torch.brasslantern.com> (raw)
In-Reply-To: <150723220642.ZM18235@torch.brasslantern.com>
On Jul 23, 10:06pm, Bart Schaefer wrote:
}
} zle yank
} zle -R
} zle read-command && zle $REPLY
That doesn't work with yank-pop, sadly, but can anyone point out a
problem with this tiny patch?
diff --git a/Src/Zle/iwidgets.list b/Src/Zle/iwidgets.list
index ebcf317..657e4ef 100644
--- a/Src/Zle/iwidgets.list
+++ b/Src/Zle/iwidgets.list
@@ -94,7 +94,7 @@
"quoted-insert", quotedinsert, ZLE_MENUCMP | ZLE_KEEPSUFFIX
"quote-line", quoteline, 0
"quote-region", quoteregion, 0
-"read-command", readcommand, 0
+"read-command", readcommand, ZLE_NOTCOMMAND
"recursive-edit", recursiveedit, ZLE_MENUCMP | ZLE_KEEPSUFFIX | ZLE_LASTCOL
"redisplay", redisplay, ZLE_MENUCMP | ZLE_KEEPSUFFIX | ZLE_LASTCOL
"redo", redo, ZLE_KEEPSUFFIX
Then you can do:
zle yank
zle -R
while zle read-command
do
# This looks odd but "zle $REPLY" might change $REPLY
# so we have to test it before doing anything else
if [[ $REPLY = (.|)yank-pop ]]
then
zle $REPLY
else
zle $REPLY
break
fi
done
Alternately,
zle yank
zle -R
zle recursive-edit
Of course that requires an extra accept-line to escape from the
recursive-edit. You could fix that with some fancy keymap stuff
passed with -K to recursive-edit, see Functions/Zle/keymap+widget
for possible inspiration.
next prev parent reply other threads:[~2015-07-24 5:21 UTC|newest]
Thread overview: 46+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-15 16:51 bracketed paste Yuri D'Elia
2015-07-15 17:33 ` Yuri D'Elia
2015-07-15 18:15 ` Mikael Magnusson
2015-07-15 18:43 ` Yuri D'Elia
2015-07-16 5:19 ` Oliver Kiddle
2015-07-16 14:32 ` Yuri D'Elia
2015-07-18 2:33 ` Oliver Kiddle
2015-07-18 11:55 ` Yuri D'Elia
2015-07-18 17:17 ` Bart Schaefer
2015-07-18 23:28 ` Oliver Kiddle
2015-07-19 8:13 ` Unmetafy of getsparam() Bart Schaefer
2015-07-21 20:07 ` Peter Stephenson
2015-07-21 23:08 ` Bart Schaefer
2015-07-23 8:50 ` Peter Stephenson
2015-07-16 20:15 ` bracketed paste Bart Schaefer
2015-07-18 12:05 ` Yuri D'Elia
2015-07-18 18:08 ` Bart Schaefer
2015-07-19 2:50 ` PATCH: highlight pasted text Oliver Kiddle
2015-07-19 8:17 ` Bart Schaefer
2015-07-19 12:13 ` Yuri D'Elia
2015-07-19 17:12 ` Daniel Shahaf
2015-07-19 18:10 ` Bart Schaefer
2015-07-21 15:23 ` Oliver Kiddle
2015-07-21 17:35 ` Bart Schaefer
2015-07-23 3:57 ` Oliver Kiddle
2015-07-19 17:57 ` Oliver Kiddle
2015-07-19 18:09 ` Yuri D'Elia
2015-08-08 21:51 ` Daniel Shahaf
2015-08-14 1:38 ` Oliver Kiddle
2015-08-14 5:28 ` Bart Schaefer
2015-07-23 5:00 ` Mikael Magnusson
2015-07-23 6:23 ` Oliver Kiddle
2015-07-24 5:06 ` Bart Schaefer
2015-07-24 5:21 ` Bart Schaefer [this message]
2015-07-24 22:22 ` Oliver Kiddle
2015-07-24 23:13 ` Bart Schaefer
2015-07-25 7:49 ` Oliver Kiddle
2015-07-25 16:46 ` zle options (was Re: PATCH: highlight pasted text) Bart Schaefer
2015-07-28 9:09 ` Oliver Kiddle
2015-07-24 19:06 ` Vim special marks - Re: PATCH: highlight pasted text Oliver Kiddle
2015-07-24 19:45 ` Bart Schaefer
2015-08-11 11:16 ` Oliver Kiddle
2015-08-13 23:14 ` Daniel Shahaf
2015-08-13 23:50 ` Bart Schaefer
2015-08-14 2:09 ` Oliver Kiddle
2015-08-14 5:24 ` Bart Schaefer
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=150723222152.ZM18547@torch.brasslantern.com \
--to=schaefer@brasslantern.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).