Gnus development mailing list
 help / color / mirror / Atom feed
From: Shenghuo ZHU <zsh@cs.rochester.edu>
Subject: Re: Peculiar treatment of edited messages
Date: 24 Oct 1999 15:53:51 -0400	[thread overview]
Message-ID: <5bwvsch6wg.fsf@giga.cs.rochester.edu> (raw)
In-Reply-To: Dan Christensen's message of "Sun, 24 Oct 1999 14:29:17 -0400"

>>>>> "Dan" == Dan Christensen <jdc@jhu.edu> writes:

Dan> Dan Christensen <jdc@chow.mat.jhu.edu> writes:

>> Ted Stern <stern@tera.com> writes:

>>> In Pgnus 0.96, Emacs 20.3, I sometimes lose my email after editing
>>> my messages.  That is, my cursor sits on a message description in
>>> the *Summary* buffer, I hit 'e', and do some changes to the
>>> article.  When finished, I hit 'C-c C-c'.  But then Gnus puts a

[...]


>> I've had similar things happen, although if I remember correctly
>> the articles actually vanished from the nnfolder file as well, and
>> I had to get them from the Incoming directory.

Dan> This happened to me again today, so I can give a bit more info.
Dan> I had point in the *Article* buffer when I hit `e'; not sure if
Dan> that is relevant, but it might be.  What happened is that the
Dan> headers of the article in my nnfolder file got replaced by just
Dan> the headers I have displayed in the *Article* buffer:


[...]

Dan> Note that the "From " line is incorrect, and the various other
Dan> headers that Gnus makes use of (like X-Gnus-Mail-Source, Xref,
Dan> and X-Gnus-Article-Number) are all missing.  So as far as Gnus
Dan> can tell this article doesn't exist.

Right. Hitting `e' in *Article* buffer causes this problem. Besides,
it will not decode MIME either.

Different functions are called for hitting `e' in *Article* buffer and
*Summary* buffer. Therefore, I am wondering whether we should remove
function `gnus-article-edit' and use `gnus-summary-edit-article'
instead.

As a hot-fix, evaluating the following lines may help.

(gnus-define-keys gnus-article-mode-map 
        "e" gnus-article-read-summary-keys)

I am not sure what caused Ted's bug. Maybe the separating blank line.

To bring back those missing articles, I tried to move all articles in
the group to a temporary group, then rescan the group, and repeat
until no articles show in the group.  It was long time ago. I also am
not sure whether it works for Ted's situation.

-- 
Shenghuo ZHU


  reply	other threads:[~1999-10-24 19:53 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1999-10-19 18:16 Ted Stern
1999-10-20  2:24 ` Dan Christensen
1999-10-24 18:29   ` Dan Christensen
1999-10-24 19:53     ` Shenghuo ZHU [this message]
     [not found]       ` <yccbt9nmoes.fsf@orff.sea.tera.com>
1999-10-25 16:45         ` Shenghuo ZHU
1999-11-06 22:16       ` Lars Magne Ingebrigtsen

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=5bwvsch6wg.fsf@giga.cs.rochester.edu \
    --to=zsh@cs.rochester.edu \
    /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).