From: Bart Schaefer <schaefer@brasslantern.com>
To: Zsh-Users List <zsh-users@zsh.org>
Subject: Re: Fish-like autosuggestions
Date: Wed, 6 Nov 2013 16:04:23 -0800 [thread overview]
Message-ID: <CAH+w=7bvb=tQbwhD=Kiu8XXKLox=pgXUa5N+qc5i18cTy-1eEw@mail.gmail.com> (raw)
In-Reply-To: <20131106200715.6e549a6e@pws-pc.ntlworld.com>
On Wed, Nov 6, 2013 at 12:07 PM, Peter Stephenson
<p.w.stephenson@ntlworld.com> wrote:
> On Tue, 05 Nov 2013 12:40:00 -0800
> Bart Schaefer <schaefer@brasslantern.com> wrote:
>> On Nov 5, 11:46am, Bart Schaefer wrote:
>> }
>> } Hmm, the doc doesn't actually explain what the return value from a -F
>> } handler means to the surrounding code.
>
> It doesn't mean anything: it doesn't make sense for a function
> listening for one file descriptor to cause aborting of a function or
> widget associated with a different descriptor.
OK, I only asked because the examples seem to have different return
values for success/failure, and I wanted to be sure that wasn't more
than a programming habit.
> You'll have to associate a widget with a file descriptor, so it'll need
> to have a specific name [... and]
> can't just use a generic widget because we don't know what file
> descriptors we're listening on.
You've already implemented your idea so perhaps this is moot, but to
explain my thought: The same widget could get invoked for all
descriptors as long as it has a way to tell which descriptor caused
the call. Hence my suggestion of putting the descriptor number in
$NUMERIC etc.; the single widget could just do "case $NUMERIC in ..."
or something (such as passing the FD as an argument, which appears to
be what you did).
next prev parent reply other threads:[~2013-11-07 0:04 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-29 17:52 Thiago Padilha
2013-10-30 16:25 ` Bart Schaefer
2013-11-04 19:30 ` Thiago Padilha
2013-11-05 15:57 ` Bart Schaefer
2013-11-05 16:18 ` Peter Stephenson
2013-11-05 19:46 ` Bart Schaefer
2013-11-05 20:40 ` Bart Schaefer
2013-11-06 20:07 ` Peter Stephenson
2013-11-07 0:04 ` Bart Schaefer [this message]
2013-11-07 9:44 ` Peter Stephenson
2013-11-07 18:07 ` Thiago Padilha
2013-11-07 18:12 ` 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='CAH+w=7bvb=tQbwhD=Kiu8XXKLox=pgXUa5N+qc5i18cTy-1eEw@mail.gmail.com' \
--to=schaefer@brasslantern.com \
--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).