unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Alan Third <alan@idiocy.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: netjune@outlook.com, 38731@debbugs.gnu.org
Subject: bug#38731: 27.0.50; Unexpected redisplay behaviour. Cursor can’t be moved to end of line.
Date: Fri, 27 Dec 2019 14:35:00 +0000	[thread overview]
Message-ID: <20191227143500.GA75733@breton.holly.idiocy.org> (raw)
In-Reply-To: <83a77fq9la.fsf@gnu.org>

[-- Attachment #1: Type: text/plain, Size: 1236 bytes --]

On Thu, Dec 26, 2019 at 07:29:21PM +0200, Eli Zaretskii wrote:
> > Date: Thu, 26 Dec 2019 12:59:17 +0000
> > From: Alan Third <alan@idiocy.org>
> > Cc: HaiJun Zhang <netjune@outlook.com>, 38731@debbugs.gnu.org
> > 
> > In ns_draw_glyph_string I can see that s->x is correctly set to 136
> > when the backtrace doesn’t contain expose_frame, but 178 when it does.
> 
> Isn't it the other way around?  The correct display should start at a
> larger X coordinate.  Or maybe I don't understand what is s->x in this
> context, i.e. what glyph string is S.

Unless I’m somehow seeing a different problem (I haven’t watched the
video) the problem occurs when the buffer is scrolled horizontally,
and we should be able to see the end of the line point is on. However,
the line is drawn off the right side of the frame.

I’ve attached an image that I hope illustrates it better than I can
describe. You can see the glyph seen in the cursor is a /, and is the
first character of the text. The end of the line is at the b in
foobar.

So the text is drawn at too large an X coordinate, although the glyph
seen in the cursor is always correct.

Anyway, I’ll have a dig around and see if I can find where it’s going
wrong.

-- 
Alan Third

[-- Attachment #2: bug38731 screenshot --]
[-- Type: image/png, Size: 14448 bytes --]

  reply	other threads:[~2019-12-27 14:35 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <a0dc5800-db7e-4091-b385-e2c888f9472b@Spark>
2019-12-24 10:43 ` bug#38731: 27.0.50; Unexpected redisplay behaviour. Cursor can’t be moved to end of line HaiJun Zhang
2019-12-24 15:50   ` Eli Zaretskii
2019-12-24 16:42     ` HaiJun Zhang
2019-12-26 12:59     ` Alan Third
2019-12-26 13:24       ` HaiJun Zhang
2019-12-26 17:29       ` Eli Zaretskii
2019-12-27 14:35         ` Alan Third [this message]
2019-12-27 16:26           ` bug#38731: [PATCH] Calculate first glyph to be redrawn when exposing (bug#38731) Alan Third
2019-12-27 17:17             ` Eli Zaretskii
2019-12-27 19:06               ` Alan Third
2019-12-28  8:54                 ` Eli Zaretskii
2019-12-28 11:20                   ` Alan Third
2019-12-28 18:27                     ` Eli Zaretskii
2019-12-29 10:46                       ` Alan Third
2019-12-30  4:55                         ` HaiJun Zhang

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=20191227143500.GA75733@breton.holly.idiocy.org \
    --to=alan@idiocy.org \
    --cc=38731@debbugs.gnu.org \
    --cc=eliz@gnu.org \
    --cc=netjune@outlook.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).