unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: me@alandmoore.com
Cc: 21658@debbugs.gnu.org
Subject: bug#21658: 24.5; Scrolling garbles text with third monitor enabled
Date: Mon, 12 Oct 2015 21:35:51 +0300	[thread overview]
Message-ID: <83pp0knddk.fsf@gnu.org> (raw)
In-Reply-To: <44352.72.237.174.2.1444674068.squirrel@67.228.73.20>

[Please keep the bug address on the CC list.]

> Date: Mon, 12 Oct 2015 18:21:08 -0000 (GMT)
> From: me@alandmoore.com
> 
> > Are the problematic frames/windows displayed on the 3rd monitor?
> >
> > Do the coordinates of the frames on the 1st and the 2nd monitor change
> > when you enable the 3rd monitor?
> >
> > If the answer to both of these questions is NO, then I cannot see how
> > it could be an Emacs problem.  It could be some hardware problem or
> > perhaps a bug in the underlying X libraries/server.  AFAIK, when Emacs
> > redraws a window on a monitor, it doesn't inquire the system about the
> > monitors, the only thing it cares about is pixel coordinates of
> > windows and frames.
> >
> 
> The frames do the same thing on any monitor.  I don't think the
> coordinates should change at all, the additional monitor is appended to
> the right of the others (though it makes no difference where I add it,
> even if I just clone one of the other screens).
> 
> Is there anything special about the way emacs buffers are drawn compared
> to other programs that would give me a clue as to why this only happens in
> emacs?

We just use Xlib calls, see xterm.c and xfns.c.





  parent reply	other threads:[~2015-10-12 18:35 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-10-09 18:31 bug#21658: 24.5; Scrolling garbles text with third monitor enabled me
2015-10-10  7:36 ` Eli Zaretskii
     [not found]   ` <44352.72.237.174.2.1444674068.squirrel@67.228.73.20>
2015-10-12 18:35     ` Eli Zaretskii [this message]
2019-09-29 21:58 ` Stefan Kangas

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

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=83pp0knddk.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=21658@debbugs.gnu.org \
    --cc=me@alandmoore.com \
    /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 public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).