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: Robert Pluim <rpluim@gmail.com>
Cc: 64270@debbugs.gnu.org, Manuel Giraud <manuel@ledu-giraud.fr>
Subject: bug#64270: 30.0.50; Font update for no toolkit menu
Date: Tue, 27 Jun 2023 17:49:15 +0800	[thread overview]
Message-ID: <87y1k56xr8.fsf@yahoo.com> (raw)
In-Reply-To: <87wmzpckck.fsf@gmail.com> (Robert Pluim's message of "Tue, 27 Jun 2023 11:42:19 +0200")

Robert Pluim <rpluim@gmail.com> writes:

> OK, but we could still fix this niggle in `font_unparse_xlfd' (if I
> call it a regression, can it go in emacs-29? 😸)

I'm not so sure... I think it is more important that Emacs be able to
parse its own XLFDs without losing information than it is for XLFDs it
generates to be understood by X, since XLFDs are often used in Lisp as a
printable replacement for font specifications.





  reply	other threads:[~2023-06-27  9:49 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-06-24 17:00 bug#64270: 30.0.50; Font update for no toolkit menu Manuel Giraud via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-06-24 17:16 ` Eli Zaretskii
2023-06-27  7:04   ` Manuel Giraud via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-06-27 11:26     ` Eli Zaretskii
2023-06-27 14:13       ` Manuel Giraud via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-06-27 15:54         ` Eli Zaretskii
2023-06-27 16:07           ` Manuel Giraud via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-06-27 18:18             ` Eli Zaretskii
2023-06-28  0:28               ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-06-28  7:50                 ` Manuel Giraud via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-06-28  9:20                   ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-06-28  7:38               ` Manuel Giraud via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-06-25  0:36 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-06-27  7:08   ` Manuel Giraud via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-06-27  7:48     ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-06-27  8:25       ` Manuel Giraud via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-06-27  8:37       ` Robert Pluim
2023-06-27  8:47         ` Robert Pluim
2023-06-27  8:55           ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-06-27  9:42             ` Robert Pluim
2023-06-27  9:49               ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors [this message]
2023-06-27  9:53                 ` Robert Pluim
2023-06-27 12:06                   ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-06-27  9:59                 ` Manuel Giraud via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-06-27 12:10                   ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-06-27 14:02                     ` Manuel Giraud via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-06-27 11:30               ` 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=87y1k56xr8.fsf@yahoo.com \
    --to=bug-gnu-emacs@gnu.org \
    --cc=64270@debbugs.gnu.org \
    --cc=luangruo@yahoo.com \
    --cc=manuel@ledu-giraud.fr \
    --cc=rpluim@gmail.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).