From: "Marko Mäkelä" <marko.makela@iki.fi>
Cc: bug-gnu-emacs@gnu.org
Subject: Re: incorrect X11 display update
Date: Tue, 23 May 2006 11:36:53 +0300 [thread overview]
Message-ID: <20060523083653.GA3901@localhost.localdomain> (raw)
In-Reply-To: <E19MV9L-0007zJ-A4@fencepost.gnu.org>
[-- Attachment #1: Type: text/plain, Size: 2612 bytes --]
On Sun, Jun 01, 2003 at 11:53:35AM -0400, Richard Stallman wrote:
> Could you possibly get the latest sources from CVS on savannah.gnu.org
> so as to see if the problem still exists in the latest sources?
> That would be a big help.
This "ghost cursor" bug still exists after 3 years, and I've become used
to it. Yesterday I come across a way to reproduce it almost always.
The reduced $HOME/.emacs and the custom X resources are attached.
This bug occurs with the attached file emacs-bug.c, but any lengthy
text file should do.
Here are the steps to reproduce this "ghost cursor" bug.
(0) Start emacs and execute M-: (blink-cursor-mode -1)
(1) Load a document at least 3 pages long [c-mode or fundamental-mode]
(2) Scroll down at least one page.
(3) Position the cursor on column 0 of the first visible line of the buffer
("line 1"). Make sure that there is text on that line.
(4) Switch to another X11 application. Place the window so that
it will cover the left part of the Emacs window, from the bottom half
of line 2 [see (3)] downwards. Ensure that the Emacs window is taller,
i.e., that the mode line won't be covered by the other window.
(5) Switch between these two windows a few times. [Enable the
"popup focused window" setting of the window manager, so that an
expose event will be generated for the left part of the Emacs window
whenever switching back to Emacs.]
(6) Switch to the Emacs window and hit C-n. Now there should be a
"ghost cursor" on line 1. You can get another ghost cursor by pressing
C-f C-p and going back to step 5.
Please note that the ghost cursor does not always appear in step 6.
When it does, it seems to appear consistently for the rest of the
Emacs session. Here, the bug occurs at some 80% or 90% probability.
> I asked people to tell you how to determine what font is in use.
I've repeated the bug with three fonts: 'fixed' (selected from the Font menu,
more exactly, -misc-fixed-bold-r-normal--0-0-75-75-c-0-iso10646-1
or ...-iso8859-1) and -sony-fixed-medium-r-normal--16-*-*-*-*-*-*-*
(more exactly, -sony-fixed-medium-r-normal--16-150-75-75-c-80-iso8859-1),
and the default .Emacs.font when none has been specified in xrdb.
I'm using the Debian GNU/Linux unstable distribution with the package
emacs21, version 21.4a-6. "M-x version" reports the following:
GNU Emacs 21.4.1 (i486-pc-linux-gnu, X toolkit, Xaw3d scroll bars) of
2006-05-15 on trouble, modified by Debian
I don't think that this bug is window manager specific. Currently, I'm
using metacity 2.14.3 of the GNOME desktop. In 2003, I most likely used
fvwm2.
Best regards,
Marko Mäkelä
[-- Attachment #2: .emacs --]
[-- Type: text/plain, Size: 23 bytes --]
(blink-cursor-mode -1)
[-- Attachment #3: .Xresources --]
[-- Type: text/plain, Size: 144 bytes --]
! before starting Emacs, feed this file to xrdb -load
.Emacs.background: White
.Emacs.foreground: black
.Emacs.cursorColor: black
[-- Attachment #4: emacs-bug.c --]
[-- Type: text/x-csrc, Size: 1182 bytes --]
/******************************************************
Xxxxxxxxxx xxxx xxxxxxxxx
Xxxxxxxx Xx
Xxxxxxx Xxxxxx Xxxxx Xxxxxx
*******************************************************/
#xxxxxx XXXX_XXXXXX
#xxxxxxx "xxxx"
#xxxxx XXXX_XXXXXX
# xxxxxxx "xxxx"
#xxxxx
#xxxxx XXXX_XXXXXX
#xxxxxxx "xxxx"
#xxxxxxx "xxxx"
#xxxxxxx "xx.x"
#xxxxxxx "xx.x"
#xxxxxxx "xx.x"
#xxxxxxx "xx.x"
#xxxxxxx "xx.x"
#xxxxxxx "xx.x"
#xxxxxxx "xx.x"
#xxxxxxx "xx.x"
#xxxxxxx "xx.x"
/* Xxxxxx xxxxx xx ../xxxxxxx/xxxx0xxx.xx xxx x xxxxxxxxxxx xx xxx
xxxxxxxxxx xxxx xxxxxx. */
/* Xxx xxxxxxx xxx xxxxxxxx xxxxxxx xxx xxxxxxx xxxx xxx xxxxxxxxxx xxxx.
Xx xxxxxxxx, xx xxxxxxx xxxx xxx xxxxxxx xxx xxxxx, xxx xx xxxxxxxxxx xx
xxxxxxx xxx xxxxxxx. */
xxxxxx xxxxx xxxx xxxxxxx_xxxxx[] = {
0x00, /* xxxx_xxxx=0, x_xxxxx=1 */
0x00, 0x00 /* xxxx_xx=0, xxxxxx=2 */
/* ?, ? */ /* xxxx=(xxxxx xxxx xxx, xx xxxxxxxx) */
};
xxxxxx xxxxx xxxx xxxxxxx_xxxx[] = {
0x00, 0x00, 0x00, 0x00,
0x00, 0x00, 0x00, 0x00 /* "xxxxxxx\0" */
};
xxxxxx xxxxx xxxx xxxxxxxx_xxxxx_xxxx[] = {
0x00, 0x00, /* xxxx_xx=1, xxxxxx=3 */
0x00, 0x00, /* xxxx=0 */
0x00, 0x00, 0x00, 0x00,
0x00, 0x00, 0x00, 0x00 /* "xxxxxxxx" */
};
[-- Attachment #5: Type: text/plain, Size: 149 bytes --]
_______________________________________________
bug-gnu-emacs mailing list
bug-gnu-emacs@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-gnu-emacs
prev parent reply other threads:[~2006-05-23 8:36 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-31 8:13 incorrect X11 display update Marko Mäkelä
[not found] ` <E19MV9L-0007zJ-A4@fencepost.gnu.org>
2006-05-23 8:36 ` Marko Mäkelä [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20060523083653.GA3901@localhost.localdomain \
--to=marko.makela@iki.fi \
--cc=bug-gnu-emacs@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.