From: Katsumi Yamaoka <yamaoka@jpl.org>
To: ding@gnus.org
Subject: Re: MIME parts not saved
Date: Thu, 08 Aug 2013 09:43:37 +0900 [thread overview]
Message-ID: <b4msiylko5i.fsf@jpl.org> (raw)
In-Reply-To: <87mwotshqt.fsf@uwo.ca>
Dan Christensen wrote:
> Katsumi Yamaoka <yamaoka@jpl.org> writes:
>> Now a temporary file will be deleted by a timer 10 seconds after
>> launching xdg-open.
> There's already logic to delay deletion in mm-display-external, although
> for some reason it is only used in certain situations. Maybe your
> change can be merged with the existing code?
Why I didn't use `mm-postponed-undisplay-list' was that a data
file is made read-only (i.e., not editable) and a viewer doesn't
need the file all the while it is running. However, given even
a 30 seconds delay is not enough, I think we should not stick to
the speediness of deleting the file.
> I find that even a 30 second delay is not enough sometimes, as
> certain viewers notice the deletion and stop displaying the file.
I can imagin it; even in a fast machine, ooffice or equivalent
takes a long time for starting up. Moreover, Gnus will never
know what program xdg-open and the like launches nor when the
program finishes. So, we may have to keep all temporary files
from being deleted.
> So I think it would be convenient to have a variable which indicates
> that temporary files should be left forever, to be cleaned up as
> other files in /tmp are.
Hm, if it is boolean and defaults to nil (deleting), I don't
think a user will find it and alter the value. Instead, how
about deleting temporary files at the next time Gnus starts?
That is:
o Save a list of files to be deleted in "$TMP/.mm-temp-files" when
Gnus exits.
o Try to delete those files when Gnus starts. If it fails on
deleting of some files, schedule them to delete again.
This way will be helpful also for Emacs on Windows and Cygwin.
next prev parent reply other threads:[~2013-08-08 0:43 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 [this message]
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
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=b4msiylko5i.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).