From: Bart Schaefer <schaefer@brasslantern.com>
To: Zsh hackers list <zsh-workers@zsh.org>
Subject: Re: zle: vi mode: wrong undo handling on fresh lines
Date: Mon, 3 Feb 2014 14:20:20 -0800 [thread overview]
Message-ID: <CAH+w=7ZP1GzdJq3NgL0_X1sn22409353Atn+FDUwc=G=GrPMPw@mail.gmail.com> (raw)
In-Reply-To: <16516.1391462981@thecus.kiddle.eu>
[-- Attachment #1: Type: text/plain, Size: 1077 bytes --]
On Mon, Feb 3, 2014 at 1:29 PM, Oliver Kiddle <okiddle@yahoo.co.uk> wrote:
>
> It really ought to be possible to redefine complete-word. The following
> works with old-style completion but not with the new. Anyone have an
> idea why?
>
> complete-word() {
> zle .complete-word
> }
> zle -N complete-word
>
The obvious reason is that "new completion" has already re-bound
complete-word to the _main_complete function. You can't override the
.complete-word form, so you're always going to bypass new completion when
running "zle .complete-word".
The second possible problem is that you've changed complete-word from a
completion widget (defined with "zle -C") into a normal widget. It mostly
works to call completion widgets from normal ones (though not the other way
around) but you have to be careful, and you might need to make calls to the
special auto-suffix-* widgets at the right times.
To get what I think you're after here, you'd more likely want
complete_word() {
_main_complete "$@"
}
zle -C complete-word .complete-word complete-word
but I'm not certain.
next prev parent reply other threads:[~2014-02-03 22:20 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-22 12:37 Hauke Petersen
2013-09-22 18:24 ` Bart Schaefer
2013-09-22 20:27 ` Hauke Petersen
2013-09-23 4:57 ` Bart Schaefer
2013-09-23 20:30 ` Peter Stephenson
2014-01-24 23:19 ` Oliver Kiddle
2014-01-25 19:15 ` Bart Schaefer
2014-01-27 12:43 ` Peter Stephenson
2014-01-27 16:11 ` Peter Stephenson
2014-01-28 14:58 ` Peter Stephenson
2014-01-28 16:28 ` Bart Schaefer
2014-01-28 16:47 ` Peter Stephenson
2014-01-28 17:41 ` Bart Schaefer
2014-01-28 23:00 ` Oliver Kiddle
2014-01-29 2:59 ` Bart Schaefer
2014-01-29 10:50 ` Oliver Kiddle
2014-01-29 14:48 ` Bart Schaefer
2014-01-30 14:51 ` Jun T.
2014-01-30 15:38 ` Peter Stephenson
2014-01-30 16:03 ` Bart Schaefer
2014-01-31 12:00 ` Jun T.
2014-01-31 15:19 ` Bart Schaefer
2014-01-31 15:33 ` Peter Stephenson
[not found] ` <16181.1391175951@thecus.kiddle.eu>
2014-01-31 16:43 ` Jun T.
2014-01-31 21:37 ` Oliver Kiddle
2014-01-31 22:32 ` Oliver Kiddle
2014-02-01 19:27 ` Bart Schaefer
2014-02-03 16:20 ` Jun T.
2014-02-03 21:29 ` Oliver Kiddle
2014-02-03 22:20 ` Bart Schaefer [this message]
2014-02-03 23:26 ` Oliver Kiddle
2014-02-04 17:11 ` Jun T.
2014-02-05 22:00 ` Oliver Kiddle
2014-02-02 22:10 ` Oliver Kiddle
2014-02-07 14:43 ` Oliver Kiddle
2014-02-07 16:22 ` Bart Schaefer
2014-01-27 16:29 ` 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='CAH+w=7ZP1GzdJq3NgL0_X1sn22409353Atn+FDUwc=G=GrPMPw@mail.gmail.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).