Gnus development mailing list
 help / color / mirror / Atom feed
From: Ted Stern <stern@tera.com>
Subject: Peculiar treatment of edited messages
Date: 19 Oct 1999 11:16:51 -0700	[thread overview]
Message-ID: <yccogdvkygc.fsf@orff.sea.tera.com> (raw)

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 'G' on the message summary, indicating that
it is about to be purged from the group.  When I exit the group and re-enter
it using 'C-u SPC', the edited message has disappeared, although other
messages are unaffected.

If I use 'more' or some other editor to actually look through the nnfolder
corresponding to the nnfolder group, the message is still there.  But Gnus no
longer acknowledges this -- how can I get Gnus to re-read all headers in the
nnfolder file?

Oddly enough, there was a message that disappeared this way 2 months ago in my
mail.misc folder, but it recently reappeared.  I have no idea what I did to
bring it back, although 2 months ago I was using pgnus 0.95 vs. 0.96.

Restarting Gnus doesn't seem to help.

Any ideas?  One thing I am thinking is that the email could be getting screwed
up because my write-file-hooks contains functions to remove trailing blanks
and trailing empty newlines.

Ted
-- 
 Tera Computer Company                                   http://www.tera.com
 411 First Avenue South, Suite 600        Direct 206/701-2182, Main 701-2000
 Seattle, WA 98104-2860                   Fax1   206/701-2205, Fax2 701-2500


             reply	other threads:[~1999-10-19 18:16 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1999-10-19 18:16 Ted Stern [this message]
1999-10-20  2:24 ` Dan Christensen
1999-10-24 18:29   ` Dan Christensen
1999-10-24 19:53     ` Shenghuo ZHU
     [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=yccogdvkygc.fsf@orff.sea.tera.com \
    --to=stern@tera.com \
    /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).