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: Sat, 02 Dec 2017 23:14:33 +0200	[thread overview]
Message-ID: <83wp24zvba.fsf@gnu.org> (raw)
In-Reply-To: <m2d13wsy9q.wl%esq@lawlist.com> (message from Keith David Bershatsky on Sat, 02 Dec 2017 11:52:33 -0800)

> Date:  Sat, 02 Dec 2017 11:52:33 -0800
> From:  Keith David Bershatsky <esq@lawlist.com>
> Cc:  emacs-devel@gnu.org
> 
> The test assumes:
> 
> * The variable word-wrap is non-nil.
> 
> * The variable tab-width is 2.
> 
> * The buffer-display table entry for a tab is:  [(187 . 120) (9 . 121)].
> 
> * Native line numbers are _not_ enabled.
> 
> I have a long line that wraps at the window edge and I put a space to simulate a new word that should be wrapped to the following line.  To make it easier to read, I am using the backslash symbol (below) to signify a word-wrap with a space at the window edge.  The next line has three "x" followed by a tab and then the word "hello-world".  The STRETCH glyph is 22 pixels wide; however, it.pixel_width is erroneously (?) reporting that it is 11 pixels wide.
> 
> I have hard-coded an emacs_abort () when it.c == '\t', which means that we have just moved passed character 187 (aka "»") and we are now on a STRETCH tab-width.

What is the value of it.what and of it.char_to_display?  And what is
the value of it.method and it.current_x?

My crystal ball says that, since your display table shows a TAB as 2
characters, the first of which is a u+00bb, and is displayed as an
11-pixel glyph, that is the display element whose metrics you are
seeing.  The stretch glyph produced by the TAB from the display table
is after that.



  reply	other threads:[~2017-12-02 21:14 UTC|newest]

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

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=83wp24zvba.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).