From: Bart Schaefer <schaefer@brasslantern.com>
To: zsh-users@zsh.org
Subject: Re: zle insert problems
Date: Tue, 02 Aug 2011 09:45:09 -0700 [thread overview]
Message-ID: <110802094509.ZM28603@torch.brasslantern.com> (raw)
In-Reply-To: <4E38178A.9050406@gmx.net>
On Aug 2, 5:28pm, Pascal Wittmann wrote:
}
} I'll take this solution but just to have a explicit no: There is no way
} doing this only via zle?
I'm going to disagree with PWS a little here (horrors!) and assert that
it's OK to use zle commands to emulate user interactions in the case
where you want to precisely mimic a command's behavior. For example
it's much easier to do
zle vi-backward-word
than it is to analyze $LBUFFER to figure out where that cursor motion
would have left you. The whole set of widget actions isn't flushed to
the screen until the widget finishes or something like "zle -R" is
run, so it's not as if the user sees the cursor jumping about.
This is particularly true if you're working with multi-line buffers
or want to move up and down in the history.
Also you can mix zle actions with direct assignments to the various
control parameters. So your original example could be written
do-something() {
CURSOR=0
LBUFFER="something"
zle end-of-line
}
Thus, similarly,
replace-pacman-command() {
if [[ $LBUFFER = "pacman"* ]]; then
CURSOR=0
zle forward-word
zle delete-word
LBUFFER+="$*"
zle end-of-line
fi
}
Another reason for using zle commands is that they properly maintain
the relative positions of $MARK and $CURSOR, which get lost when you
modify LBUFFER directly. However, there isn't a zle command to insert
arbitrary characters.
next prev parent reply other threads:[~2011-08-02 16:45 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-02 14:20 Pascal Wittmann
2011-08-02 14:34 ` Mikael Magnusson
2011-08-02 14:55 ` Pascal Wittmann
2011-08-02 15:08 ` Manuel Presnitz
2011-08-02 15:09 ` Jérémie Roquet
2011-08-02 15:28 ` Pascal Wittmann
2011-08-02 15:55 ` Peter Stephenson
2011-08-02 16:45 ` Bart Schaefer [this message]
2011-08-02 17:03 ` Pascal Wittmann
2011-08-02 15:17 ` Manuel Presnitz
2011-08-02 15:18 ` Peter Stephenson
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=110802094509.ZM28603@torch.brasslantern.com \
--to=schaefer@brasslantern.com \
--cc=zsh-users@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).