From: deskpot@myrealbox.com (Vasily Korytov)
Subject: [patch] gnus-boring-article-headers: introducing broken-reply-to
Date: Sun, 09 Mar 2003 16:07:13 +0300 [thread overview]
Message-ID: <87adg4pu2m.fsf@unix.home> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 245 bytes --]
This removes the Reply-To header on groups, that have (broken-reply-to .
t).
lisp/ChangeLog
2003-03-09 Vasily Korytov <deskpot@myrealbox.com>
* gnus-art.el (gnus-boring-article-headers): New value, on by
default: 'broken-reply-to
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1.2: source patch --]
[-- Type: text/x-patch, Size: 2291 bytes --]
--- lisp/gnus-art.el~ Fri Mar 7 10:39:27 2003
+++ lisp/gnus-art.el Sun Mar 9 15:52:15 2003
@@ -178,22 +178,26 @@
:type '(repeat regexp)
:group 'gnus-article-hiding)
-(defcustom gnus-boring-article-headers '(empty followup-to reply-to)
+(defcustom gnus-boring-article-headers '(empty broken-reply-to
+ followup-to reply-to)
"Headers that are only to be displayed if they have interesting data.
Possible values in this list are:
- 'empty Headers with no content.
- 'newsgroups Newsgroup identical to Gnus group.
- 'to-address To identical to To-address.
- 'to-list To identical to To-list.
- 'cc-list CC identical to To-list.
- 'followup-to Followup-to identical to Newsgroups.
- 'reply-to Reply-to identical to From.
- 'date Date less than four days old.
- 'long-to To and/or Cc longer than 1024 characters.
- 'many-to Multiple To and/or Cc."
+ 'empty Headers with no content.
+ 'newsgroups Newsgroup identical to Gnus group.
+ 'broken-reply-to Reply-To in groups with (broken-reply-to . t).
+ 'to-address To identical to To-address.
+ 'to-list To identical to To-list.
+ 'cc-list CC identical to To-list.
+ 'followup-to Followup-to identical to Newsgroups.
+ 'reply-to Reply-to identical to From.
+ 'date Date less than four days old.
+ 'long-to To and/or Cc longer than 1024 characters.
+ 'many-to Multiple To and/or Cc."
:type '(set (const :tag "Headers with no content." empty)
(const :tag "Newsgroups identical to Gnus group." newsgroups)
+ (const :tag "Reply-To in groups with (broken-reply-to . t)."
+ broken-reply-to)
(const :tag "To identical to To-address." to-address)
(const :tag "To identical to To-list." to-list)
(const :tag "CC identical to To-list." cc-list)
@@ -1604,6 +1608,10 @@
gnus-newsgroup-name
"")))
(gnus-article-hide-header "newsgroups")))
+ ((eq elem 'broken-reply-to)
+ (if (gnus-group-find-parameter
+ gnus-newsgroup-name 'broken-reply-to)
+ (gnus-article-hide-header "reply-to")))
((eq elem 'to-address)
(let ((to (message-fetch-field "to"))
(to-address
[-- Attachment #1.3: Type: text/plain, Size: 151 bytes --]
texi/ChangeLog
2003-03-09 Vasily Korytov <deskpot@myrealbox.com>
* gnus.texi: New value for gnus-boring-article-headers --
'broken-reply-to
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1.4: info patch --]
[-- Type: text/x-patch, Size: 904 bytes --]
--- texi/gnus.texi~ Fri Mar 7 10:39:30 2003
+++ texi/gnus.texi Sun Mar 9 16:06:00 2003
@@ -10535,6 +10535,8 @@
@item newsgroups
Remove the @code{Newsgroups} header if it only contains the current group
name.
+@item broken-reply-to
+Remove the @code{Reply-To} header if the group has (broken-reply-to . t).
@item to-address
Remove the @code{To} header if it only contains the address identical to
the current groups's @code{to-address} parameter.
@@ -10553,11 +10555,11 @@
Remove all @code{To} headers if there are more than one.
@end table
-To include these three elements, you could say something like:
+To include these four elements, you could say something like:
@lisp
(setq gnus-boring-article-headers
- '(empty followup-to reply-to))
+ '(empty broken-reply-to followup-to reply-to))
@end lisp
This is also the default value for this variable.
[-- Attachment #1.5: Type: text/plain, Size: 363 bytes --]
P.S. My copyright assignment process is delayed for some time (which is
no way a fault of the FSF people). Hoping, that's OK. If not, don't
apply this, but let me know and I'll draw a patch, when everything is
done.
--
I accept RFC3156 and RFC1991-compatible encrypted mail.
PGP key fingerprint: 123A 7CCE 6E26 6233 0D87 E01A A0F8 3524 FCD8 1841
[-- Attachment #2: Type: application/pgp-signature, Size: 188 bytes --]
next reply other threads:[~2003-03-09 13:07 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-09 13:07 Vasily Korytov [this message]
2003-03-31 16:58 ` 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=87adg4pu2m.fsf@unix.home \
--to=deskpot@myrealbox.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).