From: Pascal Wittmann <PascalWittmann@gmx.net>
To: zsh-users@zsh.org
Subject: Re: zle insert problems
Date: Tue, 02 Aug 2011 16:55:46 +0200 [thread overview]
Message-ID: <4E380FF2.3020309@gmx.net> (raw)
In-Reply-To: <CAHYJk3RgW0AbYxXxbFyF8wAow6UWtB-=cDH-98y+WWiP3pQU_A@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1216 bytes --]
On 08/02/2011 04:34 PM, Mikael Magnusson wrote:
> On 2 August 2011 16:20, Pascal Wittmann <PascalWittmann@gmx.net> wrote:
>> Hi,
>>
>> I'm trying to build something like this:
>>
>> function do-something() {
>> zle beginning-of-line
>> zle -U "something"
>> zle end-of-line
>> }
>> zle -N do-something
>> bindkey "^[i]" do-something
>
> You can modify the buffer directly via the BUFFER variable, so you
> could just say BUFFER="something $BUFFER" and it should do what you
> want. buffer.
>
Ok, that would work in this simple example. But actually I want to do
some more stuff (the code above was just a minimal working example),
here is the function:
9 replace-pacman-command() {
10 if [[ $LBUFFER = "pacman"* ]]; then
11 zle beginning-of-line
12 zle forward-word
13 zle delete-word
14 zle -U -- $@
15 zle end-of-line
16 fi
17 }
18
19 replace-pacman-command-insert() {
20 replace-pacman-command "-S"
21 }
22
23 zle -N replace-pacman-command-insert
24 bindkey "^[i" replace-pacman-command-insert
I think doing this directly via BUFFER gets quickly unreadable.
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
next prev parent reply other threads:[~2011-08-02 14:54 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 [this message]
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
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=4E380FF2.3020309@gmx.net \
--to=pascalwittmann@gmx.net \
--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).