From: Tim Cross <theophilusx@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: luangruo@yahoo.com, jporterbugs@gmail.com,
spwhitton@spwhitton.name, emacs-devel@gnu.org
Subject: Re: PGTK-related misconceptions
Date: Tue, 19 Apr 2022 18:13:03 +1000 [thread overview]
Message-ID: <87k0bltq2h.fsf@gmail.com> (raw)
In-Reply-To: <83sfq9vcod.fsf@gnu.org>
Eli Zaretskii <eliz@gnu.org> writes:
>> From: Tim Cross <theophilusx@gmail.com>
>> Date: Tue, 19 Apr 2022 12:18:07 +1000
>> Cc: Po Lu <luangruo@yahoo.com>, emacs-devel@gnu.org,
>> Sean Whitton <spwhitton@spwhitton.name>
>>
>> I agree. I think this is the main point being missed by others who have
>> argued the existing documentation is clear enough. Like it or not,
>> people often don't read the documentation or NEWS file carefully. There
>> is also a tendency for people to believe any new feature is an
>> improvement and I suspect many people will think a pure GTK build is
>> going to be better than a hybrid X/GTK one.
>>
>> We should just add a very explicit and clear warning not to use
>> --with-pgtk if your running under X and put this statement right at the
>> beginning of the section in the NEWS file about this new option.
>
> Aren't you contradicting yourself here? If people don't read
> documentation, how can any addition to the documentation solve this
> issue? (Of course, I don't object to saying something in INSTALL
> about that, just pointing out that it's hard to have it both ways.)
>
Eli, rather ironically you just proved my point. I didn't say they
didn't read the documentation, I said they didn't read it carefully.
Just like you did with my post, they skim read it and can easily miss
crucial points. The fact people are building with pgtk when only running
under X would tend to indicate the messaging is not adequate. Making a
clear concise statement not to use pgtk when using X early, even at the
start, would increase the likelihood skim readers see it.
>> It might even be worthwhile adding a warning in configure as well (like
>> the one we have about pop support).
>
> I object to annoying people who build Emacs with such warnings.
> Besides, warnings (as opposed to errors) in the configure script are
> easily overlooked, because people tend to leave the build run
> unattended, and do other useful things while it runs.
>
I guess there not terribly annoying if they are easily overlooked!
Just like the warning about removal of pop support and pointer
to mail utils, this warning could be at the end of the build. At any
rate, seems like a more important warning than one about no longer
supporting pop3, which few mail providers support anymore anyway.
>> Like others, I expect many distributions are going to bundle
>> emacs-gtk believing it is an improvement. I suspect it is going to
>> be a bigger issue given that some popular distributions, like
>> fedora, will be shipping with wayland as their default but there
>> will likely be many who will choose to switch back to X, but then be
>> faced with an Emacs built with pgtk to better support the default
>> wayland setup.
>
> IME, there's nothing we can do against such misconceptions. We will
> get bug reports and will respond by pointing people to NEWS and
> INSTALL. Eventually, enough people will bump into this to realize the
> truth, and the issue will go away. No catastrophe that I could spot,
> and no need to get too excited.
You do seem to like jumping to extremes. I don't think anyone has been
screaming catastrophe. All I've seen is people asking to make this more
obvious and explicit. Maybe it won't make a big difference, but then
again, maybe it will. The cost of making the limitations of pgtk more
explicit in NEWS and INSTALL is very low and even if it only stops a few
people from doing the wrorng build, reporting a 'non-bug' and getting
directed back to NEW/INSTALL and having to rebuild, I think the cost has
been justified.
next prev parent reply other threads:[~2022-04-19 8:13 UTC|newest]
Thread overview: 56+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-12 4:56 bug#53200: 29.0.50; C-S-u shortcut fails with 'PGTK' enable Campbell Barton
2022-01-12 6:24 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-01-13 7:08 ` Lars Ingebrigtsen
2022-01-13 8:04 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-04-15 2:01 ` Morgan Smith
2022-04-15 2:29 ` PGTK-related misconceptions Po Lu
2022-04-15 7:11 ` Byung-Hee HWANG
2022-04-15 16:24 ` Eric Abrahamsen
2022-04-18 5:18 ` Sean Whitton
2022-04-18 5:31 ` Po Lu
2022-04-18 5:43 ` Sean Whitton
2022-04-18 5:57 ` Po Lu
2022-04-18 18:27 ` Sean Whitton
2022-04-18 19:49 ` Jim Porter
2022-04-19 1:02 ` Po Lu
2022-04-19 2:46 ` Sean Whitton
2022-04-19 2:18 ` Tim Cross
2022-04-19 5:56 ` Eli Zaretskii
2022-04-19 8:13 ` Tim Cross [this message]
2022-04-19 10:32 ` Eli Zaretskii
2022-04-19 9:10 ` Dirk-Jan C. Binnema
2022-04-19 10:42 ` Po Lu
2022-04-19 11:53 ` Phil Sainty
2022-04-19 13:58 ` Sean Whitton
2022-04-20 3:29 ` Phil Sainty
2022-04-20 4:48 ` Stefan Monnier
2022-04-19 16:51 ` Yuri Khan
2022-04-22 5:44 ` Pankaj Jangid
2022-05-22 16:25 ` bug#53200: 29.0.50; C-S-u shortcut fails with 'PGTK' enable daanturo
2022-05-22 17:44 ` Morgan Smith
2022-05-23 0:55 ` 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-04-18 21:50 PGTK-related misconceptions Trey
2022-04-19 0:59 ` Po Lu
2022-04-19 3:28 ` Trey Peacock
2022-04-19 4:27 ` Po Lu
2022-04-19 23:02 ` Trey Peacock
2022-04-20 0:48 ` Po Lu
2022-04-20 2:33 ` Trey Peacock
2022-04-20 4:05 ` Po Lu
2022-07-25 21:18 ` Akira Kyle
2022-07-26 2:08 ` Po Lu
2022-07-26 12:10 ` Lars Ingebrigtsen
2022-07-26 12:35 ` Po Lu
2022-07-29 14:26 ` Stefan Monnier
2022-07-30 0:58 ` Po Lu
2022-07-26 21:36 ` Akira Kyle
2022-07-27 2:48 ` Po Lu
2022-07-27 8:34 ` Trey Peacock
2022-07-27 9:10 ` Po Lu
2022-07-27 13:45 ` Trey Peacock
2022-07-27 13:52 ` Po Lu
2022-07-28 1:39 ` Akira Kyle
2022-07-28 2:50 ` Po Lu
2022-04-20 7:52 Trey Peacock
2022-04-20 8:25 ` Po Lu
2022-04-20 13:13 ` Brian Cully
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=87k0bltq2h.fsf@gmail.com \
--to=theophilusx@gmail.com \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=jporterbugs@gmail.com \
--cc=luangruo@yahoo.com \
--cc=spwhitton@spwhitton.name \
/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.