zsh-workers
 help / color / mirror / code / Atom feed
From: Dylan Alex Simon <dylan@dylex.net>
To: zsh-workers@sunsite.dk
Subject: Re: crash when expand-or-complete widget wrapped
Date: Sat, 11 Apr 2009 00:31:52 -0400	[thread overview]
Message-ID: <20090411043152.GA26742@datura.dylex.net> (raw)
In-Reply-To: <20090408044920.GA21100@datura.dylex.net>

> > Is there some reason this is not an okay thing to do or that completion widgets
> > should be called differently?  (I'm working on improving predict-on.)
> 
> You can't call completion widgets from non-completion widgets, in the
> general case.  In fact you generally can't call completion widgets
> with "zle widget_name", because completion widgets don't share the
> normal editor state.

> zle -C widget-wrapper expand-or-complete widget-wrapper

Sorry, I guess my question was a little confused (I shouldn't have said
"completion widgets").  As far as I understand, expand-or-complete and
complete-word are not themselves actual completion widgets (they aren't
generating completion lists) but rather zle widgets that invoke completion.

In fact, complete-word is invoked exactly as "zle complete-word" from
insert-and-predict in predict-on (which works fine).  The problem seems only
to happen when you invoke the dotted version "zle .expand-or-complete" rather
than "zle expand-and-complete".  That is, if I create a new widget to wrap
expand-and-complete that just does "zle expand-and-complete -- "$@"" and bind
tab to it instead, things work fine.

:-Dylan


  parent reply	other threads:[~2009-04-11  4:32 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-04-07  3:57 subscript too small after complete in variable Dylan Alex Simon
2009-04-07  4:16 ` Bart Schaefer
2009-04-07  9:18   ` Peter Stephenson
2009-04-08  4:49 ` crash when expand-or-complete widget wrapped Dylan Alex Simon
2009-04-08 16:02   ` Bart Schaefer
2009-04-11  4:31   ` Dylan Alex Simon [this message]
2009-04-12 17:55     ` 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=20090411043152.GA26742@datura.dylex.net \
    --to=dylan@dylex.net \
    --cc=zsh-workers@sunsite.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).