Gnus development mailing list
 help / color / mirror / Atom feed
From: Robert Pluim <rpluim@gmail.com>
To: ding@gnus.org
Subject: Re: Date header rewrite
Date: Mon, 31 Jan 2011 12:30:45 +0100	[thread overview]
Message-ID: <pknaaihwbru.fsf@this.is.really.invalid> (raw)
In-Reply-To: <87r5btqrob.fsf@gnus.org>

Lars Ingebrigtsen <larsi@gnus.org> writes:

> Robert Pluim <rpluim@gmail.com> writes:
>
>> I had (gnus-treat-date-local 'head), which now seems to be ignored, I
>> had to do (setq gnus-article-date-headers '(local)) to get it back.
>
> `gnus-article-date-headers' is set from -date-local, etc, and if I try
> setting it, I get the expected result.
>
> Are you setting gnus-treat-date-local after loading gnus-art, by any
> chance? 

So this turned out to be because I'd set gnus-treat-date-local using
customize, which means this:

    (dolist (type types)
      (let ((variable (intern (format "gnus-treat-date-%s" type))))
	(when (and (boundp variable)
		   (symbol-value variable))

fails when doing the boundp test. Setting it with setq in .gnus.el makes
things work fine.

Whether customize should create variable bindings for variables that
don't exist is a question I'm not going to think about early on a Monday
morning :)

>> Just for fun, I tried:
>>
>> (setq gnus-article-date-headers '(local lapsed))
>>
>> which caused my CPU to overheat, and everything in a summary buffer to
>> become ridiculously slow.
>
> Should be fixed now.

Confirmed.

Robert




  reply	other threads:[~2011-01-31 11:30 UTC|newest]

Thread overview: 39+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-01-31  1:56 Lars Ingebrigtsen
2011-01-31  8:07 ` Francis Moreau
2011-01-31  9:38   ` Rupert Swarbrick
2011-01-31 10:34 ` Robert Pluim
2011-01-31 10:43   ` Lars Ingebrigtsen
2011-01-31 11:30     ` Robert Pluim [this message]
2011-02-01  1:55       ` Lars Ingebrigtsen
2011-02-01  7:42         ` Robert Pluim
2011-02-01 19:23         ` Eric S Fraga
2011-02-03  4:14           ` Lars Ingebrigtsen
2011-01-31 13:49 ` Greg Troxel
2011-02-01  1:07   ` Lars Ingebrigtsen
2011-02-01  1:47     ` Richard Riley
2011-02-01  2:04       ` Lars Ingebrigtsen
2011-02-01  2:25         ` Richard Riley
2011-02-01  2:38           ` Lars Ingebrigtsen
2011-02-01  2:44             ` Richard Riley
2011-02-01  3:10               ` Lars Ingebrigtsen
2011-02-01  6:41                 ` Richard Riley
2011-02-01 18:23   ` Philipp Haselwarter
2011-02-01  6:05 ` Michael Welsh Duggan
2011-02-01  6:14   ` Lars Ingebrigtsen
2011-02-01 17:05     ` James Cloos
2011-02-02 11:18       ` Francis Moreau
2011-02-01 18:54     ` Greg Troxel
2011-02-03  4:13       ` Lars Ingebrigtsen
2011-02-03 11:50         ` Greg Troxel
2011-02-01  8:11 ` Francis Moreau
2011-02-01  8:23   ` Robert Pluim
2011-02-01  9:17     ` Francis Moreau
2011-02-01 10:06       ` Tassilo Horn
2011-02-01 10:11         ` Francis Moreau
2011-02-01 10:19         ` Lars Ingebrigtsen
2011-02-01 10:08       ` Lars Ingebrigtsen
2011-02-01 10:11         ` Francis Moreau
2011-02-01 10:08       ` Robert Pluim
2011-02-01 10:09     ` Lars Ingebrigtsen
2011-02-01 11:15       ` Robert Pluim
2011-02-03  4:10         ` Lars 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=pknaaihwbru.fsf@this.is.really.invalid \
    --to=rpluim@gmail.com \
    --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).