From: Dan Jacobson <jidanni@jidanni.org>
Subject: Re: message-shorten-references hardwired 21 references
Date: Tue, 10 Jan 2006 06:30:26 +0800 [thread overview]
Message-ID: <87psn1t4ot.fsf@jidanni.org> (raw)
In-Reply-To: <v9u0cikcau.fsf@marauder.physik.uni-ulm.de>
>> There should be a variable to allow users to have
>> message-shorten-references use less than the hardwired 21 references.
R> Please elaborate why you think this would be useful.
I want full control of my references. No "mother knows best". I feel
ashamed to send out bloated headers. I want to have tidy tiny spartan
headers.
>> Also are you sure you want the oldest 21 references, not the latest?
R> I'm quite sure that Gnus does the right thing. See section
R> "6.5. References" in [1].
It is permissible to not include the entire previous "References"
line if it is too long. An attempt should be made to include a
reasonable number of backwards references.
He just says "reasonable". I say that the newest 21 is the only way to
keep threads intact, vs. the oldest 21, no?
>> I want to just include the single very last reference but setting
>> maxcount to 1 gives just the earliest.
R> Mail or news?
mail. I didn't try news.
next prev parent reply other threads:[~2006-01-09 22:30 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <877j9fbsko.fsf@jidanni.org>
2006-01-05 13:57 ` Reiner Steib
2006-01-09 22:30 ` Dan Jacobson [this message]
2006-01-10 16:17 ` 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=87psn1t4ot.fsf@jidanni.org \
--to=jidanni@jidanni.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).