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: 70989@debbugs.gnu.org, me@rodrigomorales.site
Subject: bug#70989: 29.3; Calling isearch-forward when using Unifont throws error "Invalid font name"
Date: Mon, 20 May 2024 21:03:26 +0800	[thread overview]
Message-ID: <87r0dw63fl.fsf@yahoo.com> (raw)
In-Reply-To: <86a5kmaqhj.fsf@gnu.org> (Eli Zaretskii's message of "Sun, 19 May 2024 16:19:36 +0300")

Eli Zaretskii <eliz@gnu.org> writes:

>> From: Po Lu <luangruo@yahoo.com>
>> Cc: me@rodrigomorales.site,  70989@debbugs.gnu.org
>> Date: Sun, 19 May 2024 21:00:30 +0800
>> 
>> Eli Zaretskii <eliz@gnu.org> writes:
>> 
>> > Thanks, but why not replace all of those with a SPC?  It's simpler, I
>> > think.
>> 
>> No reason in particular, I simply thought it would be more elegant to
>> replace the other special characters with a different placeholder.
>
> I'd prefer to replace all the characters we cannot use there with a
> SPC, for consistency.
>
> Otherwise, I'm okay with the patch; please feel free to install.

Now done.  Rodrigo, please test and ack, and thanks.





      reply	other threads:[~2024-05-20 13:03 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-05-16 18:39 bug#70989: 29.3; Calling isearch-forward when using Unifont throws error "Invalid font name" Rodrigo Morales
2024-05-16 19:31 ` Eli Zaretskii
2024-05-16 20:09   ` Rodrigo Morales
2024-05-17  6:13     ` Eli Zaretskii
2024-05-17 11:03       ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-05-17 15:14         ` Rodrigo Morales
2024-05-18 12:25           ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-05-18 15:34             ` Eli Zaretskii
2024-05-19  0:15               ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-05-19  6:05                 ` Eli Zaretskii
2024-05-19  7:37                   ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-05-19  7:49                     ` Eli Zaretskii
2024-05-19 11:13                       ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-05-19 11:42                         ` Eli Zaretskii
2024-05-19 13:00                           ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-05-19 13:19                             ` Eli Zaretskii
2024-05-20 13:03                               ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors [this message]

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=87r0dw63fl.fsf@yahoo.com \
    --to=bug-gnu-emacs@gnu.org \
    --cc=70989@debbugs.gnu.org \
    --cc=eliz@gnu.org \
    --cc=luangruo@yahoo.com \
    --cc=me@rodrigomorales.site \
    /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).