Gnus development mailing list
 help / color / mirror / Atom feed
From: asjo@koldfront.dk (Adam Sjøgren)
To: ding@gnus.org
Subject: Re: MIME parts not saved
Date: Wed, 14 Aug 2013 10:58:41 +0200	[thread overview]
Message-ID: <87siyck5ry.fsf@topper.koldfront.dk> (raw)
In-Reply-To: <b4mwqnpf8vk.fsf@jpl.org>

Katsumi Yamaoka <yamaoka@jpl.org> writes:

> For the present Gnus code, it starts the timer when Gnus detects
> that the external viewer process exits.

Ah, perfect - sorry for making noise without checking the facts.

> However, if eog is launched by way of xdg-open and the like, Gnus
> immediately detects that the process of xdg-open, not eog, does
> exit, and starts the timer.

Yeah, that's the annoying case.

> In that case, Gnus doesn't know whether a viewer is still running, and
> the viewing will fail, if it is eog, one minute after. But the
> solution for this is obvious. That is to configure the mailcap so as
> to use a viewer program directly, rather than to launch a viewer by
> way of xdg-open.

You could do that, but it would be so much nicer if interaction with
those tools "just worked", as they are widespread as defaults (I
think?)...

Except for a longer time-out, I cannot see a better solution - now that
"delete on quit" isn't acceptable, as per the emacs-devel mailing list.

Maybe the time-out could default to 1 minute, but if you configure it to
nil, then the temporary files will be kept until Emacs quits?

Then people who use detaching viewers simply have to set a single
variable, making an informed decision knowing what "problems" this
causes in /tmp/, and everybody is sort of happy?

I thought your solution with "delete on quit" was elegant, for what it's
worth.


  Best regards,

    Adam

-- 
 "It's my chainsaw                                            Adam Sjøgren
  Division is mine"                                      asjo@koldfront.dk




      parent reply	other threads:[~2013-08-14  8:58 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-08-02  6:17 John Williams
2013-08-03 11:25 ` Lars Magne Ingebrigtsen
2013-08-05  3:31   ` John Williams
2013-08-05  0:54 ` Katsumi Yamaoka
2013-08-05  3:35   ` John Williams
2013-08-05 11:25     ` Katsumi Yamaoka
2013-08-05 15:16       ` Katsumi Yamaoka
2013-08-06 13:52         ` Katsumi Yamaoka
2013-08-07 14:22           ` Dan Christensen
2013-08-08  0:43             ` Katsumi Yamaoka
2013-08-09  8:06               ` Katsumi Yamaoka
2013-08-09 23:20                 ` Dan Christensen
2013-08-12  2:38                   ` Katsumi Yamaoka
2013-08-12  5:59                     ` Katsumi Yamaoka
2013-08-12 14:09                     ` Dan Christensen
2013-08-12 17:18                       ` Lars Magne Ingebrigtsen
2013-08-13  2:29                         ` Dan Christensen
2013-08-13  4:02                           ` Katsumi Yamaoka
2013-08-13  5:22                             ` Katsumi Yamaoka
2013-08-13 10:43                             ` Adam Sjøgren
2013-08-13 20:47                               ` Dan Christensen
2013-08-13 23:50                                 ` Katsumi Yamaoka
2013-08-14  1:41                                   ` Dan Christensen
2013-08-14  8:52                                     ` Adam Sjøgren
2013-08-14  8:58                                   ` Adam Sjøgren [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=87siyck5ry.fsf@topper.koldfront.dk \
    --to=asjo@koldfront.dk \
    --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).