From: Simon Josefsson <jas@extundo.com>
Cc: bugs@gnus.org (The Gnus Bugfixing Girls + Boys),
ding@gnus.org, 200823-forwarded@bugs.debian.org
Subject: Re: gnus: apparently kills external viewers too aggressively
Date: Wed, 27 Aug 2003 08:03:11 +0200 [thread overview]
Message-ID: <ilubrubwsbk.fsf@latte.josefsson.org> (raw)
In-Reply-To: <86d6erg0mn.fsf@someotherplace.org> (David Coe's message of "Wed, 27 Aug 2003 00:55:44 -0400")
David Coe <davidc@debian.org> writes:
> Simon Josefsson <jas@extundo.com> writes:
>
>> Makes sense, the patch below has been installed. It tries to
>> interrupt the process in a loop with a echo area message, and when it
>> is dead, or you press C-g, it goes on and send it a final KILL and
>> remove the files.
>
> Thanks. That works nicely, but the message "Waiting for external
> displayer to die..." doesn't go away (until user does something, like
> select the next message). The external display process does get
> stopped correctly (and it does destroy the shared segments it had
> allocated), but the message implies to the user that gnus is still
> waiting.
>
> Is there a better way to deal with that message, or do we have a bug
> somewhere else? (Perhaps I or debian gnus/emacs have something wrong.)
I have installed the fix below too. Thanks for testing.
--- mm-decode.el.~6.93.~ Thu Jan 1 01:00:01 1970
+++ mm-decode.el Wed Aug 27 08:01:16 2003
@@ -852,6 +852,7 @@
(quit)
(error))
(ignore-errors (and (cdr object) (kill-buffer (cdr object))))
+ (message "Waiting for external displayer to die...done")
(ignore-errors (delete-file (car object)))
(ignore-errors (delete-directory (file-name-directory
(car object)))))
prev parent reply other threads:[~2003-08-27 6:03 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-20 18:17 Manoj Srivastava
2003-08-20 23:25 ` Simon Josefsson
2003-08-26 17:58 ` David Coe
2003-08-27 1:47 ` Simon Josefsson
2003-08-27 4:55 ` David Coe
2003-08-27 6:03 ` Simon Josefsson [this message]
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=ilubrubwsbk.fsf@latte.josefsson.org \
--to=jas@extundo.com \
--cc=200823-forwarded@bugs.debian.org \
--cc=bugs@gnus.org \
--cc=ding@gnus.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.
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 NNTP newsgroup(s).