From: Bart Schaefer <schaefer@brasslantern.com>
To: Ray Andrews <rayandrews@eastlink.ca>
Cc: Zsh Users <zsh-users@zsh.org>
Subject: Re: array with newlines preserved as literal text
Date: Tue, 2 Feb 2021 18:21:46 -0800 [thread overview]
Message-ID: <CAH+w=7ZWs4ataEtKK+SQraA4dfisPFkagvqbr48jZKL_HwQV6g@mail.gmail.com> (raw)
In-Reply-To: <36596ab3-14b6-da57-e40b-3e66d9ffbb5a@eastlink.ca>
On Tue, Feb 2, 2021 at 3:31 PM Ray Andrews <rayandrews@eastlink.ca> wrote:
>
> Complicated. It goes back to my first bitch with zsh, namely not being
> able to capture the literal invocation of a function (along with it's
> tail) unexpanded, just as you'd see in history.
I'm not entirely sure I understand what that means, but maybe it's this?
_fn2hist() {
emulate -L zsh
local cmd=$1
shift
if [[ -n $functions[$cmd] ]]
then
print -rS "${$(functions -x 2 $cmd)#$cmd} ${${(qq)@}}"
fi
$cmd "$@"
}
Intended to be used like this:
myfn() { : do whatever myfn does }
alias myfn='_fn2hist myfn'
What this does is turn the body of "myfn" into an anonymous function,
and stuff that into the history followed by the original arguments,
and then run the function.
At this point if you up-history, you'll get something like
ubuntu% () {
: do whatever myfn does
} 'original' 'arguments'
That could be a very long history entry, if "myfn" is complicated ...
but if you hit "enter", it should behave just like "myfn" did.
With one caveat: If the function depends on getting its own name from
$0 or some similar trick involving $funcstack, etc., that will fail.
next prev parent reply other threads:[~2021-02-03 2:22 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-02 19:16 Ray Andrews
2021-02-02 19:26 ` Roman Perepelitsa
2021-02-03 1:10 ` Ray Andrews
2021-02-02 20:25 ` Bart Schaefer
2021-02-02 23:31 ` Ray Andrews
2021-02-03 2:21 ` Bart Schaefer [this message]
2021-02-03 19:29 ` Ray Andrews
2021-02-03 21:19 ` Bart Schaefer
2021-02-04 2:07 ` Ray Andrews
2021-02-05 2:57 ` Bart Schaefer
2021-02-04 21:55 ` Ray Andrews
2021-02-05 3:22 ` Bart Schaefer
2021-02-05 4:17 ` Ray Andrews
2021-02-05 4:24 ` Bart Schaefer
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=7ZWs4ataEtKK+SQraA4dfisPFkagvqbr48jZKL_HwQV6g@mail.gmail.com' \
--to=schaefer@brasslantern.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).