From: Steven L Baur <steve@miranova.com>
Subject: Re: September Gnus v0.90 is released
Date: 21 May 1996 21:06:18 -0700 [thread overview]
Message-ID: <m2spctic79.fsf@deanna.miranova.com> (raw)
In-Reply-To: michael lamoureux's message of 21 May 1996 17:21:32 -0700
>>>>> "michael" == michael lamoureux <lamour@engin.umich.edu> writes:
michael> In several of my mail groups, the 'E' mark got removed from
michael> all of the messages somehow when I went from 0.86 to 0.90.
michael> All of the messages that had this happen showed up again in
michael> the summary buffer as if they were new mail.
What kind of mail group do you use? I haven't seen it in nnml.
michael> I think there's a typo in message.el. In my XEmacs 19.13
michael> installation it's mail-abbrevs not mail-abbrev.
Yup.
--
steve@miranova.com baur
Unsolicited commercial e-mail will be proofread for $250/hour.
Andrea Seastrand: For your vote on the Telecom bill, I will vote for anyone
except you in November.
next prev parent reply other threads:[~1996-05-22 4:06 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
1996-05-21 21:31 Lars Magne Ingebrigtsen
1996-05-22 0:21 ` michael lamoureux
1996-05-22 4:06 ` Steven L Baur [this message]
1996-05-22 12:17 ` michael lamoureux
1996-05-22 20:18 ` Steven L Baur
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=m2spctic79.fsf@deanna.miranova.com \
--to=steve@miranova.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).