Gnus development mailing list
 help / color / mirror / Atom feed
From: Raymond Scholz <rscholz@tzi.de>
Subject: Reply confusion with latest CVS
Date: 22 Apr 2000 13:59:14 +0200	[thread overview]
Message-ID: <m3g0seny7h.fsf@rscholz.dyndns.org> (raw)

Hi!

The latest CVS Gnus gets heavily confused on replies, follow-ups
etc. A reply (r) works like a wide reply (S w), if there isn't
anything to widen (i.e. there is only the From: header, no Cc:) no To:
header is inserted in message mode. Mails like these seem to vanish on
sending (they don't show up in my sendmail queue).

My previous CVS update with replies working was on Friday, 21st 10:30
p.m.

Um, Lars or any other Lisp guru, could you have a look at this?

Cheers,
  Ray
-- 
Raymond Scholz -*- rscholz@tzi.de -*- http://www.tzi.de/~rscholz/
FB 3 Informatik, Universität Bremen -*- PGP key available via WWW



             reply	other threads:[~2000-04-22 11:59 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-04-22 11:59 Raymond Scholz [this message]
2000-04-22 12:27 ` 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=m3g0seny7h.fsf@rscholz.dyndns.org \
    --to=rscholz@tzi.de \
    /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).