emacs-bug-tracker
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Emacs-bug-tracker] bug#5531: closed (23.1.92; .emacs-custom.el read des


From: GNU bug Tracking System
Subject: [Emacs-bug-tracker] bug#5531: closed (23.1.92; .emacs-custom.el read despite presence of .elc)
Date: Sat, 09 Jul 2011 22:38:02 +0000

Your message dated Sat, 09 Jul 2011 18:36:55 -0400
with message-id <address@hidden>
and subject line Re: bug#5531: 23.1.92; .emacs-custom.el read despite presence 
of .elc
has caused the GNU bug report #5531,
regarding 23.1.92; .emacs-custom.el read despite presence of .elc
to be marked as done.

(If you believe you have received this mail in error, please contact
address@hidden)


-- 
5531: http://debbugs.gnu.org/cgi/bugreport.cgi?bug=5531
GNU Bug Tracking System
Contact address@hidden with problems
--- Begin Message --- Subject: 23.1.92; .emacs-custom.el read despite presence of .elc Date: Sat, 06 Feb 2010 01:42:49 +0800
view-echo-area-messages shows
  Loading /home/jidanni/.emacs-custom.el (source)...done
even though there is an .elc available. (Made by
(add-hook
 'emacs-lisp-mode-hook
 '(lambda ()
    (turn-on-auto-fill)
    (or (string-equal buffer-file-name "/home/jidanni/.newsrc.eld")
        (add-hook
         'after-save-hook
         '(lambda ()
            (byte-compile-file buffer-file-name)
            ) nil t))))
in my ~/.emacs.)




--- End Message ---
--- Begin Message --- Subject: Re: bug#5531: 23.1.92; .emacs-custom.el read despite presence of .elc Date: Sat, 09 Jul 2011 18:36:55 -0400 User-agent: Gnus (www.gnus.org), GNU Emacs (www.gnu.org/software/emacs/)
Presumably you have a

(load custom-file)

line in your .emacs, because that is the documented way to make the
feature work. Adjust it so that it looks like

(load (file-name-sans-extension custom-file))

It is not worth documenting this because byte-compiling your init files
is a bad idea that generally loses you time due to confusion (this is
documented).


--- End Message ---

reply via email to

[Prev in Thread] Current Thread [Next in Thread]