From: Eli Zaretskii <eliz@gnu.org>
To: Keith David Bershatsky <esq@lawlist.com>
Cc: emacs-devel@gnu.org
Subject: Re: Identifying the face between STRETCH and right fringe.
Date: Tue, 20 Nov 2018 19:20:42 +0200 [thread overview]
Message-ID: <83h8gbis2d.fsf@gnu.org> (raw)
In-Reply-To: <m24lcb66vf.wl%esq@lawlist.com> (message from Keith David Bershatsky on Tue, 20 Nov 2018 08:39:16 -0800)
> Date: Tue, 20 Nov 2018 08:39:16 -0800
> From: Keith David Bershatsky <esq@lawlist.com>
>
> Step 3: Observe that the result is different on Emacs --with-ns, versus --with-x and also on a Windows machine. Specifically, the STRETCH on an NS platform is seen spanning all the way to the right fringe. On an X11 and NT platform, the STRETCH is only visible for the width of the STRETCH (depicted in the dump-glyph-row for each platform below).
It's not the stretch glyph that spans all the window width, it's the
face of the stretch that gets extended to the window end. The stretch
glyph is still 7-character wide:
> ;;; NS
>
> Row Start End Used oE><\CTZFesm X Y W H V A P
> ==============================================================================
> 11 384 385 2 010010101000 0 176 56 16 16 12 12
> -1 -1 0
> -1 -1
> -1 -1
> Glyph# Type Pos O W Code C Face LR
> 0 C 384 B 7 0x0000bb . 30 00
> 1 S 384 B 49 0x000000 29 00
^^
49 = 7 * 7
> QUESTION #1: In terms of identifying the face between the STRETCH and the right fringe, how can I programmatically know the difference between the NS situation, versus the NT and X11 situation?
>
> QUESTION #2: Is the difference in behavior between the different platforms "a bug", and should the X11 and NT ports be "fixed" so that they behave like the NS port in this situation?
I will look into this when I have time. I don't yet know whether the
bug is on NS or on the other 2 platforms, though I tend to think the
former.
next prev parent reply other threads:[~2018-11-20 17:20 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-20 16:39 Identifying the face between STRETCH and right fringe Keith David Bershatsky
2018-11-20 17:20 ` Eli Zaretskii [this message]
2018-11-21 7:44 ` Robert Pluim
2018-11-23 10:04 ` Eli Zaretskii
2018-11-23 13:25 ` Robert Pluim
2018-11-23 13:48 ` Eli Zaretskii
2018-11-23 14:04 ` Robert Pluim
2018-11-23 15:51 ` Eli Zaretskii
2018-11-23 15:58 ` Robert Pluim
2018-11-23 20:33 ` Eli Zaretskii
2018-11-27 8:56 ` Robert Pluim
2018-11-27 9:34 ` Eli Zaretskii
2018-11-27 11:02 ` Robert Pluim
2018-11-27 11:29 ` Eli Zaretskii
2018-11-27 13:55 ` Robert Pluim
2018-11-27 18:55 ` Eli Zaretskii
2018-11-27 19:14 ` Robert Pluim
2018-11-27 19:38 ` Robert Pluim
2018-11-28 6:03 ` Eli Zaretskii
2018-11-28 9:00 ` Robert Pluim
2018-11-28 9:42 ` Eli Zaretskii
2018-11-28 9:49 ` Eli Zaretskii
2018-11-28 13:24 ` Robert Pluim
2018-11-28 16:19 ` Eli Zaretskii
2018-11-28 7:13 ` Eli Zaretskii
2018-11-28 8:36 ` Robert Pluim
2018-11-28 9:45 ` Eli Zaretskii
2018-11-28 9:56 ` Robert Pluim
2018-11-28 10:11 ` Eli Zaretskii
2018-11-28 13:21 ` Robert Pluim
2018-11-28 16:20 ` Eli Zaretskii
2018-11-29 12:51 ` Robert Pluim
2018-11-29 14:15 ` Eli Zaretskii
2018-11-28 21:14 ` Alan Third
2018-11-29 12:26 ` Robert Pluim
2018-11-29 12:54 ` Eli Zaretskii
2018-11-29 13:52 ` Robert Pluim
2018-11-29 14:08 ` Eli Zaretskii
2018-11-30 7:59 ` Robert Pluim
2018-11-30 8:04 ` Robert Pluim
2018-11-30 8:22 ` 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=83h8gbis2d.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).