GNU bug report logs - #65110
eshell variable triggers error

Previous Next

Package: emacs;

Reported by: Raoul Comninos <revcomninos <at> gmail.com>

Date: Sun, 6 Aug 2023 08:53:01 UTC

Severity: normal

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>
Cc: tracker <at> debbugs.gnu.org
Subject: bug#65110: closed (eshell variable triggers error)
Date: Tue, 08 Aug 2023 02:42:01 +0000
[Message part 1 (text/plain, inline)]
Your message dated Mon, 7 Aug 2023 19:41:35 -0700
with message-id <cda147b1-4393-5244-2c4a-9807e6a2626f <at> gmail.com>
and subject line Re: bug#65110: eshell variable triggers error
has caused the debbugs.gnu.org bug report #65110,
regarding eshell variable triggers error
to be marked as done.

(If you believe you have received this mail in error, please contact
help-debbugs <at> gnu.org.)


-- 
65110: https://debbugs.gnu.org/cgi/bugreport.cgi?bug=65110
GNU Bug Tracking System
Contact help-debbugs <at> gnu.org with problems
[Message part 2 (message/rfc822, inline)]
From: Raoul Comninos <revcomninos <at> gmail.com>
To: bug-gnu-emacs <at> gnu.org
Subject: eshell variable triggers error
Date: Sun, 6 Aug 2023 10:51:44 +0200
[Message part 3 (text/plain, inline)]
If I set this variable:

(setq eshell-list-files-after-cd t)

Emacs egnerates an error in eshell when changing directories:

Assertion failed: (> (cdar handle) 0), 0

The error disappears if the variable is set to nil.

I am running:GNU Emacs 30.0.50 (build 1, x86_64-w64-mingw32) of 2023-08-03

Windows 11

Kindest regards,
Raoul Comninos
[Message part 4 (text/html, inline)]
[Message part 5 (message/rfc822, inline)]
From: Jim Porter <jporterbugs <at> gmail.com>
To: Raoul Comninos <revcomninos <at> gmail.com>, 65110-done <at> debbugs.gnu.org
Subject: Re: bug#65110: eshell variable triggers error
Date: Mon, 7 Aug 2023 19:41:35 -0700
On 8/6/2023 1:44 PM, Jim Porter wrote:
> Happily, this issue *wasn't* a bug in the I/O refcounting code. The 
> failed assertion (which is new in Emacs 30 and exists for exactly this 
> reason) just revealed a bug in another part of Eshell. Fix attached 
> (plus fixing another issue mentioned in the code comments) with some 
> regression tests.
> 
> Let me know if this works for you, or if you see any further issues.

After discussing this off-list, this looks good (thanks for testing!). 
Merged to master as 301e6a747ac, and closing this now.


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

Previous Next


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