all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Vordoo 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: 54188@debbugs.gnu.org
Subject: bug#54188: Crash when eval-ing font test elisp code
Date: Mon, 28 Feb 2022 23:44:47 +0200	[thread overview]
Message-ID: <d66c6e83-236d-658a-b66b-2a465ef720d2@yahoo.com> (raw)
In-Reply-To: <83zgmbmbei.fsf@gnu.org>

On 2/28/22 14:19, Eli Zaretskii wrote:
> If you can establish which font causes this, it could allow us to
> decide whether and how to deal with this issue. Thanks. 
Tested on Emacs: 27.2 | 28.0.60 | 29.0.50
Crashes with fonts: terminal, lucida, charter, Caladings CLM.

For clarity replaced (font-family-list) with an actual font list:
(require 'cl-lib)
(require 'cl-extra)
(let ((str "The quick brown fox jumps over the lazy dog 
´`''\"\"1lI|¦!Ø0Oo{[()]}.,:; ")
       (font-families (cl-remove-duplicates
               (sort '("Standard Symbols PS" "URW Gothic" "Roboto 
Condensed" "Droid Sans") ;; <-- WORKS
                    ;; '("terminal")                              ;; <-- 
CRASH
                    ;; '("lucida" )                            ;;<-- CRASH
                    ;; '("Caladings CLM")                    ;; <-- CRASH
                    ;; '("charter")                            ;; <-- CRASH

                (lambda(x y) (string< (upcase x) (upcase y))))
               :test 'cl-equalp)))
   (dolist (ff font-families)
     (insert
      (propertize str 'font-lock-face `(:family ,ff))               ff "\n"
      (propertize str 'font-lock-face `(:family ,ff :slant italic)) ff 
"\n")))








  reply	other threads:[~2022-02-28 21:44 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <50f9bd97-02a4-4b0d-0eae-54e804293219.ref@yahoo.com>
2022-02-27 20:33 ` bug#54188: Crash when eval-ing font test elisp code Vordoo via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-02-28  3:30   ` Eli Zaretskii
2022-02-28  7:09     ` Vordoo via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-02-28 12:19       ` Eli Zaretskii
2022-02-28 21:44         ` Vordoo via Bug reports for GNU Emacs, the Swiss army knife of text editors [this message]
2022-03-01 12:55           ` Eli Zaretskii
2022-03-01 15:23             ` Vordoo via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-03-01 17:38               ` Eli Zaretskii
2022-03-01 18:50                 ` Vordoo via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-03-01 19:37                   ` Eli Zaretskii
2022-03-01 20:08                     ` Vordoo via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-03-01 20:33                       ` Eli Zaretskii
2022-03-01 21:51                         ` Vordoo via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-03-03  9:46                           ` Eli Zaretskii
2022-03-03 12:46                             ` Vordoo via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-03-03 14:05                               ` Eli Zaretskii
2022-03-03 14:16                                 ` Lars Ingebrigtsen
2022-03-03 14:25                                   ` Eli Zaretskii
2022-03-03 14:51                                     ` Lars Ingebrigtsen
2022-03-03 15:04                                       ` Vordoo via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-03-03 15:22                                         ` Vordoo via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-03-03 14:39                                   ` Vordoo via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-03-03 14:49                                     ` jeff
2022-02-28  9:41   ` Lars Ingebrigtsen

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=d66c6e83-236d-658a-b66b-2a465ef720d2@yahoo.com \
    --to=bug-gnu-emacs@gnu.org \
    --cc=54188@debbugs.gnu.org \
    --cc=eliz@gnu.org \
    --cc=vordoo@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 external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.