unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Po Lu via "Bug reports for GNU Emacs, the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: JD Smith <jdtsmith@gmail.com>, 73082@debbugs.gnu.org
Subject: bug#73082: 30; Inconsistent Stipple Support
Date: Sat, 07 Sep 2024 14:51:05 +0800	[thread overview]
Message-ID: <87v7z8q7mu.fsf@yahoo.com> (raw)
In-Reply-To: <86wmjoyoon.fsf@gnu.org> (Eli Zaretskii's message of "Sat, 07 Sep 2024 09:15:36 +0300")

Eli Zaretskii <eliz@gnu.org> writes:

>> Cc: Po Lu <luangruo@yahoo.com>
>> From: JD Smith <jdtsmith@gmail.com>
>> Date: Fri, 6 Sep 2024 17:58:02 -0400
>> 
>> (let* ((w (window-font-width))
>>        (stipple `(,w 1 ,(apply #'unibyte-string (make-list (/ (+ w 7) 8) 186)))))
>>   (insert "\n" (propertize (concat  (make-string 15 ?\s)
>> 				    "THIS IS A TEST"
>> 				    (make-string 15 ?\s))
>>                            'face `(:background "red" :foreground "blue" :stipple ,stipple))))
>> 
>> Only some Emacs 30 builds correctly render this simple stipple.  There has been some progress on :stipple support recently, but it remains incomplete.  To my knowledge, the current situation for :stipple support in Emacs 30 is as follows:
>> NS (partially working): Commit ef6ffbdc79 from last May provided a partial fix, but stipples are black and white only (bug#70712)
>> Windows (working?): patched in June (bug#71159)
>> PGTK (working): incorrect stipple display patched July, 2023 (bug#64969)
>> GTK, non-Cairo (working): appears to be working correctly
>> GTK + Cairo (not working uniformly): Stipples are reported to be missing with some Cairo builds of Emacs 30
>> Other X11 builds (?): Unsure if these are supported (but suspect they are given the legacy of stipple)
>
> The MS-Windows build of the emacs-30 branch here shows the display you
> expected.

You should add Haiku and Android to your list, as Emacs supports
stipples on both of these window systems.  (And on the latter they were
in fact implemented for your package.)

I am also interested to know precisely which Cairo builds fail to
display them, the stipple implementations being virtually identical
across the PGTK and the X + Cairo builds.






  reply	other threads:[~2024-09-07  6:51 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-09-06 21:58 bug#73082: 30; Inconsistent Stipple Support JD Smith
2024-09-07  6:15 ` Eli Zaretskii
2024-09-07  6:51   ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors [this message]
2024-09-07 12:50     ` JD Smith
2024-09-07 13:17       ` JD Smith
2024-09-13 18:07         ` JD Smith
2024-09-14  0:33           ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-09-19 15:53             ` JD Smith
2024-09-07  6:19 ` Arash Esbati

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=87v7z8q7mu.fsf@yahoo.com \
    --to=bug-gnu-emacs@gnu.org \
    --cc=73082@debbugs.gnu.org \
    --cc=eliz@gnu.org \
    --cc=jdtsmith@gmail.com \
    --cc=luangruo@yahoo.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).