From: Reiner Steib <reinersteib+gmane@imap.cc>
Subject: Re: message-shorten-references hardwired 21 references
Date: Tue, 10 Jan 2006 17:17:36 +0100 [thread overview]
Message-ID: <v97j98ukf3.fsf@marauder.physik.uni-ulm.de> (raw)
In-Reply-To: <87psn1t4ot.fsf@jidanni.org>
On Mon, Jan 09 2006, Dan Jacobson wrote:
> 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".
And "if it is too long".
> I say that the newest 21 is the only way to keep threads intact,
> vs. the oldest 21, no?
You've misread the code. It keeps the first MID and the last 20 MIDs:
ELISP> (setq rs-test "<id-1@invalid> <id-2@invalid> ...
... <id-89@invalid> <id-90@invalid>")
ELISP> (with-temp-buffer
(message-shorten-references 'References rs-test)
(buffer-string))
"References: <id-1@invalid> <id-71@invalid> <id-72@invalid> ...
... <id-88@invalid> <id-89@invalid> <id-90@invalid>"
Bye, Reiner.
--
,,,
(o o)
---ooO-(_)-Ooo--- | PGP key available | http://rsteib.home.pages.de/
prev parent reply other threads:[~2006-01-10 16:17 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
2006-01-10 16:17 ` Reiner Steib [this message]
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=v97j98ukf3.fsf@marauder.physik.uni-ulm.de \
--to=reinersteib+gmane@imap.cc \
--cc=Reiner.Steib@gmx.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).