unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: "Gerd Möllmann" <gerd.moellmann@gmail.com>
Cc: 56808@debbugs.gnu.org
Subject: bug#56808: 29.0.50; Elusive display problem on macOS
Date: Thu, 28 Jul 2022 09:04:48 +0300	[thread overview]
Message-ID: <83r125ai2n.fsf@gnu.org> (raw)
In-Reply-To: <m2h731zuup.fsf@Mini.fritz.box> (message from Gerd Möllmann on Thu, 28 Jul 2022 07:09:34 +0200)

> From: Gerd Möllmann <gerd.moellmann@gmail.com>
> Date: Thu, 28 Jul 2022 07:09:34 +0200
> 
> I am seeing a display problem on macOS.  I am looking at code like this:
> 
> (dap-register-debug-template
>  (list :name "LLDB Emacs"
>        :type "lldb-vscode"
> 
> When the problem happens, the display looks like
> 
> (dap-register-debug-template
>  (list :name "LLDB Emacs"
>         :type "lldb-vscode"
> 
> I.e. :name and :type don't align anymore.

Are there any :align-to display properties involved in this?
("C-x =" could help you find out.)

Can you run this under a debugger and show the display elements in the
offending glyph_row?  The easiest way of doing that with GDB is like
this:

  (gdb) break Fredraw_display
  (gdb) run

Then wait for the problem to happen when it does, move the cursor to
the screen line with the alignment problem, invoke redraw-display, and
when the debugger kicks in, do:

  (gdb) break set_cursor_from_row
  (gdb) continue

Typically, the first time the breakpoint in set_cursor_from_row breaks
it's in a mini-window.  Verify with

  (gdb) p it->w->contents
  (gdb) xtype
  (gdb) xbuffer

Then type "continue".  Do the above until set_cursor_from_row is
called in the right buffer.  Then step until the variable 'row' is
assigned in one of the first lines of the function, and do

  (gdb) pgrow

This should display the glyph_row with some detail.

Of course, you don't have GDB, so some of the above will need to be
done differently, sigh...  In particular, the 'pgrow' command is
defined in src/.gdbinit.

You may wish starting by doing the above in a "good" session, to see
what display elements are shown in that glyph_row when the display is
correct.

Thanks.





  reply	other threads:[~2022-07-28  6:04 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-28  5:09 bug#56808: 29.0.50; Elusive display problem on macOS Gerd Möllmann
2022-07-28  6:04 ` Eli Zaretskii [this message]
2022-07-28  7:37   ` Gerd Möllmann
2022-07-28  8:01     ` Eli Zaretskii
2022-07-28  9:18       ` Gerd Möllmann
2022-07-28 11:31         ` Gerd Möllmann
2022-07-28 12:07           ` Gerd Möllmann
2022-07-28 13:03             ` Gerd Möllmann
2022-07-28 13:37             ` Eli Zaretskii
2022-07-28 15:04               ` Gerd Möllmann
2022-07-28 15:12                 ` Eli Zaretskii
2022-07-28 17:13                   ` Gerd Möllmann
2022-07-29 12:32                     ` Gerd Möllmann
2022-07-29 13:52                       ` YAMAMOTO Mitsuharu
2022-07-29 14:32                         ` Gerd Möllmann
2022-07-30  7:49                           ` YAMAMOTO Mitsuharu
2022-07-30  7:54                             ` Gerd Möllmann
2022-07-30  8:13                             ` Eli Zaretskii
2022-07-30  8:28                               ` YAMAMOTO Mitsuharu
2022-07-29 13:17   ` Alexander Adolf
2022-07-29 14:18     ` Gerd Möllmann

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=83r125ai2n.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=56808@debbugs.gnu.org \
    --cc=gerd.moellmann@gmail.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).