From: Sebastian Gniazdowski <sgniazdowski@gmail.com>
To: Yefim Vedernikoff <hi@yef.im>
Cc: Zsh hackers list <zsh-workers@zsh.org>
Subject: Re: feature request
Date: Fri, 17 Jan 2020 03:51:18 +0100 [thread overview]
Message-ID: <CAKc7PVBQ7jCZPGn_Lj2i8UbVUnZSKU0rugEO2n2TKAUXU96kUw@mail.gmail.com> (raw)
In-Reply-To: <CAKc7PVDRRRYS=fkvV92KaoeAt-SAYzz6rYAuBAoW1e1NK5Erjg@mail.gmail.com>
On Fri, 17 Jan 2020 at 02:49, Sebastian Gniazdowski
<sgniazdowski@gmail.com> wrote:
>
> On Thu, 16 Jan 2020 at 23:11, Yefim Vedernikoff <hi@yef.im> wrote:
> >
> > What would it take to add a new environment variable like $OUTPUT to keep
> > track of the last output? I like the $(!!) solution from
> > https://stackoverflow.com/questions/24283097/reusing-output-from-last-command-in-bash
> > but I don't like that it redoes the work (especially if the work is
> > intensive).
>
> I have a plugin in my TODO that would be defining global aliases OUT,
> OUT2, etc. for the previous command's output, etc. It'll be based on
> tmux capture-pane command. I'm not sure when the project will start,
> any cooperation could speed this up.
Also, you could look at:
https://github.com/psprint/ztrace
--
Sebastian Gniazdowski
News: https://twitter.com/ZdharmaI
IRC: https://kiwiirc.com/client/chat.freenode.net:+6697/#zplugin
Blog: http://zdharma.org
next prev parent reply other threads:[~2020-01-17 2:52 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-16 22:10 Yefim Vedernikoff
2020-01-16 22:18 ` Eric Cook
2020-01-16 23:17 ` Andreas Kusalananda Kähäri
2020-01-16 23:57 ` Daniel Shahaf
2020-01-17 1:49 ` Sebastian Gniazdowski
2020-01-17 2:51 ` Sebastian Gniazdowski [this message]
2020-01-17 2:35 ` Martijn Dekker
2020-01-18 18:59 ` Vincent Lefevre
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=CAKc7PVBQ7jCZPGn_Lj2i8UbVUnZSKU0rugEO2n2TKAUXU96kUw@mail.gmail.com \
--to=sgniazdowski@gmail.com \
--cc=hi@yef.im \
--cc=zsh-workers@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).