custom and nnoo

custom and nnoo

[Kai Grossjohann]

Can one do custom with nnoo?  Currently, I have `defvoo' in my Gnus
backend, but of course one would like to be able to change these
variables with Custom.  Using `defcustom' instead would mean that
these variables are un-noo'd.

Is there a `defcoostom'?

kai
-- 
OOP: object oriented programming;  OOPS: object oriented mistakes

Re: custom and nnoo

[Hrvoje Niksic]

Kai Grossjohann <grossjohann@amaunet.cs.uni-dortmund.de> writes:

> Can one do custom with nnoo?  Currently, I have `defvoo' in my Gnus
> backend, but of course one would like to be able to change these
> variables with Custom.  Using `defcustom' instead would mean that
> these variables are un-noo'd.
> 
> Is there a `defcoostom'?

If I understand nnoo correctly, a `defcoostom' would be meaningless
because `defvoo'ed variables aren't really variables, but server
parameters (or something like that.)  They can change whenever you
change the server in Gnus, for instance.

-- 
Hrvoje Niksic <hniksic@srce.hr> | Student at FER Zagreb, Croatia
--------------------------------+--------------------------------
We are all just prisoners here of our own MAKEDEV.

Re: custom and nnoo

[Kai Grossjohann]

>>>>> Hrvoje Niksic <hniksic@srce.hr> writes:

  > If I understand nnoo correctly, a `defcoostom' would be
  > meaningless because `defvoo'ed variables aren't really variables,
  > but server parameters (or something like that.)  They can change
  > whenever you change the server in Gnus, for instance.

In some cases, setting these `variables' via `setq' is sufficient.
For these cases it would be nice if one could use Custom, too.

Of course, if there was a way to customize a server similar, like
there is a command `G c' to customize a group, that would be even
better.  But item # 1 is useful without this, regardless.

kai
-- 
OOP: object oriented programming;  OOPS: object oriented mistakes

Re: custom and nnoo

[Simon Josefsson]

Kai Grossjohann <grossjohann@amaunet.cs.uni-dortmund.de> writes:

>   > If I understand nnoo correctly, a `defcoostom' would be
>   > meaningless because `defvoo'ed variables aren't really variables,
>   > but server parameters (or something like that.)  They can change
>   > whenever you change the server in Gnus, for instance.
> 
> 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?

(And if you defvar it you can, of course, defcustom it...)

Re: custom and nnoo

[Kai Grossjohann]

>>>>> 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

Re: custom and nnoo

[Lars Magne Ingebrigtsen]

Kai Grossjohann <grossjohann@amaunet.cs.uni-dortmund.de> writes:

> 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?

It's fine in the group params, but it's not a server variable. 

-- 
(domestic pets only, the antidote for overdose, milk.)
  larsi@gnus.org * Lars Magne Ingebrigtsen

Re: custom and nnoo

[Lars Magne Ingebrigtsen]

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.

setq only (reliably) modifies the default value of nnoo
"variables".  Trying to modify these with setq after Gnus has been
loaded is usually futile.

-- 
(domestic pets only, the antidote for overdose, milk.)
  larsi@gnus.org * Lars Magne Ingebrigtsen