Gnus development mailing list
 help / color / mirror / Atom feed
From: Sam Steingold <sds@gnu.org>
Subject: Re: follow-up & CC
Date: Mon, 10 Nov 2003 14:26:57 -0500	[thread overview]
Message-ID: <uznf49g8u.fsf@gnu.org> (raw)
In-Reply-To: <v9r80ghx5m.fsf@marauder.physik.uni-ulm.de>

> * Reiner Steib <4.hpr.03.e.f@aheshrefcnz.qr> [2003-11-10 19:54:29 +0100]:
>
> I changed the doc-string to reflect the new behavior (any suggestions
> for better wording?):
>
> ,----[ C-h f message-insert-to RET ]
> | Insert a To header that points to the author of the article being replied to.
> | If the original author requested not to be sent mail, don't insert it.  With
> | the prefix argument FORCE, insert the header anyway.
> `----

Another suggested change: when there is no reasonable reply-to address,
`message-insert-to' will insert an empty "To: " field (like C-c C-f C-t
`message-goto-to' does), which is undesirable when `message-insert-to'
is run from `message-setup-hook'.

Maybe the following is even better?

(defun message-insert-to (&optional force)
  "Insert a To header that points to the author of the article being replied to.
If the original author requested not to be sent mail, the function signals
an error.
With the prefix argument FORCE, insert the header anyway."
  (interactive "P")
  (let* ((co (message-fetch-reply-field "mail-copies-to"))
         (dont (and co (or (equal (downcase co) "never")
                           (equal (downcase co) "nobody"))))
         (to (or (message-fetch-reply-field "mail-reply-to")
                 (message-fetch-reply-field "reply-to")
                 (message-fetch-reply-field "from"))))
    (when (and dont to)
      (message
       (if force
         "Ignoring the user request not to have copies sent via mail"
         "Complying with the user request not to have copies sent via mail")))
    (when (and force (not to))
      (error "no mail address in the article"))
    (when (and to (or force (not dont)))
      (message-carefully-insert-headers (list (cons 'To to))))))


-- 
Sam Steingold (http://www.podval.org/~sds) running w2k
<http://www.camera.org> <http://www.iris.org.il> <http://www.memri.org/>
<http://www.mideasttruth.com/> <http://www.honestreporting.com>
Only adults have difficulty with child-proof caps.




  parent reply	other threads:[~2003-11-10 19:26 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-11-10  1:18 Sam Steingold
2003-11-10 12:30 ` Reiner Steib
2003-11-10 14:47   ` Sam Steingold
2003-11-10 17:44     ` Reiner Steib
2003-11-10 18:04       ` Sam Steingold
2003-11-10 18:54         ` Reiner Steib
2003-11-10 19:12           ` Sam Steingold
2003-11-10 19:26           ` Sam Steingold [this message]
2003-11-10 20:26             ` Reiner Steib
2003-11-12 16:05               ` Sam Steingold
2003-11-12 16:54                 ` Reiner Steib
2003-11-12 18:36                   ` Sam Steingold
2003-11-12 20:00                     ` Reiner Steib
2003-11-12 21:13                       ` Sam Steingold
2003-11-18 16:05                         ` Reiner Steib
2003-11-18 18:50                           ` Sam Steingold
2003-11-18 19:57                             ` Reiner Steib
2003-11-18 20:47                               ` Sam Steingold
2004-01-03 14:07                                 ` Reiner Steib

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=uznf49g8u.fsf@gnu.org \
    --to=sds@gnu.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).