From: Katsumi Yamaoka <yamaoka@jpl.org>
To: ding@gnus.org
Subject: Re: Set temp files (viewing attachments) read-only?
Date: Mon, 07 Apr 2008 13:19:33 +0900 [thread overview]
Message-ID: <b4my77qthyi.fsf@jpl.org> (raw)
In-Reply-To: <87myo68gsg.fsf@rimspace.net>
>>>>> Daniel Pittman wrote:
> Reiner Steib <reinersteib+gmane@imap.cc> writes:
>> Setting the temp file read-only[2] should make it clear, that editing
>> it might be a bad idea. It also forces the user to choose a different
>> file name or location when saving. What do you think?
> I think that this would be a good idea.
I think that's good, too.
BTW, do you know that performing `gnus-mime-copy-part' on the pdf
part automatically launches the `doc-view-mode'? I.e., the pdf
file is viewed in an Emacs buffer. I think it would also be nice
if the `doc-view-mode' supports not only pdf/ps/dvi files but also
the types that OpenOffice supports. ;-)
Regards,
next prev parent reply other threads:[~2008-04-07 4:19 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-05 17:37 Reiner Steib
2008-04-07 3:50 ` Daniel Pittman
2008-04-07 4:19 ` Katsumi Yamaoka [this message]
2008-04-13 20:39 ` Reiner Steib
2008-04-08 16:22 ` Magnus Henoch
2008-04-08 17:05 ` Reiner Steib
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=b4my77qthyi.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).