zsh-workers
 help / color / mirror / code / Atom feed
From: "Andrej Borsenkow" <borsenkow.msk@sni.de>
To: <zsh-workers@sunsite.auc.dk>
Subject: RE: Completion widgets, bindkey and ZLE widgets
Date: Wed, 24 Mar 1999 15:52:19 +0300	[thread overview]
Message-ID: <002701be75f5$2748c3b0$21c9ca95@mowp.siemens.ru> (raw)
In-Reply-To: <199903241217.NAA20924@beta.informatik.hu-berlin.de>


Well, I tried to redefine widgets instead of bindkey - and it works. And the
completion is available after switching keymaps as well.

>
> What if you want more than one completion widget behaving like one of
> the builtin widgets? (Just think of the special key completion widgets
> we already have.)
>

It was just an idea ... But, really, let's see, what builtin widgets
describe:

1. Should we first try to glob
2. should we complete prefix or whole word
3. should we list or insert matches
4. should we start menu completion or not

Most (if not all) of this can already be emulated by setting compstate
before calling main completion function. The case of delete-char-or-list is
somewhat hard ... but if it would be possible to call ZLE widget, that could
test, if we are not at the end and then call completion ...

>> Looks somewhat cleaner ... and, later, if we find the way to make ZLE
>> widgets more useful, that will be automatically available to completion
>> widgets as well.
> What are you thinking about here?

Calling one widget from other (like above), getting user input from inside
of widget ... mostly this all were discussed already.

cheers

/andrej


  reply	other threads:[~1999-03-24 12:53 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1999-03-24 12:17 Sven Wischnowsky
1999-03-24 12:52 ` Andrej Borsenkow [this message]
  -- strict thread matches above, loose matches on Subject: below --
1999-03-24 11:49 Andrej Borsenkow

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='002701be75f5$2748c3b0$21c9ca95@mowp.siemens.ru' \
    --to=borsenkow.msk@sni.de \
    --cc=zsh-workers@sunsite.auc.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).