unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Keith David Bershatsky <esq@lawlist.com>
Cc: emacs-devel@gnu.org
Subject: Re: Problems with move_it_in_display_line_to X when tabs exist.
Date: Wed, 29 Nov 2017 20:04:14 +0200	[thread overview]
Message-ID: <838tep3qsh.fsf@gnu.org> (raw)
In-Reply-To: <m2vahtd358.wl%esq@lawlist.com> (message from Keith David Bershatsky on Tue, 28 Nov 2017 22:12:35 -0800)

> Date: Tue, 28 Nov 2017 22:12:35 -0800
> From: Keith David Bershatsky <esq@lawlist.com>
> 
> I can see that X and/or HPOS are wrong when tabs are present on the current line because I get superimposed letters and double of the same word slightly off to the left and/or the right of where the word should be.
> 
> HYPOTHESIS:  I would venture to say that what is displayed on screen does _not_ coincide with what IT reports when running move_it_in_display_line_to.

Does this happen only when line numbers are displayed?

In any case, your description provides a lot of details that are hard
to reason about, because most of the code is not shown.  OTOH, if
indeed there's a bug in move_it_in_display_line_to, then presenting
evidence for it is very simple: show a line of text and its line
number, and then show the X and HPOS values for each tab in that line
as calculated by move_it_in_display_line_to vs the same values in a
displayed line.  (For the latter, you can use the pgrowx command
defined in src/.gdbinit, or manually display the values using the
debugger.)

If you do that, any mismatches between displaying a line and moving
through it with move_it_in_display_line_to will be immediately
apparent, and it should be easy to fix them.



  reply	other threads:[~2017-11-29 18:04 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-11-29  6:12 Problems with move_it_in_display_line_to X when tabs exist Keith David Bershatsky
2017-11-29 18:04 ` Eli Zaretskii [this message]
  -- strict thread matches above, loose matches on Subject: below --
2017-11-30  4:29 Keith David Bershatsky
2017-12-02 19:52 Keith David Bershatsky
2017-12-02 21:14 ` Eli Zaretskii
2017-12-02 22:28 Keith David Bershatsky
2017-12-03  3:32 ` Eli Zaretskii
2017-12-03  3:38 Keith David Bershatsky
2017-12-03 14:29 ` Eli Zaretskii
2017-12-03 20:56 Keith David Bershatsky
2017-12-04 15:48 ` Eli Zaretskii
2017-12-04  3:01 Keith David Bershatsky
2017-12-04 16:26 ` Eli Zaretskii
2017-12-04  8:03 Keith David Bershatsky
2017-12-06 16:24 Keith David Bershatsky
2018-01-15  5:48 Keith David Bershatsky
2018-01-15 12:06 ` Eli Zaretskii
2018-01-16  4:41 Keith David Bershatsky
2018-01-16 17:00 ` Eli Zaretskii
2018-01-16 17:53 Keith David Bershatsky
2018-01-21 20:32 Keith David Bershatsky
2018-01-23  7:38 Keith David Bershatsky

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=838tep3qsh.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=esq@lawlist.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).