Gnus development mailing list
 help / color / mirror / Atom feed
From: Per Abrahamsen <abraham@dina.kvl.dk>
Subject: Re: Feedback on new Customization
Date: 09 Oct 1996 15:45:04 +0200	[thread overview]
Message-ID: <rjpw2sjlpb.fsf@kolmogorov.dina.kvl.dk> (raw)
In-Reply-To: Wesley.Hardaker@sphys.unil.ch's message of 09 Oct 1996 10:47:32 +0100


>>>>> "WH" == Wesley Hardaker <Wesley.Hardaker@sphys.unil.ch> writes:

WH> You know, I hate things that modify my .emacs...  I hate using the
WH> 'save options' menu item for that reason.  Oh well, someday I had to
WH> give in (I did so for 'customize'...).  

RMS wanted it that way.  You can customize it though, by setting the
`custom-file' option.  You will then have to load the new custom file
from `.emacs' explicitly.

WH> However, it would be nice to have some more 'topics', I guess
WH> they're called, to seperate the different sections a bit more.

They are called customization groups.

WH> I don't know how difficult this is to do as I haven't glanced at
WH> the code at all.

I think you will find the code for adding customization support pretty
intuitive.  Maybe you could try to add customization support to
smiley.el?  I don't touch the files that don't have Lars as the
primary author, and would really appreciate if someone else would try
to use the custom API before it gets added to Emacs.

WH> IE, under gnus-summary you could have it divided a bit more into
WH> 'threads', 'hooks', 'display', 'scoring', etc...  

Yes.  I have just basically created one group per lisp file, since
that was the easiest to do.  But I hope someone will organize it a bit
further. 

WH> A decent plan would be to follow the info file(s) hierarchy, which
WH> would make using custom really cool if you were reading the manual
WH> at the same time!

Yes it is.  I also want to be able to attach info-links and perhaps
url-links to each option or group, but haven't figured out how to do
that without cluttering up the display even more.

I already dislike that the help button and the state button look too
similar, and too much like checkboxes.  How and where would a info
button fit?  And additionally, you might want to have multiple info
and url buttons.

At some point, you should be able to edit the options directly in the
online manual.

WH> Anyway, its probably too late to start adding more hierarchy huh?

No, it is quite easy to change.  You can also have the same options
appear in multiple groups, so there could be a `gnus-visual' group
containing all the faces.


  reply	other threads:[~1996-10-09 13:45 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 [this message]
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
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=rjpw2sjlpb.fsf@kolmogorov.dina.kvl.dk \
    --to=abraham@dina.kvl.dk \
    /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).