GNU bug report logs - #72857
30.0.90; emacs 30: eshell-execute-file DESTINATION

Previous Next

Package: emacs;

Reported by: Christopher Howard <christopher <at> librehacker.com>

Date: Wed, 28 Aug 2024 17:47:01 UTC

Severity: normal

Found in version 30.0.90

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

Bug is archived. No further changes may be made.

Full log


Message #14 received at 72857 <at> debbugs.gnu.org (full text, mbox):

From: Eli Zaretskii <eliz <at> gnu.org>
To: Jim Porter <jporterbugs <at> gmail.com>
Cc: christopher <at> librehacker.com, 72857 <at> debbugs.gnu.org
Subject: Re: bug#72857: 30.0.90; emacs 30: eshell-execute-file DESTINATION
Date: Thu, 29 Aug 2024 07:49:36 +0300
> Date: Wed, 28 Aug 2024 13:51:13 -0700
> From: Jim Porter <jporterbugs <at> gmail.com>
> 
> On 8/28/2024 10:45 AM, Christopher Howard wrote:
> > - Am I supposed to be able to pass in the name of a buffer as a string? E.g., "*test*" or "#<*test*>". This does not generate an error, but it does not generate output in the buffer.
> 
> That writes to a file, not a buffer. (Though it seems this regressed in 
> Emacs 31.)

IMO, a string should not be interpreted as a buffer name.  Buffers
should be specified in buffer notation, as in #<*test*>.  If all you
have is a name, you could use get-buffer to return a buffer.




This bug report was last modified 268 days ago.

Previous Next


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