[Top][All Lists]

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

customize apparently (still) adds text to .emacs.elc rather than .emacs

From: Daniel Ortmann
Subject: customize apparently (still) adds text to .emacs.elc rather than .emacs
Date: Tue, 21 Nov 2000 11:31:11 -0600

This bug report will be sent to the Free Software Foundation,
 not to your local site managers!!
Please write in English, because the Emacs maintainers do not have
translators to read other languages for them.

In GNU Emacs 20.7.1 (rs6000-ibm-aix4.3.3.0, Motif)
 of Mon Nov 20 2000 on neon.rchland.ibm.com
configured using `configure  
--prefix=/afs/rch/rel/common/prod/ct/local/200011/rs_aix43 --with-x 

Please describe exactly what actions triggered the bug
and the precise symptoms of the bug:

- I have both .emacs and .emacs.elc files.
- "customize" settings saved for future settings are put (apparently) as text.
  into the .emacs.elc file rather than into the .emacs file.
- I think I reported this bug back on version 20.5a.

- customize saves correctly if only a .emacs file exists.  I will use this

- By the way, I did not test if the problem occurs if the .emacs file is named

Recent input:
C-n C-n C-n C-n C-n C-n C-l M-> C-x k return C-x 0 
M-> C-x 2 C-x o C-x 1 C-r s u M-> C-r c u s t o m - 
s e t - v a r i a C-r C-r C-r M-> C-x 2 M-v M-{ M-{ 
M-{ C-p C-p C-p C-p C-p C-p C-p C-p C-p C-p C-p C-p 
C-l C-x o C-x C-r . e m a c s . e l tab return M-> 
M-x b u g tab tab backspace backspace backspace r e 
tab o backspace p o tab r tab return

Recent messages:
Scanning buffer for index (  0%)
Scanning buffer for index ( 54%)
Scanning buffer for index (100%)
Making completion list...
Mark set [5 times]
Mark saved where search started
Mark set
Mark saved where search started
Mark set [2 times]
Making completion list... [2 times]

Daniel Ortmann, IBM Circuit Technology, Rochester, MN 55901-7829
address@hidden / internal 8.553.6795 / external 507.253.6795
address@hidden home 507.288.7732

"The answers are so simple, and we all know where to look,
but it's easier just to avoid the question." -- Kansas

reply via email to

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