GNU bug report logs - #492
messages upon kill-emacs gone before you know it

Previous Next

Package: emacs;

Reported by: jidanni <at> jidanni.org

Date: Fri, 27 Jun 2008 16:15:04 UTC

Severity: wishlist

Tags: wontfix

Merged with 1411

Done: Glenn Morris <rgm <at> gnu.org>

Bug is archived. No further changes may be made.

To add a comment to this bug, you must first unarchive it, by sending
a message to control AT debbugs.gnu.org, with unarchive 492 in the body.
You can then email your comments to 492 AT debbugs.gnu.org in the normal way.

Toggle the display of automated, internal messages from the tracker.

View this report as an mbox folder, status mbox, maintainer mbox


Report forwarded to bug-submit-list <at> lists.donarmstrong.com, Emacs Bugs <bug-gnu-emacs <at> gnu.org>:
bug#492; Package emacs. Full text and rfc822 format available.

Acknowledgement sent to jidanni <at> jidanni.org:
New bug report received and forwarded. Copy sent to Emacs Bugs <bug-gnu-emacs <at> gnu.org>. Full text and rfc822 format available.

Message #5 received at submit <at> emacsbugs.donarmstrong.com (full text, mbox):

From: jidanni <at> jidanni.org
To: bug-gnu-emacs <at> gnu.org
Cc: emacs-w3m <at> namazu.org
Subject: messages upon kill-emacs gone before you know it
Date: Fri, 27 Jun 2008 23:48:23 +0800
Gentlemen, today upon exiting emacs I saw there in the minibuffer:
    "error when ..." or something.
But poof, it was gone, as of course emacs then exited, without even
enough time to read the rest of the message.

Normally one would leisurely view-echo-area-messages, but no, too late
for that, emacs was exiting and no trace is left of anything, even if
one uses emacs -nw.

Got an idea: why not spew any final exit messages straight to the
terminal, so they stay on the screen after emacs disappears.

For now I'll use

;;else how are we to see final error messages?
(add-hook
 'kill-emacs-hook
 '(lambda ()
    (sleep-for 5) ;or (sit-for 5)
    ))

And what if there's two or more messages?

Anyway, no I don't enjoy delaying my supposedly busy day for five
whole seconds on the slight chance that something inside emacs might
have some last words.

(Hmmm,
kill-emacs-hook is a variable defined in `C source code'.
Its value is
(w3m-arrived-shutdown
 (lambda nil
   (sleep-for 5))
 #[nil "\300\301!\207"
       [server-mode -1]
       2])

So it was probably some w3m-arrived-shutdown error messages that went
by so fast that they were gone before one could read them. But still,
not being able to read any final error messages is a general problem.
And one cannot expect every possible message in emacs to come with a
sit-for...)





Severity set to `wishlist' from `normal' Request was from Glenn Morris <rgm <at> gnu.org> to control <at> emacsbugs.donarmstrong.com. (Sat, 28 Jun 2008 01:10:05 GMT) Full text and rfc822 format available.

Information forwarded to bug-submit-list <at> lists.donarmstrong.com, Emacs Bugs <bug-gnu-emacs <at> gnu.org>:
bug#492; Package emacs. (Thu, 30 Apr 2009 22:15:03 GMT) Full text and rfc822 format available.

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

From: Glenn Morris <rgm <at> gnu.org>
To: <control <at> debbugs.gnu.org>
Subject: control message for bug 492
Date: Sat, 09 Jul 2011 19:00:36 -0400
forcemerge 1411 492




bug archived. Request was from Debbugs Internal Request <help-debbugs <at> gnu.org> to internal_control <at> debbugs.gnu.org. (Sun, 07 Aug 2011 11:24:06 GMT) Full text and rfc822 format available.

This bug report was last modified 14 years and 11 days ago.

Previous Next


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