From: Kai Grossjohann <grossjohann@amaunet.cs.uni-dortmund.de>
Cc: Hrvoje Niksic <hniksic@srce.hr>, ding@gnus.org
Subject: Re: custom and nnoo
Date: 21 Aug 1998 00:29:30 +0200 [thread overview]
Message-ID: <87ogtfs2wl.fsf@slowfox.do.uunet.de> (raw)
In-Reply-To: Simon Josefsson's message of "20 Aug 1998 21:53:59 +0200"
>>>>> Simon Josefsson <jas@pdc.kth.se> writes:
> Kai Grossjohann <grossjohann@amaunet.cs.uni-dortmund.de> writes:
>
> > In some cases, setting these `variables' via `setq' is sufficient.
> > For these cases it would be nice if one could use Custom, too.
>
> If this is enough, shouldn't the variable just be defvar'ed? The
> only point in defvoo'ing variables is to let them have different
> values for different servers. Or am I missing something?
I'm trying to say that there are variables where John just needs a
setq whereas Jill has different needs and therefore has different
values for different servers/groups.
Oops. I just thought that nnmail-expiry-wait would be a likely
candidate, but now I see that it is defcustom'd. Hm. Does that mean
that one can't put nnmail-expiry-wait in the group parameters?
Maybe I ran down the wrong track there? Can anyone enlighten me?
kai
--
OOP: object oriented programming; OOPS: object oriented mistakes
next prev parent reply other threads:[~1998-08-20 22:29 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
1998-08-20 15:59 Kai Grossjohann
1998-08-20 16:48 ` Hrvoje Niksic
1998-08-20 17:03 ` Kai Grossjohann
1998-08-20 19:53 ` Simon Josefsson
1998-08-20 22:29 ` Kai Grossjohann [this message]
1998-08-21 0:02 ` Lars Magne Ingebrigtsen
1998-08-20 19:55 ` Lars Magne 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=87ogtfs2wl.fsf@slowfox.do.uunet.de \
--to=grossjohann@amaunet.cs.uni-dortmund.de \
--cc=ding@gnus.org \
--cc=hniksic@srce.hr \
/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).