GNU bug report logs - #65374
30.0.50 [PATCH]; Allow extending Eshell output targets

Previous Next

Package: emacs;

Reported by: Jim Porter <jporterbugs <at> gmail.com>

Date: Sat, 19 Aug 2023 00:50:02 UTC

Severity: normal

Tags: patch

Found in version 30.0.50

Done: Jim Porter <jporterbugs <at> gmail.com>

Bug is archived. No further changes may be made.

Full log


View this message in rfc822 format

From: help-debbugs <at> gnu.org (GNU bug Tracking System)
To: Jim Porter <jporterbugs <at> gmail.com>
Subject: bug#65374: closed (Re: bug#65374: 30.0.50 [PATCH]; Allow
 extending Eshell output targets)
Date: Mon, 21 Aug 2023 18:48:02 +0000
[Message part 1 (text/plain, inline)]
Your bug report

#65374: 30.0.50 [PATCH]; Allow extending Eshell output targets

which was filed against the emacs package, has been closed.

The explanation is attached below, along with your original report.
If you require more details, please reply to 65374 <at> debbugs.gnu.org.

-- 
65374: https://debbugs.gnu.org/cgi/bugreport.cgi?bug=65374
GNU Bug Tracking System
Contact help-debbugs <at> gnu.org with problems
[Message part 2 (message/rfc822, inline)]
From: Jim Porter <jporterbugs <at> gmail.com>
To: 65374-done <at> debbugs.gnu.org
Subject: Re: bug#65374: 30.0.50 [PATCH]; Allow extending Eshell output targets
Date: Mon, 21 Aug 2023 11:47:46 -0700
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.

[Message part 3 (message/rfc822, inline)]
From: Jim Porter <jporterbugs <at> gmail.com>
To: bug-gnu-emacs <at> gnu.org
Subject: 30.0.50 [PATCH]; Allow extending Eshell output targets
Date: Fri, 18 Aug 2023 17:48:55 -0700
[Message part 4 (text/plain, inline)]
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!).

This won't have any major impact just yet, but it's a very helpful 
precursor to a larger project I'm working on to pipe output in Eshell 
into Lisp functions (currently, Lisp functions - including Eshell 
builtins - can only be the first command in a pipeline).
[0001-Remove-unused-Eshell-target-type.patch (text/plain, attachment)]
[0002-Use-generics-to-define-Eshell-output-targets.patch (text/plain, attachment)]

This bug report was last modified 1 year and 277 days ago.

Previous Next


GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.