From: Roman Perepelitsa <roman.perepelitsa@gmail.com>
To: Ray Andrews <rayandrews@eastlink.ca>
Cc: Zsh Users <zsh-users@zsh.org>
Subject: Re: command tails
Date: Sun, 16 Apr 2023 18:13:12 +0200 [thread overview]
Message-ID: <CAN=4vMqOXQ4YKev2Hz78zBiDWnT7MvtjJ+a6A=TfopHBuvVzjg@mail.gmail.com> (raw)
In-Reply-To: <b8c7b5a1-83f4-0e00-ac0f-0476237d9cb7@eastlink.ca>
On Sun, Apr 16, 2023 at 5:59 PM Ray Andrews <rayandrews@eastlink.ca> wrote:
>
> 'my_function' should report the literal keystrokes that follow it
This requirement is, unfortunately, ill-defined. Consider an analogy.
Provide a function that prints the weight of the command line in
pounds minus its beauty in parsecs.
You can have the full command line unexpanded (grab it from zle) but
you cannot have an unexpanded command line split on semicolons (weight
minus beauty).
Roman.
prev parent reply other threads:[~2023-04-16 16:14 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-16 15:59 Ray Andrews
2023-04-16 16:13 ` Roman Perepelitsa [this message]
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='CAN=4vMqOXQ4YKev2Hz78zBiDWnT7MvtjJ+a6A=TfopHBuvVzjg@mail.gmail.com' \
--to=roman.perepelitsa@gmail.com \
--cc=rayandrews@eastlink.ca \
--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).