From: "Adam Sjøgren" <asjo@koldfront.dk>
To: ding@gnus.org
Subject: Re: gnus-article-date-headers, new type "combined-local"?
Date: Thu, 11 Apr 2019 19:55:24 +0200 [thread overview]
Message-ID: <87v9zkfmur.fsf@tullinup.koldfront.dk> (raw)
In-Reply-To: <87d0lse91o.fsf@igel.home>
Andreas writes:
> On Apr 11 2019, Adam Sjøgren <asjo@koldfront.dk> wrote:
>
>> It looks like adding that would be another type in
>> article-make-date-line, say combined-local.
>>
>> What do you think, would it make sense to add that, or is there an
>> "easier" way?
>
> Try 'user-defined.
The documentation of gnus-article-date-headers says:
‘user-defined’ (a user-defined format defined by the
‘gnus-article-time-format’ variable).
which is almost as information-free as your answer.
The default value of gnus-article-time-format is "%a, %d %b %Y %T %Z".
To implement combined-lapsed, I find this piece of code:
((eq type 'combined-lapsed)
(let ((date-string (article-make-date-line date 'original))
(segments 3)
lapsed-string)
(while (and
time
(setq lapsed-string
(concat " (" (article-lapsed-string time segments) ")"))
(> (+ (length date-string)
(length lapsed-string))
(+ fill-column 6))
(> segments 0))
(setq segments (1- segments)))
(if (> segments 0)
(concat date-string lapsed-string)
date-string)))
Which kind of makes me think that it probably can't be done with a
user-defined string.
Maybe it really is trivial using 'user-defined, it's hard to tell from
your reply.
Best regards,
Adam
--
"Everything needs to change. Adam Sjøgren
And it has to start today." asjo@koldfront.dk
next prev parent reply other threads:[~2019-04-11 17:55 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-11 7:51 Adam Sjøgren
2019-04-11 17:38 ` Andreas Schwab
2019-04-11 17:55 ` Adam Sjøgren [this message]
2019-04-11 19:31 ` Andreas Schwab
2019-04-11 19:33 ` Adam Sjøgren
2019-04-11 20:02 ` Andreas Schwab
2019-06-22 10:52 ` Lars Ingebrigtsen
2019-07-20 9:50 ` [PATCH] Add new gnus-article-date-headers option combined-local-lapsed Adam Sjøgren
2019-07-20 13:02 ` Lars Ingebrigtsen
2019-07-20 13:16 ` Adam Sjøgren
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=87v9zkfmur.fsf@tullinup.koldfront.dk \
--to=asjo@koldfront.dk \
--cc=ding@gnus.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).