unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: "Jeff Dwork" <jeff.dwork@amd.com>
Cc: eddy@opera.no
Subject: Re: customize
Date: Thu, 25 Jul 2002 14:02:09 -0700	[thread overview]
Message-ID: <15680.26449.937153.817907@localhost.localdomain> (raw)
In-Reply-To: <E17SgpB-0003rO-00@whorl.intern.opera.no>

Customizing custom-file will fix this:

 M-x customize-option RET custom-file RET

I changed mine to ~/.emacs-customize and have 
  (load (expand-file-name "~/.emacs-customize"))
in my ~/.emacs where I want it, so I can run both 19.34 and 21.1
without confusing 19.34.

IMHO, custom-file should have a prominent mention in the manual and
the top level customize group.  I found it by reading cus-edit.el.

IMVHO, the default behavior of customize should be to save to a file
different from user-init-file.  When saving, customize would scan
user-init-file looking for (load (expand-file-name "custom-file")).
If it is not found, customize offers to modify user-init-file, with
allowable responses of "yes", "no" and "no and do not ask again" (the
last being saved as a customization).  I believe this will make life
easier for both novices and experts new to emacs >19.

Jeff

Edward Welbourne writes:
 > To: rms@gnu.org
 > cc: bug-gnu-emacs@gnu.org
 > Subject: Re: customize
 > Date: Thu, 11 Jul 2002 18:29:49 +0200
 > 
...
 > 
 > All customize-cruft is appended to ~/.emacs, while my own config is
 > accessed via a line early in the file (which loads it from some
 > byte-compiled elisp in a conveniently out-of-the-way directory).  Thus
 > my own config can't control the face, because customize insists on
 > having the last word (and saying: suppress this face) despite my best
 > efforts to get the fancy GUI to understand that I no longer want
 > customize to have anything to do with the setting of this face.
 > 
...
 > 
 > 	Eddy.
 > 
 > _______________________________________________
 > Bug-gnu-emacs mailing list
 > Bug-gnu-emacs@gnu.org
 > http://mail.gnu.org/mailman/listinfo/bug-gnu-emacs

-- 
Jeff Dwork                      |           jeff.dwork@amd.com
Advanced Micro Devices, M/S 45  | 408-749-5216 (voice) 408-774-8448 (fax)
PO Box 3453                     |----------------------------------------
Sunnyvale, Ca 94088-3453        | 

  reply	other threads:[~2002-07-25 21:02 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-07-10 16:51 customize Edward Welbourne
2002-07-11 12:01 ` customize Richard Stallman
2002-07-11 16:29   ` customize Edward Welbourne
2002-07-25 21:02     ` Jeff Dwork [this message]
2002-07-30 15:44   ` customize Edward Welbourne

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

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=15680.26449.937153.817907@localhost.localdomain \
    --to=jeff.dwork@amd.com \
    --cc=eddy@opera.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.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

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 read-only IMAP folder(s) and NNTP newsgroup(s).