>>>>> "Chris" == Chris Moore <[EMAIL PROTECTED]>
>>>>> on Wed, 24 Aug 2005 19:11:15 +0200 writes:
>> Because of my ~/.emacs and our site-local default.el are not
>> small and load dozens of other files, I'd need quite a bit of time
>> for producing a smallish "single-file" ~/.emacs which
>> reproduces the problem.
Chris> If you can't tell us how to reproduce the problem then we have no
Chris> chance of fixing it.
of course I know that ...
Chris> It's probably not as hard as you think to make a small .emacs that
Chris> reproduces the problem. Put a (setq debug-on-error t) at the top of
I have had this anyway, but it didn't really help together with
my "startup initialization mess" (;-)
Chris> ~/.emacs then start commenting out large sections of the .emacs until
Chris> you find a small version that shows the problem. Putting '( and
)
Chris> around a bunch of s-expressions acts as an effective 'block comment'.
Well, I've taken the time and have succeeded:
The following reproducibly produces the bug
emacs-22.0.50 -q -l emacs-22.0-bug.el &
where I've attached the emacs-22.0-bug.el file (in text/plain)
(setq debug-on-error t) ;-- reset at end...
;;; I now at least found that the problem starts exactly after
;;; these lines in ./default.el :
(add-hook 'font-lock-mode-hook 'turn-on-lazy-lock)
(setq font-lock-maximum-decoration t) ;-- MAXIMUM
;;; but these alone are not yet a problem ...
(setq-default transient-mark-mode t)
(setq-default mark-even-if-inactive t);-- new feature -- better ? --
(global-font-lock-mode t)
--
Ok, I hope this helps to pin it down and fix it!
BTW, thanks a lot for GNU emacs!! I've been using it since
version 18.55 and still ``couldn't live'' without it.
Martin Maechler, ETH Zurich
_______________________________________________
Emacs-pretest-bug mailing list
[email protected]
http://lists.gnu.org/mailman/listinfo/emacs-pretest-bug
