GNU bug report logs - #33782
27.0.50; Emacsclient ignores errors when its frame is deleted

Previous Next

Package: emacs;

Reported by: Philipp <p.stephani2 <at> gmail.com>

Date: Mon, 17 Dec 2018 21:53:01 UTC

Severity: normal

Tags: notabug

Found in version 27.0.50

Done: Noam Postavsky <npostavs <at> gmail.com>

Bug is archived. No further changes may be made.

Full log


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

From: Lars Ingebrigtsen <larsi <at> gnus.org>
To: Noam Postavsky <npostavs <at> gmail.com>
Cc: Philipp <p.stephani2 <at> gmail.com>, 33782 <at> debbugs.gnu.org
Subject: Re: bug#33782: 27.0.50;
 Emacsclient ignores errors when its frame is deleted
Date: Wed, 10 Jul 2019 13:16:08 +0200
Noam Postavsky <npostavs <at> gmail.com> writes:

>>> $ emacsclient --create-frame --eval '(unwind-protect (error "foo")
>>> (delete-frame))' ; echo $?
>>> 0
>>>
>>> This means that if the frame created by Emacsclient is deleted, errors
>>> are ignored.  This seems like a bug; I wouldn't expect errors to be
>>> ignored in this case, because they should bubble up through the
>>> `unwind-protect' form.

[...]

> No, that's incorrect, unwind-protect doesn't catch errors, it just
> executes the handler forms (in this case (message "zot")) before the
> error finishes bubbling.

Yes, but there is no...  bubbling...  in this context.  The code is the
moral equivalent of saying

emacs -Q -nw --eval '(unwind-protect (error "foo") (kill-emacs))'; echo $?

in an emacsclient context, and this which also says "0".

-- 
(domestic pets only, the antidote for overdose, milk.)
   bloggy blog: http://lars.ingebrigtsen.no




This bug report was last modified 5 years and 319 days ago.

Previous Next


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