all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Jim Porter <jporterbugs@gmail.com>
Cc: christopher@librehacker.com, 72857@debbugs.gnu.org
Subject: bug#72857: 30.0.90; emacs 30: eshell-execute-file DESTINATION
Date: Thu, 29 Aug 2024 07:49:36 +0300	[thread overview]
Message-ID: <867cc0gcgv.fsf@gnu.org> (raw)
In-Reply-To: <927fa6ae-0b55-3151-178a-67efd50f8a41@gmail.com> (message from Jim Porter on Wed, 28 Aug 2024 13:51:13 -0700)

> Date: Wed, 28 Aug 2024 13:51:13 -0700
> From: Jim Porter <jporterbugs@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.





  parent reply	other threads:[~2024-08-29  4:49 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-08-28 17:45 bug#72857: 30.0.90; emacs 30: eshell-execute-file DESTINATION Christopher Howard
2024-08-28 20:51 ` Jim Porter
2024-08-29  2:17   ` Jim Porter
2024-08-29  4:51     ` Jim Porter
2024-08-29  5:50       ` Eli Zaretskii
2024-08-30  4:54         ` Jim Porter
2024-08-29  4:49   ` Eli Zaretskii [this message]
2024-08-29  4:58     ` Jim Porter

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=867cc0gcgv.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=72857@debbugs.gnu.org \
    --cc=christopher@librehacker.com \
    --cc=jporterbugs@gmail.com \
    /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 external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.