Gnus development mailing list
 help / color / mirror / Atom feed
From: Katsumi Yamaoka <yamaoka@jpl.org>
To: ding@gnus.org
Subject: Re: MIME parts not saved
Date: Wed, 14 Aug 2013 08:50:39 +0900	[thread overview]
Message-ID: <b4mwqnpf8vk.fsf@jpl.org> (raw)
In-Reply-To: <87zjslnwr1.fsf@uwo.ca>

Dan Christensen wrote:
> asjo@koldfront.dk (Adam Sjøgren) writes:

>> Katsumi Yamaoka <yamaoka@jpl.org> writes:
>>
>>> Please let me make a simple question.  Does it take over one
>>> minute when viewing an image by eog?
>>
>> No, but eog is one of those viewers that monitor the file and update the
>> view if it changes.

> Exactly.

Adam Sjøgren also wrote:
> (Can be very nice if you are generating a graph, and you adjust and
> regenerate the file, then eog automatically displays the changed
> graph.)

> Unfortunately this also means that eog will stop displaying the
> image if the file is deleted.

For the present Gnus code, it starts the timer when Gnus detects
that the external viewer process exits.  And after one minute,
Gnus tries to delete a data file.  So, the file should not be
deleted while the viewer is running (if not, it's a bug).
Nevertheless does it cause a problem?

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.  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.

I'm going to try eog anyway in this weekend.



  reply	other threads:[~2013-08-13 23:50 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 [this message]
2013-08-14  1:41                                   ` Dan Christensen
2013-08-14  8:52                                     ` Adam Sjøgren
2013-08-14  8:58                                   ` Adam Sjøgren

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=b4mwqnpf8vk.fsf@jpl.org \
    --to=yamaoka@jpl.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).