From: Ray Andrews <rayandrews@eastlink.ca>
To: zsh-users@zsh.org
Subject: Re: "Pull just the text of a single command" (was Re: .zsh_history)
Date: Sun, 16 Apr 2023 09:37:08 -0700 [thread overview]
Message-ID: <037a075e-14ee-b68e-44f0-de81425f4c4d@eastlink.ca> (raw)
In-Reply-To: <CAH+w=7bZfwGgKeznLdHK+ZWXbHo0w=H+HAsEac+kZ-8iBLKuBA@mail.gmail.com>
On 2023-04-16 08:53, Bart Schaefer wrote:
> It's much worse than that, consider
You know, as a logician I'm quite aware that there are things one might
ask for that are logically not possible to deliver. It's Godel's
Theorem applied to tokens. Heavy duty stuff. In my case close will count.
> % my_function one && my_function $PATH || my_function three > filename
>
> Or pipelines, or backgrounding, or if/then/else/fi, etc. You will
> need to define what you intend in each case (please, not by writing it
> in prose here).
>
> The ${(z)...} expansion does a best-case job of mimicking the parser,
> so you can start by using ${(z)1} in preexec and work forward from
> there. The simple case with semicolons can be handled by
>
> chain=( ${(s:; :)${(z)1}} )
That all sounds quite promising. What I have now works 99% of the time
and I'm not interested -- except as a brain-bending puzzle -- in trying
to break it, but I think what you're suggesting will be a possible
simplification and that will be nice. Some virgin territory here tho,
so I'll be getting stuck most likely.
>
next prev parent reply other threads:[~2023-04-16 16:37 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-08 16:16 .zsh_history Perry Smith
2023-04-08 16:53 ` .zsh_history Roman Perepelitsa
2023-04-08 17:23 ` .zsh_history Ray Andrews
2023-04-08 17:27 ` .zsh_history Roman Perepelitsa
2023-04-08 17:35 ` .zsh_history Perry Smith
2023-04-08 17:54 ` .zsh_history Ray Andrews
2023-04-14 14:36 ` .zsh_history Felipe Contreras
2023-04-14 15:27 ` .zsh_history Ray Andrews
2023-04-15 4:49 ` .zsh_history Felipe Contreras
2023-04-15 15:29 ` .zsh_history Ray Andrews
2023-04-15 19:47 ` "Pull just the text of a single command" (was Re: .zsh_history) Bart Schaefer
2023-04-15 22:47 ` Ray Andrews
2023-04-15 23:26 ` Bart Schaefer
2023-04-16 15:53 ` Bart Schaefer
2023-04-16 16:37 ` Ray Andrews [this message]
2023-04-16 19:24 ` Ray Andrews
2023-04-16 7:38 ` .zsh_history Roman Perepelitsa
2023-04-16 14:53 ` .zsh_history Ray Andrews
2023-04-16 15:28 ` .zsh_history Bart Schaefer
2023-04-16 15:29 ` .zsh_history Roman Perepelitsa
2023-04-14 14:28 ` .zsh_history Felipe Contreras
2023-04-14 15:18 ` .zsh_history Ray Andrews
2023-04-14 14:00 ` .zsh_history Felipe Contreras
2023-04-14 14:51 ` .zsh_history Felipe Contreras
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=037a075e-14ee-b68e-44f0-de81425f4c4d@eastlink.ca \
--to=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).