From: "Alfred M\. Szmidt" <ams@gnu.org>
To: Xavier Maillard <xma@gnu.org>
Cc: cyd@stupidchicken.com, stephen@xemacs.org, rms@gnu.org,
emacs-devel@gnu.org
Subject: Re: Recognize mbox files?
Date: Sat, 14 Feb 2009 22:52:30 +0100 [thread overview]
Message-ID: <1234648350.475573.8599.nullmailer@beryx.hq.kred> (raw)
In-Reply-To: message from Xavier Maillard on Sat, 14 Feb 2009 22:25:12 +0100
A better idea would be for Rmail to detect whether it has
already munged the file (a quick grep for "^X-RMAIL-.*"
headers should do) and if not make the buffer read-only.
That sounds like a good idea. It should be enough to check the
first message for that header, since a previous visit with Rmail
will necessarily have displayed the first message and put that
header into it.
This mbox detection problem sounds like what we are trying to solve
with bug#2222 (Labels). Launching rmail would automatically add a
message on top of the mbox file, adding special rmail headers and
thus making this mbox file detection really easy (if grepping for
rmail headers on the first message). We would have solved two
problems that way. I am strongly in favour of this approach. Still
we need to find a consensus to the question: to hide or not to
hide.
How would thiis work for "C-x C-f ~/RMAIL.foo"? Is the suggestion to
do this check on all files one opens? I think this would be very
bad...
Using file variables is the right solution.
next reply other threads:[~2009-02-14 21:52 UTC|newest]
Thread overview: 45+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-14 21:52 Alfred M. Szmidt [this message]
-- strict thread matches above, loose matches on Subject: below --
2009-02-18 16:57 Recognize mbox files? Alfred M. Szmidt
2009-02-17 23:55 Xavier Maillard
2009-02-17 23:55 Xavier Maillard
2009-02-17 15:27 Alfred M. Szmidt
2009-02-17 16:36 ` Stefan Monnier
2009-02-18 3:27 ` Stephen J. Turnbull
2009-02-18 3:39 ` Miles Bader
2009-02-18 4:18 ` Stephen J. Turnbull
2009-02-18 12:10 ` Richard M Stallman
2009-02-18 12:09 ` Richard M Stallman
2009-02-17 13:10 Alfred M. Szmidt
2009-02-17 14:17 ` Stephen J. Turnbull
2009-02-18 12:10 ` Richard M Stallman
2009-02-16 16:12 Alfred M. Szmidt
2009-02-17 12:13 ` Richard M Stallman
2009-02-14 21:25 Xavier Maillard
2009-02-14 22:51 ` Stefan Monnier
2009-02-16 15:40 ` Richard M Stallman
2009-02-14 21:25 Xavier Maillard
2009-02-13 8:25 Alfred M. Szmidt
2009-02-12 8:16 Alfred M. Szmidt
2009-02-13 6:33 ` Richard M Stallman
2009-02-12 7:45 Alfred M. Szmidt
2009-02-10 7:36 Alfred M. Szmidt
2009-02-09 18:38 Alfred M. Szmidt
2009-02-10 1:34 ` Stefan Monnier
2009-02-10 9:36 ` Eli Zaretskii
2009-02-10 20:02 ` Richard M Stallman
2009-02-11 0:34 ` Chetan Pandya
2009-02-11 20:58 ` Richard M Stallman
2009-02-11 4:51 ` Stephen J. Turnbull
2009-02-11 20:18 ` Eli Zaretskii
2009-02-12 1:59 ` Stefan Monnier
2009-02-12 4:09 ` Eli Zaretskii
2009-02-12 5:15 ` Stefan Monnier
2009-02-12 2:40 ` Stephen J. Turnbull
2009-02-11 20:59 ` Richard M Stallman
2009-02-09 5:31 Richard M Stallman
2009-02-09 18:17 ` Chong Yidong
2009-02-09 19:09 ` Harald Hanche-Olsen
2009-02-09 21:26 ` Reiner Steib
2009-02-09 22:06 ` Eli Zaretskii
2009-02-09 22:35 ` Reiner Steib
2009-02-10 8:34 ` Eli Zaretskii
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1234648350.475573.8599.nullmailer@beryx.hq.kred \
--to=ams@gnu.org \
--cc=cyd@stupidchicken.com \
--cc=emacs-devel@gnu.org \
--cc=rms@gnu.org \
--cc=stephen@xemacs.org \
--cc=xma@gnu.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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).