comparison man/custom.texi @ 90066:fb79180b618d

Revision: [e-mail]--gnu-2004/emacs--unicode--0--patch-78 Merge from emacs--cvs-trunk--0 Patches applied: * [e-mail]--gnu-2004/emacs--cvs-trunk--0--patch-719 - [e-mail]--gnu-2004/emacs--cvs-trunk--0--patch-732 Update from CVS * [e-mail]--gnu-2004/emacs--cvs-trunk--0--patch-733 Update from CVS: man/calc.texi: Fix some TeX definitions. * [e-mail]--gnu-2004/emacs--cvs-trunk--0--patch-734 Merge from gnus--rel--5.10 * [e-mail]--gnu-2004/gnus--rel--5.10--patch-75 Merge from emacs--cvs-trunk--0 * [e-mail]--gnu-2004/gnus--rel--5.10--patch-76 - [e-mail]--gnu-2004/gnus--rel--5.10--patch-77 Update from CVS

90065:c26eb15cd14a

@c This is part of the Emacs manual.
@c Copyright (C) 1985,86,87,93,94,95,97,2000,2001,2002
@c  Free Software Foundation, Inc.
@c See file emacs.texi for copying conditions.
@node Customization, Quitting, Amusements, Top
@chapter Customization
@cindex customization

@vindex custom-file
  The customization buffer normally saves customizations in
@file{~/.emacs}.  If you wish, you can save customizations in another
file instead.  To make this work, your @file{~/.emacs} should set
@code{custom-file} to the name of that file.  Emacs loads the file
right after your @file{.emacs} if you did not load it already.  For
example:

@example
(setq custom-file "~/.emacs-custom")
@end example

  The variable @code{custom-file} is useful if you want to have
different customizations for different Emacs versions:

@example
(if (< emacs-major-version 21)
    ;; @r{Emacs 20 customization.}
    (setq custom-file "~/.custom-20.el")
  ;; @r{Emacs 21 customization.}
  (setq custom-file "~/.custom-21.el"))
@end example

  If Emacs was invoked with the @option{-q} or @option{--no-init-file}
options (@pxref{Initial Options}), it will not let you save your
customizations in your @file{~/.emacs} init file.  This is because

90066:fb79180b618d

@c This is part of the Emacs manual.
@c Copyright (C) 1985,86,87,93,94,95,97,2000,2001,2002,2004
@c  Free Software Foundation, Inc.
@c See file emacs.texi for copying conditions.
@node Customization, Quitting, Amusements, Top
@chapter Customization
@cindex customization

@vindex custom-file
  The customization buffer normally saves customizations in
@file{~/.emacs}.  If you wish, you can save customizations in another
file instead.  To make this work, your @file{~/.emacs} should set
@code{custom-file} to the name of that file.  If you are using Emacs
version 21.4 or later, Emacs loads the file right after your
@file{.emacs} if you did not load it already.  In earlier versions,
you have to load the file in your @file{~/emacs}.  If you customize
@code{custom-file} through the @samp{Customize} interface, you still
need to load it in your @file{.emacs}, but there is no need to set
it.  For example:

@example
;; @r{if not set through the @samp{Customize} interface:}
(setq custom-file "~/.emacs-custom")

;; @r{in Emacs versions before 21.4 or if set through}
;; @r{the @samp{Customize} interface.}
(load "~/.emacs-custom")
@end example

  You can also use @code{custom-file} to specify different
customization files for different Emacs versions, like this:

@example
(cond ((< emacs-major-version 21)
       ;; @r{Emacs 20 customization.}
       (setq custom-file "~/.custom-20.el"))
      ((and (= emacs-major-version 21) (< emacs-minor-version 4))
       ;; @r{Emacs 21 customization, before version 21.4.}
       (setq custom-file "~/.custom-21.el"))
      (t
       ;; @r{Emacs version 21.4 or later.}
       (setq custom-file "~/.custom-21.4.el")))

(load custom-file)
@end example

  If Emacs was invoked with the @option{-q} or @option{--no-init-file}
options (@pxref{Initial Options}), it will not let you save your
customizations in your @file{~/.emacs} init file.  This is because