Gnus development mailing list
 help / color / mirror / Atom feed
From: Wesley.Hardaker@sphys.unil.ch
Subject: Re: Feedback on new Customization
Date: 15 Oct 1996 08:38:49 +0100	[thread overview]
Message-ID: <qk2d8ykhe2e.fsf@iptsun2.unil.ch> (raw)
In-Reply-To: Per Abrahamsen's message of 11 Oct 1996 19:53:23 +0200

Per Abrahamsen <abraham@dina.kvl.dk> writes:

> Using groups would be the wrong mechanism.  Each customization option
> can belong to any number of groups, from zero and upward.  The same is
> true for the groups, so the result is not a nice hierarchy, but a
> directed graph.  It can even be cyclic.

Speaking of groups...

One of the problems with customization as exsists at the moment is
that you won't see new options until the appropriate file is
loaded...  IE, until a function is actually called and autoload loads
the file, the customization vars aren't found for that section.  

The only solution I can see for this is to define the groups in a
different file (all of them in one maybe) and then tell each group
which file to load when its visiblity is toggled...  Ugly...  Hard to
implement...  Makes you keep track of files when you shouldn't...
Bad...

Any other ideas?
Forget it?
Wes


  parent reply	other threads:[~1996-10-15  7:38 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1996-10-08 15:55 Lance A. Brown
1996-10-08 16:46 ` Richard Pieri
1996-10-08 23:43 ` Per Abrahamsen
1996-10-09  0:30   ` Raja R Harinath
1996-10-10  0:51     ` Problems w/ rgnus-0.49 and tm-7.89 (was Re: Feedback on new Customization) Raja R Harinath
1996-10-10  9:32       ` Jan Vroonhof
1996-10-09  9:47   ` Feedback on new Customization Wesley.Hardaker
1996-10-09 13:45     ` Per Abrahamsen
1996-10-09 22:22       ` Brent B. Powers
1996-10-10 10:11         ` Per Abrahamsen
1996-10-10 13:41         ` William Perry
1996-10-11 17:53           ` Per Abrahamsen
1996-10-11 22:30             ` William Perry
1996-10-15  7:38             ` Wesley.Hardaker [this message]
1996-10-15 11:49               ` Per Abrahamsen
1996-10-10  7:13       ` Wesley.Hardaker

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=qk2d8ykhe2e.fsf@iptsun2.unil.ch \
    --to=wesley.hardaker@sphys.unil.ch \
    /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).