Date: Thu, 29 Nov 2001 09:40:54 -0500 From: Jonathan Kamens <jik.ma.us> To: bug-gnu-emacs Subject: emacs in xterm -- arrow invisible in M-x gdb 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. Your bug report will be posted to the bug-gnu-emacs mailing list, and to the gnu.emacs.bug news group. In GNU Emacs 21.1.1 (i386-redhat-linux-gnu, X toolkit, Xaw3d scroll bars) of 2001-11-06 on stripples.devel.redhat.com configured using `configure i386-redhat-linux --prefix=/usr --exec-prefix=/usr --bindir=/usr/bin --sbindir=/usr/sbin --sysconfdir=/etc --datadir=/usr/share --includedir=/usr/include --libdir=/usr/lib --libexecdir=/usr/libexec --localstatedir=/var --sharedstatedir=/usr/com --mandir=/usr/share/man --infodir=/usr/share/info --with-gcc --with-pop --with-sound' Important settings: value of $LC_ALL: nil value of $LC_COLLATE: C value of $LC_CTYPE: nil value of $LC_MESSAGES: nil value of $LC_MONETARY: nil value of $LC_NUMERIC: nil value of $LC_TIME: nil value of $LANG: en_US locale-coding-system: iso-latin-1 default-enable-multibyte-characters: t Please describe exactly what actions triggered the bug and the precise symptoms of the bug: I'm using "emacs -nw -q" in an xterm. When I use M-x gdb to debug a program, put in a breakpoint and run the program, the arrow showing me where I am is not visible when the breakpoint is hit. If I type "frame 0", the arrow flashes and then disappears again. Note that I've got my xterm configured with a foreground color of green and a background color of black, but I'm not sure how relevant this is (since if this were a color problem, I imagine that the arrow wouldn't flash even briefly). Note, furthermore, that I see this problem with two different versions of xterm -- the one in Red Hat's XFree86 3.3.6 package, and the one in Red Hat's XFree86 4.1.0 package. jik ************************* Date: Thu, 29 Nov 2001 19:15:11 +0200 (IST) From: Eli Zaretskii <eliz.co.il> To: Jonathan Kamens <jik.ma.us> cc: bug-gnu-emacs Subject: Re: emacs in xterm -- arrow invisible in M-x gdb On Thu, 29 Nov 2001, Jonathan Kamens wrote: > I'm using "emacs -nw -q" in an xterm. When I use M-x gdb to debug a > program, put in a breakpoint and run the program, the arrow showing me > where I am is not visible when the breakpoint is hit. Is the arrow visible when you step through the program with `n'? More generally, could you describe the circumstances which make the arrow disappear (unless it is never visible)? I did some simple tests, and it seems that for me, the arrow is always visible. So perhaps you do something special do trigger this problem. ************************* Date: Thu, 29 Nov 2001 12:21:48 -0500 From: Jonathan Kamens <jik.ma.us> To: bug-gnu-emacs Subject: Re: emacs in xterm -- arrow invisible in M-x gdb > Date: Thu, 29 Nov 2001 19:15:11 +0200 (IST) > From: Eli Zaretskii <eliz.co.il> > > Is the arrow visible when you step through the program with `n'? No. > More generally, could you describe the circumstances which make the > arrow disappear (unless it is never visible)? It is never visible (except for the flashes I noted previously). I will report the problem to Red Hat as well, since I am using a Red Hat Emacs package. Perhaps they've customized Emacs in some way that is causing this problem. jik
"(require 'python-mode)" is the culprit - something's not quite right in there.
It's also different between emacs 20 and emacs 21 - (require 'python-mode) break the arrow in emacs 21, while it works in emacs 20. Please forward that information to your emacs bug report.
I think perhaps you should correspond with bug-gnu-emacs directly. It doesn't seem like there's any advantage to my acting as a middle man at this point.
You're not going to ship without fixing this, are you?
Created attachment 60545 [details] patch to python-mode.el
I've attached my patch for this bug, which is still present in 7.3. The SourceForge python project page has another pending patch for this bug, too; I didn't notice it until I went to submit mine. And I like mine better, anyway.
*** Bug 72609 has been marked as a duplicate of this bug. ***
Is there any reason why Jason's patch has not been integrated yet?
emacs-21.2-17 should fix this.