From: Katsumi Yamaoka <yamaoka@jpl.org>
To: ding@gnus.org
Subject: Re: MIME parts not saved
Date: Tue, 13 Aug 2013 13:02:35 +0900 [thread overview]
Message-ID: <b4miozaqlus.fsf@jpl.org> (raw)
In-Reply-To: <87a9kmtjau.fsf@uwo.ca>
Dan Christensen wrote:
> Lars Magne Ingebrigtsen <larsi@gnus.org> writes:
>> Dan Christensen <jdc@uwo.ca> writes:
>>
>>> I would prefer to not have deletion after one minute, but I'm not
>>> sure what other people think. For example, if I view an image
>>> using eog, the window goes blank as soon as the file is deleted.
>>
>> That's unfortunate, but I think that if you wish to do image treatment
>> (and stuff), it would make more sense to save the image, and then start
>> whatever command you want to use on that saved file. The `v'-iew
>> related commands are more for viewing.
> All I'm doing is viewing, using the standard gnome image viewer. I
> pop-up the image of a cat riding a roomba, and by the time I bring my
> laptop over to my wife to impress her, all that eog displays is a blank
> image. It would save me a lot of embarrassment(*) if Gnus wouldn't
> delete the file until later. Especially with Katsumi's fancy
> delete-at-exit code, there doesn't seem to be much point in deleting
> the files using a timer...
> There are other programs which are used purely for viewing attachments
> which also choke when the file they are viewing disappears, and it's not
> unusual to need to spend a lot more than a minute reading a document.
> Dan
> (*) Or maybe you think the current behaviour is already saving me
> some embarrassment?
Please let me make a simple question. Does it take over one
minute when viewing an image by eog? Someone said it's fast[1].
If it needs more than one minute, how long should we prolong a
timer value? I don't think it is down-to-earth if it takes over
one minute, though.
Please see also [2] for the privacy issue.
[1] http://community.linuxmint.com/software/view/eog
[2] http://thread.gmane.org/gmane.emacs.devel/162539
next prev parent reply other threads:[~2013-08-13 4:02 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 [this message]
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=b4miozaqlus.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).