From: Po Lu via "Bug reports for GNU Emacs, the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
To: Bjoern Bidar <bjorn.bidar@thaodan.de>
Cc: 56967@debbugs.gnu.org
Subject: bug#56967: 29.0.50; Frequent crashes under Wayland
Date: Mon, 08 Aug 2022 18:10:36 +0800 [thread overview]
Message-ID: <87r11rqc4j.fsf@yahoo.com> (raw)
In-Reply-To: <2062339.XFdaHZJ8Qi@odin> (Bjoern Bidar's message of "Mon, 08 Aug 2022 11:56:19 +0300")
Bjoern Bidar <bjorn.bidar@thaodan.de> writes:
> What could be the way that GTK is used or is emacs with pgtk 99% a run of the
> mill gtk app?
Emacs isn't a run-of-the-mill GTK app, but we only use what the
platform-independent parts of what the GTK developers expose.
> I don't know, can someone ask? I feel like these people act like douches when
> some random person asks.
They behave that way no matter who asks, which is why most people have
already given up trying to interact with them. Simple example:
apparently, all the GTK developers have expensive monitors, so modern
font rendering techniques that improve font rendering on Full-HD
monitors have been deleted from GTK 4, and anyone who complains is given
some ridiculous excuse along the lines of "expensive monitors are the
future" and "subpixel font anti-aliasing is not adaptable to our
rendering pipeline", even though multiple people have already proposed
patches that demonstrate the opposite.
next prev parent reply other threads:[~2022-08-08 10:10 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-04 7:36 bug#56967: 29.0.50; Frequent crashes under Wayland Bjoern Bidar via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-08-04 8:01 ` Eli Zaretskii
[not found] ` <3230275.qDoO4GC8Cx@odin>
2022-08-04 8:21 ` Eli Zaretskii
2022-08-04 11:49 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-08-05 0:18 ` Bjoern Bidar via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-08-05 0:50 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-08-05 6:25 ` Eli Zaretskii
2022-08-05 6:28 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-08-05 6:43 ` Eli Zaretskii
2022-08-05 6:53 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-08-05 7:46 ` Eli Zaretskii
2022-08-05 8:26 ` Bjoern Bidar via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-08-05 8:38 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-08-05 6:56 ` Bjoern Bidar via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-08-05 6:59 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-08-05 11:40 ` Gregory Heytings
2022-08-05 11:50 ` Eli Zaretskii
[not found] ` <2972937.jrzt3BHeHG@odin>
2022-08-05 6:29 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-08-07 14:51 ` Bjoern Bidar via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-08-07 15:07 ` Eli Zaretskii
2022-08-07 15:14 ` Bjoern Bidar via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-08-07 15:44 ` Eli Zaretskii
2022-08-08 2:42 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-08-08 2:40 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-08-08 6:07 ` Bjoern Bidar via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-08-08 8:56 ` Bjoern Bidar via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-08-08 10:10 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors [this message]
2022-12-13 12:10 ` Björn Bidar via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-12-13 12:10 ` Björn Bidar via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-12-13 13:11 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-12-13 17:06 ` Björn Bidar via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-08-05 6:31 ` Bjoern Bidar via Bug reports for GNU Emacs, the Swiss army knife of text editors
[not found] ` <2189728.upBv5HjrgE@odin>
2022-08-05 6:31 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
[not found] ` <1917872.q2Y8mqo1ke@odin>
2022-08-05 6:35 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-08-05 6:55 ` Bjoern Bidar via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-08-05 7:01 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-11-17 16:02 ` Gavin Massingham
[not found] <CAH3b6=SPM_Pys81fi-_Eu=VXO8mETqV+s0YFC+8c1huv4dmh9Q@mail.gmail.com>
2022-08-04 18:29 ` Eli Zaretskii
2022-08-05 7:34 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
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=87r11rqc4j.fsf@yahoo.com \
--to=bug-gnu-emacs@gnu.org \
--cc=56967@debbugs.gnu.org \
--cc=bjorn.bidar@thaodan.de \
--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 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.