[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
"Invalid input style"
From: |
Daniel Ortmann |
Subject: |
"Invalid input style" |
Date: |
Tue, 21 Nov 2000 10:54:40 -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
--with-x-toolkit=motif'
Please describe exactly what actions triggered the bug
and the precise symptoms of the bug:
The error of "Invalid input style" which was patched in (I believe) emacs
version 20.5a by Gerd is back again. The bug reappeared in version 20.6 and
Gerd mentioned that it would be in version 20.7. I've just compiled and
tested 20.7 and the bug is still there.
Let me know if you want me to help track this bug down or if you already have
enough information to find and fix it. (By the way, AIX 4.3.3 has switched
completely to using the "VisualAge" C compiler; xlc is dead. :-/ I don't
know how to use the new debugging tools.)
One difference. The bug now does not seem to inhibit fontification:
I *think* I recall that it did so before, but I *know* it does not now.
Recent input:
M-x e m a c s - b tab u tab backspace backspace tab
M-backspace r e tab p o tab r tab return
Recent messages:
rchland settings loaded. the (informal) maintainer is ortmann@us.ibm.com
For information about the GNU Project and its goals, type C-h C-p.
Loading fast-lock...
Loading fast-lock...done
Making completion list...
Loading view...
Loading view...done
Making completion list... [2 times]
Loading emacsbug...
Loading emacsbug...done
--
Daniel Ortmann, IBM Circuit Technology, Rochester, MN 55901-7829
ortmann@us.ibm.com / internal 8.553.6795 / external 507.253.6795
ortmann@isl.net 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
[Prev in Thread] |
Current Thread |
[Next in Thread] |
- "Invalid input style",
Daniel Ortmann <=