Mercurial > emacs
comparison admin/FOR-RELEASE @ 61602:71c8a6678c21
*** empty log message ***
author | Richard M. Stallman <rms@gnu.org> |
---|---|
date | Sun, 17 Apr 2005 16:04:44 +0000 |
parents | 818ed72fc2d1 |
children | bee2af4a7427 2c2b97b30980 e1fbb019c538 |
comparison
equal
deleted
inserted
replaced
61601:aaa0bead8bc5 | 61602:71c8a6678c21 |
---|---|
78 Redisplay may loop if there is an error in some display property, e.g. | 78 Redisplay may loop if there is an error in some display property, e.g. |
79 (space 'left-margin) | 79 (space 'left-margin) |
80 | 80 |
81 A fix would be to somehow disable handling of display properties if an error | 81 A fix would be to somehow disable handling of display properties if an error |
82 is encountered. | 82 is encountered. |
83 | |
84 | |
85 ** custom mode-line face makes Emacs freeze up | |
86 | |
87 From: Stephen Berman <Stephen.Berman@gmx.net> | |
88 Date: Sun, 24 Oct 2004 02:08:56 +0200 | |
89 | |
90 1. Start Emacs with -q -no-site-file. | |
91 | |
92 2. Type `M-x customize-face' and at the prompt `mode-line'. | |
93 | |
94 3. In the Custom buffer for mode-line face | |
95 a. check width and give it the value `narrow'; | |
96 b. check height and give it the value 120 in 1/10 pt; | |
97 c. check underline and give it the value `on' (or `colored'); | |
98 d. check overline and give it the value `on' (or `colored'). | |
99 | |
100 4. Set for current session. | |
101 | |
102 5. Invoke Ediff on any two files. | |
103 | |
104 6. Now Emacs is frozen and consumes 95-99% of CPU. | |
105 | |
106 The customizations in step 3 appear to be the minimum necessary to | |
107 induce this bug. Leave out any one of them and Ediff runs without a | |
108 problem. Also if the 1/10 point value of height is 130 or greater | |
109 there's no bug (with the default font family; with e.g. Helvetica the | |
110 bug is induced only by a value of 100 or less). | |
111 | |
112 I've noticed this freeze up only when invoking Ediff. The only thing | |
113 I've been able to do is kill Emacs externally, via top or with kill | |
114 when run in gdb, after interrupting. When the freeze up happens | |
115 within a gdb session, there is no automatic debugging feedback. After | |
116 interrupting I can get a backtrace, here's an example: | |
117 | |
118 Update: Maybe only reveals itself when compiled with GTK+ | |
119 | 83 |
120 | 84 |
121 * DOCUMENTATION | 85 * DOCUMENTATION |
122 | 86 |
123 ** Document Custom Themes. | 87 ** Document Custom Themes. |