From: "Brent B. Powers" <powers@ml.com>
Cc: ding@ifi.uio.no
Subject: Re: Feedback on new Customization
Date: Wed, 9 Oct 1996 18:22:32 -0400 [thread overview]
Message-ID: <199610092222.SAA08682@swapsdvlp02.ny-swaps-develop.ml.com> (raw)
In-Reply-To: <rjpw2sjlpb.fsf@kolmogorov.dina.kvl.dk>
Per Abrahamsen writes:
> From: Per Abrahamsen <abraham@dina.kvl.dk>
> To: ding@ifi.uio.no
> Subject: Re: Feedback on new Customization
> Date: 09 Oct 1996 15:45:04 +0200
>
>
> >>>>> "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.
Wouldn't it be lovely if one could have a custom-file attached to
particular customization groups? {ahem, hint, hint} In that way, I
could have my gnus stuff go to either .custom or .gnus, my
customization stuff go to .custom, et alia
>
> 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.
>
next prev parent reply other threads:[~1996-10-09 22:22 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 [this message]
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=199610092222.SAA08682@swapsdvlp02.ny-swaps-develop.ml.com \
--to=powers@ml.com \
--cc=ding@ifi.uio.no \
/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).