From: Eli Zaretskii <eliz@gnu.org>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: oitofelix@gnu.org, 18912@debbugs.gnu.org
Subject: bug#18912: 24.4; mode-line corruption on graphical frames in dual-headed display
Date: Sat, 01 Nov 2014 10:42:29 +0200 [thread overview]
Message-ID: <834mujz4zu.fsf@gnu.org> (raw)
In-Reply-To: <jwvwq7gugou.fsf-monnier+emacsbugs@gnu.org>
> From: Stefan Monnier <monnier@iro.umontreal.ca>
> Date: Fri, 31 Oct 2014 16:30:18 -0400
> Cc: 18912@debbugs.gnu.org
>
> > In this setup GNU Emacs corrupts the mode-line (a graphical glitch)
> > drawing over it the buffer's line that would otherwise be below it.
>
> My guess is that it's a bug in the X11 acceleration code for your
> graphics card.
How could the graphics card "know" the details of the file that should
not be visible in the window? The text that overwrites the mode line
is not for any of the files shown above the mode line, it's the file
that is the next one in the listing. So the only way the acceleration
could cause that is if it returned incorrect information about the
display dimensions/pixel size. I cannot explain to myself how this
kind of bug in the graphics card could affect Emacs, except perhaps in
a maximized frame.
Bruno, do these problems happen in a non-maximized frame, e.g. the one
you get immediately after invoking "emacs -Q"?
next prev parent reply other threads:[~2014-11-01 8:42 UTC|newest]
Thread overview: 63+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-30 13:46 bug#18912: 24.4; mode-line corruption on graphical frames in dual-headed display Bruno Félix Rezende Ribeiro
2014-10-31 20:30 ` Stefan Monnier
2014-10-31 20:44 ` Bruno Félix Rezende Ribeiro
2014-11-01 8:42 ` Eli Zaretskii [this message]
2014-11-01 12:56 ` Bruno Félix Rezende Ribeiro
2014-11-01 8:38 ` Eli Zaretskii
2014-11-01 9:16 ` Eli Zaretskii
2014-11-01 12:54 ` Bruno Félix Rezende Ribeiro
2014-11-01 13:03 ` Eli Zaretskii
2014-11-02 21:49 ` Bruno Félix Rezende Ribeiro
2014-11-03 3:34 ` Eli Zaretskii
2014-11-03 6:03 ` Bruno Félix Rezende Ribeiro
2014-11-03 16:20 ` Eli Zaretskii
2014-11-03 17:43 ` martin rudalics
2014-11-03 17:52 ` Eli Zaretskii
2014-11-03 18:01 ` martin rudalics
2014-11-03 18:19 ` Eli Zaretskii
2014-11-03 20:06 ` Bruno Félix Rezende Ribeiro
2014-11-03 20:24 ` Eli Zaretskii
2014-11-03 20:29 ` Eli Zaretskii
2014-11-03 20:46 ` Eli Zaretskii
2014-11-03 21:01 ` Bruno Félix Rezende Ribeiro
2014-11-03 21:19 ` Eli Zaretskii
2014-11-04 6:05 ` Bruno Félix Rezende Ribeiro
2014-11-04 8:25 ` Bruno Félix Rezende Ribeiro
2014-11-04 16:00 ` Eli Zaretskii
2014-11-04 19:24 ` martin rudalics
2014-11-04 19:52 ` Eli Zaretskii
2014-11-04 20:13 ` Stefan Monnier
2014-11-05 3:39 ` Eli Zaretskii
2014-11-05 9:17 ` Andreas Schwab
2014-11-04 21:09 ` Bruno Félix Rezende Ribeiro
2014-11-05 16:02 ` Eli Zaretskii
2014-11-05 21:38 ` Bruno Félix Rezende Ribeiro
2014-11-06 3:45 ` Eli Zaretskii
2014-11-06 15:28 ` Stefan Monnier
2014-11-04 15:54 ` Stefan Monnier
2014-11-04 21:28 ` Bruno Félix Rezende Ribeiro
2014-11-04 23:11 ` Stefan Monnier
2014-11-04 15:56 ` Eli Zaretskii
2014-11-04 19:24 ` martin rudalics
2014-11-04 20:55 ` Bruno Félix Rezende Ribeiro
2014-11-04 20:14 ` Bruno Félix Rezende Ribeiro
2014-11-05 3:51 ` Eli Zaretskii
2014-11-05 6:28 ` Bruno Félix Rezende Ribeiro
2014-11-05 15:58 ` Eli Zaretskii
2014-11-05 19:46 ` Bruno Félix Rezende Ribeiro
2014-11-03 20:55 ` Bruno Félix Rezende Ribeiro
2014-11-03 20:44 ` Bruno Félix Rezende Ribeiro
2014-11-03 9:08 ` Andreas Schwab
2014-11-03 16:23 ` Eli Zaretskii
2014-11-03 9:41 ` martin rudalics
2014-11-03 18:58 ` Bruno Félix Rezende Ribeiro
2014-11-03 19:14 ` Eli Zaretskii
2014-11-03 20:10 ` Bruno Félix Rezende Ribeiro
2014-11-04 7:55 ` martin rudalics
2014-11-04 8:20 ` Bruno Félix Rezende Ribeiro
2014-11-04 9:19 ` martin rudalics
2014-11-04 10:25 ` Bruno Félix Rezende Ribeiro
2014-11-04 16:16 ` Eli Zaretskii
2014-11-04 19:56 ` Bruno Félix Rezende Ribeiro
2014-11-04 19:23 ` martin rudalics
2014-11-04 21:46 ` Bruno Félix Rezende Ribeiro
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=834mujz4zu.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=18912@debbugs.gnu.org \
--cc=monnier@iro.umontreal.ca \
--cc=oitofelix@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.