From: Jim Porter <jporterbugs@gmail.com>
To: 65374-done@debbugs.gnu.org
Subject: bug#65374: 30.0.50 [PATCH]; Allow extending Eshell output targets
Date: Mon, 21 Aug 2023 11:47:46 -0700 [thread overview]
Message-ID: <39e614a6-6b14-5549-84de-6d49f15a7ae7@gmail.com> (raw)
In-Reply-To: <0e112183-47fc-d94b-761b-3ddd2c2238fc@gmail.com>
On 8/18/2023 5:48 PM, Jim Porter wrote:
> The attached patches split up the Eshell I/O target code so that each
> target type is its own method. Aside from fixing a couple tiny bugs,
> this should be exactly the same as before, but will make it easier to
> add new target types in the future (and for third-parties to be able to
> do this!).
Merged to master as dc0839de9b3 and closing this bug now.
prev parent reply other threads:[~2023-08-21 18:47 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-19 0:48 bug#65374: 30.0.50 [PATCH]; Allow extending Eshell output targets Jim Porter
2023-08-21 18:47 ` Jim Porter [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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=39e614a6-6b14-5549-84de-6d49f15a7ae7@gmail.com \
--to=jporterbugs@gmail.com \
--cc=65374-done@debbugs.gnu.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.savannah.gnu.org/cgit/emacs.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).