Gnus development mailing list
 help / color / mirror / Atom feed
From: Michael Piotrowski <mxp@dynalabs.de>
To: ding@gnus.org
Subject: Backslash in subject
Date: Mon, 09 Apr 2012 18:32:50 +0200	[thread overview]
Message-ID: <x61unweuh9.fsf@dynalabs.de> (raw)

Hi,

The subject

  ~(E)[\]] does not match "]"?

on the ast-users mailing list has repeatedly caused problems for me.
I'm using Ma Gnus v0.4 and GNU Emacs 24.0.93.1.

First, when fetching the batch of messages which contained this thread
from my POP3 server, all messages were written into
~/.emacs-mail-crash-box.  It's a good idea to save the data when a
problem occurs, but you have to know about .emacs-mail-crash-box,
because you're not notified.  So you wonder (a) where your mail has gone
and (b) why you can't fetch new mail.

Second, I tried to import the mail from .emacs-mail-crash-box into Gnus
by opening the file via G f.  However, this batch of mail also contained
several digests, and Gnus then showed me only the messages of the first
digest (as individual messages) and no other messages.  Again I wondered
where may mail had gone.

Eventually I was able to solve the problem by replacing \] with \\] in
.emacs-mail-crash-box and copying it to my local mailbox.  However, this
was a very unpleasant experience.

Now I wonder:

1. Is this a bug in Gnus?  It seems so.

2. Shouldn't users be informed when their mail is written into
   .emacs-mail-crash-box?

3. Is there a way to open an mbox file which contains digests as a
   foreign group?

This particular batch of mail does not contain any personal messages, so
I'd be happy to provide it for debugging.

Thanks in advance!

Best regards

-- 
Dr.-Ing. Michael Piotrowski, M.A.                   <mxp@dynalabs.de>
Public key at <http://www.dynalabs.de/mxp/pubkey.txt> (ID 0x1614A044)




             reply	other threads:[~2012-04-09 16:32 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-04-09 16:32 Michael Piotrowski [this message]
2012-04-10 18:47 ` Lars Magne Ingebrigtsen
2012-04-11 15:34   ` Michael Piotrowski

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=x61unweuh9.fsf@dynalabs.de \
    --to=mxp@dynalabs.de \
    --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).