unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Keith David Bershatsky <esq@lawlist.com>
To: 36633@debbugs.gnu.org
Subject: bug#36633: Scrolling by pixels: visible stretch glyphs overwrite header-line.
Date: Fri, 12 Jul 2019 19:10:44 -0700	[thread overview]
Message-ID: <m2v9w6bs63.wl%esq@lawlist.com> (raw)

Step 1:  Launch Emacs 26.

Step 2:  Evaluate the following code.

(progn
  (find-library "simple")
  (pixel-scroll-mode 1)
  (re-search-forward "\t\t\t\t\t" nil t)
  (set-window-start (selected-window) (match-beginning 0))
  (setq header-line-format "hello-world")
  (setq buffer-display-table (make-display-table))
  (aset buffer-display-table
        ?\t
        (vector (make-glyph-code ?\u00BB 'font-lock-warning-face)
                (make-glyph-code ?\t 'highlight)))
  (setq tab-width 8))

Step 3:  Move the mousewheel downward one time; i.e., one ratchet.

Step 4:  Observe the visible stretch glyphs overwriting the header-line.

BEHAVIOR EXPECTED:  The header-line should not be overwritten by the visible stretch glyphs that are being scrolled upwards from the row beneath the header-line.

I am on OSX 10.6.8 and performed this minimal working example with:

GNU Emacs 26.1 (build 1, x86_64-apple-darwin10.8.0, NS appkit-1038.36 Version 10.6.8 (Build 10K549)) of 2018-05-30





             reply	other threads:[~2019-07-13  2:10 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-07-13  2:10 Keith David Bershatsky [this message]
2019-07-13  6:19 ` bug#36633: Scrolling by pixels: visible stretch glyphs overwrite header-line Eli Zaretskii
2019-07-13  8:32   ` Stefan Kangas
2019-07-13  8:39     ` Eli Zaretskii
2019-07-14 10:39 ` Alan Third
2019-07-14 16:47 ` Keith David Bershatsky
2019-07-15 12:26   ` Tak Kunihiro
2019-07-16 20:38   ` Alan Third
2019-07-14 16:52 ` Keith David Bershatsky
2019-07-17  6:34 ` Keith David Bershatsky
2019-07-17 18:31   ` Alan Third
2019-07-17 19:08     ` Keith David Bershatsky
2019-07-17 23:31     ` Tak Kunihiro
2019-07-18  3:56 ` Keith David Bershatsky
2019-07-27 17:32   ` Alan Third

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=m2v9w6bs63.wl%esq@lawlist.com \
    --to=esq@lawlist.com \
    --cc=36633@debbugs.gnu.org \
    /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).