From: Bart Schaefer <schaefer@brasslantern.com>
To: Zsh-Users List <zsh-users@zsh.org>
Subject: Re: Fish-like autosuggestions
Date: Tue, 05 Nov 2013 11:46:40 -0800 [thread overview]
Message-ID: <131105114640.ZM18224@torch.brasslantern.com> (raw)
In-Reply-To: <20131105161858.543037da@pwslap01u.europe.root.pri>
On Nov 5, 4:18pm, Peter Stephenson wrote:
}
} It would seem natural to replace the callhookfunc() in raw_getbyte()
} with a zlecallhook(). However, that's incompatible so it probably needs
} augmenting with an additional option to zle -F to indicate the argument
} is a ZLE widget rather than a shell function
How about we treat it like zle-line-init, zle-keymap-select, etc.? Have
a single predefined widget name that is called at that point (whether
before, after, or instead of the "zle -F" handlers, I don't really have
an opinion yet). Pass the file descriptor number in $NUMERIC, and maybe
even set $PENDING to say how many bytes are ready on that FD.
Hmm, the doc doesn't actually explain what the return value from a -F
handler means to the surrounding code. There should probably be some
sort of return-code-based protocol to indicate whether handling should
proceed, which makes me lean away from the "instead" option but still
doesn't resolve before/after for me.
next prev parent reply other threads:[~2013-11-05 19:47 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 [this message]
2013-11-05 20:40 ` Bart Schaefer
2013-11-06 20:07 ` Peter Stephenson
2013-11-07 0:04 ` Bart Schaefer
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=131105114640.ZM18224@torch.brasslantern.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).