zsh-workers
 help / color / mirror / code / Atom feed
From: Bart Schaefer <schaefer@tiny.zanshin.com>
To: Sven Wischnowsky <wischnow@informatik.hu-berlin.de>
Cc: zsh-workers@sunsite.auc.dk
Subject: Re: Reading completion manual
Date: Wed, 3 Mar 1999 21:50:16 -0800 (PST)	[thread overview]
Message-ID: <14046.7960.802938.351321@localhost.localdomain> (raw)
In-Reply-To: <199903030929.KAA20363@beta.informatik.hu-berlin.de>

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain; charset=unknown, Size: 1070 bytes --]

I may get a chance to reply to more of this later, but for now:

Sven Wischnowsky writes:
 > 
 > > It may be useful to interpret return code from such a function (a lá -t).
 > 
 > Agreed. I was already searching for things we could do with the return 
 > value, but hadn't thought about `-t'. Any suggestions how the return
 > value of completion widgets and zle widgets could be used (when not
 > called from `-K' for the former)?

As long as we're revisiting this discussion and adding things like the
new NUMERIC parameter, allow me to direct your attention to these old
zsh-workers postings and any associated threads:

http://www.zsh.org/cgi-bin/mla/redirect?WORKERNUMBER=4067
http://www.zsh.org/cgi-bin/mla/redirect?WORKERNUMBER=4073 (Bug report)
http://www.zsh.org/cgi-bin/mla/redirect?WORKERNUMBER=4099 (Bug report)
http://www.zsh.org/cgi-bin/mla/redirect?WORKERNUMBER=4568

I'm strongly in favor of having zle widget functions return a useful
value (see 4067) and Zefram even agreed with me, but I don't think
anything ever came of it.


  reply	other threads:[~1999-03-04  5:52 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1999-03-03  9:29 Sven Wischnowsky
1999-03-04  5:50 ` Bart Schaefer [this message]
  -- strict thread matches above, loose matches on Subject: below --
1999-03-03 13:34 Sven Wischnowsky
1999-03-02 16:52 Andrej Borsenkow
1999-03-02 17:09 ` Bruce Stephens
1999-03-02 17:20   ` Andrej Borsenkow
1999-03-02 17:29     ` Bruce Stephens

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=14046.7960.802938.351321@localhost.localdomain \
    --to=schaefer@tiny.zanshin.com \
    --cc=schaefer@brasslantern.com \
    --cc=wischnow@informatik.hu-berlin.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).