Using things from 'custom.el'

Using things from 'custom.el'

[Sharon Kimble]

[-- Attachment #1.1: Type: text/plain, Size: 463 bytes --]

I have this line in my 'custom.el' -  '(gnus-fetch-old-headers 300) but how do I
call it from within gnus please. I have several things that I have customised so
I would like to make full use of them, if only I knew how to include them in my
'.gnus.el'.

Thanks
Sharon.
-- 
A taste of linux = http://www.sharons.org.uk
my git repo = https://bitbucket.org/boudiccas/dots
TGmeds = http://www.tgmeds.org.uk
Debian testing, Fluxbox 1.3.5, emacs 24.3.1

[-- Attachment #1.2: Type: application/pgp-signature, Size: 818 bytes --]

Re: Using things from 'custom.el'

[Glyn Millington]

Sharon Kimble <boudiccas@talktalk.net> writes:

> gnus-fetch-old-headers

C-h v is your friend

,----
| Documentation:
| *Non-nil means that Gnus will try to build threads by grabbing old headers.
| If an unread article in the group refers to an older, already
| read (or just marked as read) article, the old article will not
| normally be displayed in the Summary buffer.  If this variable is
| t, Gnus will attempt to grab the headers to the old articles, and
| thereby build complete threads.  If it has the value `some', all
| old headers will be fetched but only enough headers to connect
| otherwise loose threads will be displayed.  This variable can
| also be a number.  In that case, no more than that number of old
| headers will be fetched.  If it has the value `invisible', all
| old headers will be fetched, but none will be displayed.
| 
| The server has to support NOV for any of this to work.
| 
| This feature can seriously impact performance it ignores all
| locally cached header entries.  Setting it to t for groups for a
| server that doesn't expire articles (such as news.gmane.org),
| leads to very slow summary generation.
`----

atb




Glyn

Re: Using things from 'custom.el'

[Michael Heerdegen]

Sharon Kimble <boudiccas@talktalk.net> writes:

> I have this line in my 'custom.el' - '(gnus-fetch-old-headers 300) but
> how do I call it from within gnus please.

For variables, in 99% of the cases, setq-default is the right thing to
use - in your case, for example, just

    (setq-default gnus-fetch-old-headers 300)

In very rare cases, custom uses a specialized setter function and using
just setq-default won't work.

BTW, `setq-default' is like `setq', but always sets the default
(i.e. the global) binding of a variable even when it is buffer local.

Michael.