unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Richard M Stallman <rms@gnu.org>
To: Xavier Maillard <xma@gnu.org>, 2222@emacsbugs.donarmstrong.com
Cc: 2222@emacsbugs.donarmstrong.com, jpff@codemist.co.uk
Subject: bug#2222: 23.0.90; Labels in RMAIL
Date: Mon, 16 Feb 2009 10:39:34 -0500	[thread overview]
Message-ID: <E1LZ5ZG-0000pu-IC@fencepost.gnu.org> (raw)
In-Reply-To: <200902142125.n1ELP8TW021246@zogzog.maillard.mobi> (message from Xavier Maillard on Sat, 14 Feb 2009 22:25:08 +0100)

    If it is correctly documented and the message is well identified,
    that would not hurt to have it visible. A message with a subject
    like "Special rmail message, do not delete" could be enough.

If Rmail adds this special message
only when the file has messages with labels,
and if the subject says it exists to record the labels,
I think it will be ok to show these messages.
This way, most users won't have these messages, and those who do
will recognize them as serving a specific useful purpose.

The subject could be "Rmail label list for completion".

To hide these messages poses a number of problems that each need
to be solved.  It is less reliable.

For instance, what happens if you concatenate two mbox files to make a
longer one, and the second one has one of these magic messages at the
front?  It will end up in the middle of the combined file.  If these
messages are normally visible, the user will understand how it got
there.  If they are normally hidden, this one will appear out of the
blue.  Or should Rmail be prepared to hide any number of such
messages?  Should it automatically delete any that appear other than
at the start of the file?

Another advantage of showing them is that you can delete them if you
wish.  There might be occasions when you don't want any magic added
message in your file.  If you delete it, it will stay deleted until
you read the file into Rmail once again, or use commands to manage
labels.






  reply	other threads:[~2009-02-16 15:39 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-02-14 21:25 bug#2222: 23.0.90; Labels in RMAIL Xavier Maillard
2009-02-16 15:39 ` Richard M Stallman [this message]
2009-02-16 19:36   ` Stefan Monnier
2009-02-17 12:13     ` Richard M Stallman
2009-02-17  2:57   ` Glenn Morris
2009-02-17 18:04     ` Richard M Stallman
  -- strict thread matches above, loose matches on Subject: below --
2009-02-19  0:24 Xavier Maillard
2009-02-17 23:55 Xavier Maillard
2009-02-18  3:02 ` Stefan Monnier
2009-02-17 23:55 Xavier Maillard
2009-02-12 23:25 Xavier Maillard
2009-02-12  6:20 jpff
2009-02-13  6:34 ` Richard M Stallman
2009-02-06 13:53 jpff
2009-02-11  3:59 ` Glenn Morris
2009-02-11 20:58   ` Richard M Stallman
2009-02-12  3:30     ` Glenn Morris

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=E1LZ5ZG-0000pu-IC@fencepost.gnu.org \
    --to=rms@gnu.org \
    --cc=2222@emacsbugs.donarmstrong.com \
    --cc=jpff@codemist.co.uk \
    --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).