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

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

[Emacs-bug-tracker] bug#1246: closed (Bug : 23.0.60; "customize emacs" o


From: GNU bug Tracking System
Subject: [Emacs-bug-tracker] bug#1246: closed (Bug : 23.0.60; "customize emacs" overwrites "custom-set-variables" in .emacs)
Date: Sun, 10 Jul 2011 02:10:02 +0000

Your message dated Sat, 09 Jul 2011 22:09:03 -0400
with message-id <address@hidden>
and subject line Re: bug#1246: Bug : 23.0.60; "customize emacs" overwrites 
"custom-set-variables" in .emacs
has caused the GNU bug report #1246,
regarding Bug : 23.0.60; "customize emacs" overwrites "custom-set-variables" in 
.emacs
to be marked as done.

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


-- 
1246: http://debbugs.gnu.org/cgi/bugreport.cgi?bug=1246
GNU Bug Tracking System
Contact address@hidden with problems
--- Begin Message --- Subject: Bug : 23.0.60; "customize emacs" overwrites "custom-set-variables" in .emacs Date: Fri, 24 Oct 2008 20:30:38 -0400
I used the "customize emacs" options and made permanent changes
(regarding fonts if I remember correctly). Emacs
changed the .emacs file on disk and modified the
"custom-set-variables". The problem was that all the old
custom-set-variables (like tex-output-view-style and stuff) were
completely overwritten.

Don't know if this is intended but it's quite annoying.



--- End Message ---
--- Begin Message --- Subject: Re: bug#1246: Bug : 23.0.60; "customize emacs" overwrites "custom-set-variables" in .emacs Date: Sat, 09 Jul 2011 22:09:03 -0400 User-agent: Gnus (www.gnus.org), GNU Emacs (www.gnu.org/software/emacs/)
This absolutely isn't supposed to happen. The whole purpose of customize
would be defeated and there would be lots of bug reports.
But since there aren't lots of these reports, I'm afraid the problem
must have been something peculiar to your settings somehow.
(Random guess: maybe you had multiple custom-set-variables sections - as
it says there must be only one.)

Without a reproducible recipe showing us how you got into this state,
I'm afraid there is nothing we can do.

If you have such info, please reply and we can reopen this report.

You can view the whole report at http://debbugs.gnu.org/BUGNUMBER


--- End Message ---

reply via email to

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