From: "Daniel Martín via Bug reports for GNU Emacs, the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
To: 58540@debbugs.gnu.org
Cc: luangruo@yahoo.com, eliz@gnu.org, paaguti@gmail.com
Subject: bug#58540: 29.0.50; While opening the font dialog
Date: Sat, 15 Oct 2022 10:33:08 +0200 [thread overview]
Message-ID: <m1r0z94hbv.fsf@yahoo.es> (raw)
In-Reply-To: <875yglpkvv.fsf@yahoo.com> (Po Lu via's message of "Sat, 15 Oct 2022 16:10:44 +0800")
Po Lu via "Bug reports for GNU Emacs, the Swiss army knife of text
editors" <bug-gnu-emacs@gnu.org> writes:
> Eli Zaretskii <eliz@gnu.org> writes:
>
>> This is macOS specific, because I don't see anything like that here.
>
> Not only that, but it also shows up on every other Mac OS app when
> opening the font dialog. So let's sue Apple for their illegal
> activities. (Doesn't this joke ring a bell? I think this bug report is
> a duplicate of another, but I can't find it.)
Yes, it's a duplicate of bug#56259.
next prev parent reply other threads:[~2022-10-15 8:33 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-15 6:44 bug#58540: 29.0.50; While opening the font dialog Pedro Andres Aranda Gutierrez
2022-10-15 7:47 ` Eli Zaretskii
2022-10-15 8:10 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-10-15 8:33 ` Daniel Martín via Bug reports for GNU Emacs, the Swiss army knife of text editors [this message]
2022-10-15 8:35 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
-- strict thread matches above, loose matches on Subject: below --
2022-06-27 14:22 bug#56259: 29.0.50; Illegal -layoutSubtreeIfNeeded on NS Gerd Möllmann
2022-08-21 21:57 ` Daniel Martín via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-11-12 20:57 ` bug#58540: 29.0.50; While opening the font dialog Stefan Kangas
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=m1r0z94hbv.fsf@yahoo.es \
--to=bug-gnu-emacs@gnu.org \
--cc=58540@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=luangruo@yahoo.com \
--cc=mardani29@yahoo.es \
--cc=paaguti@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 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.