unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Jim Porter <jporterbugs@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: christopher@librehacker.com, 73722@debbugs.gnu.org
Subject: bug#73722: 30.0.91; error calling eshell/clear with no argument
Date: Tue, 15 Oct 2024 14:31:21 -0700	[thread overview]
Message-ID: <05bd5ca0-7c14-a2af-ff58-77e6725b4be7@gmail.com> (raw)
In-Reply-To: <86msj5qm2g.fsf@gnu.org>

On 10/15/2024 11:04 AM, Eli Zaretskii wrote:
>> Eli, does this look ok for the release branch? It fixes a regression
>> from Emacs 29 and adds a pair of regression tests to prevent future
>> breakage. (If and when this merges, I'll see about a more-thorough fix
>> for the master branch too.)
> 
> If the problem is with empty body of progn, why does the fix have to
> be so much less self-evident?  Can you fix it by protecting against
> empty body of progn instead, so that the fix is less likely to cause
> unintended consequences?

That's just the loudest part of the bug. Even though I've already fixed 
that part on Emacs 31, things still don't work correctly there. If you 
run the "clear" command in Eshell it clears the screen, but then prints 
two new prompts on the same line together. However, this behavior is 
pretty close to what "clear" did in Emacs 29: it prints two prompts (but 
there's a newline between them).

If I fix the empty 'progn' case, I guess that would fix the regression 
(aside from the missing newline, which I'm not sure how to fix). 
However, "clear" still wouldn't work correctly.

What do you think would be better for Emacs 30? Fix "clear" so it works 
properly, or just fix the new regression? (In the latter case, I can fix 
it with a one-liner.)





  reply	other threads:[~2024-10-15 21:31 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-10-09 17:33 bug#73722: 30.0.91; error calling eshell/clear with no argument Christopher Howard
2024-10-15 17:00 ` Jim Porter
2024-10-15 18:04   ` Eli Zaretskii
2024-10-15 21:31     ` Jim Porter [this message]
2024-10-16  5:17       ` Eli Zaretskii
2024-10-16 18:04         ` Jim Porter
2024-10-17  4:47           ` 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

  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=05bd5ca0-7c14-a2af-ff58-77e6725b4be7@gmail.com \
    --to=jporterbugs@gmail.com \
    --cc=73722@debbugs.gnu.org \
    --cc=christopher@librehacker.com \
    --cc=eliz@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).