From: Daniel Colascione <dancol@dancol.org>
To: Po Lu <luangruo@yahoo.com>
Cc: 57012@debbugs.gnu.org
Subject: bug#57012: Activating versus raising frames
Date: Sun, 07 Aug 2022 00:59:03 -0400 [thread overview]
Message-ID: <18276abbdd8.2829.cc5b3318d7e9908e2c46732289705cb0@dancol.org> (raw)
In-Reply-To: <87zgggy8ux.fsf@yahoo.com>
[-- Attachment #1: Type: text/plain, Size: 1141 bytes --]
On August 7, 2022 00:29:36 Po Lu <luangruo@yahoo.com> wrote:
> Daniel Colascione <dancol@dancol.org> writes:
>
>> Then emit an error message at runtime if you detect them running on
>> X11 telling users that things will mysteriously. To let them build
>> and run pgtk initially, then get frustrated with a few edge cases, is
>> doing them a disservice. They're not going to read that
>> documentation.
>
> Why won't they?
Because, as a pragmatic matter, they don't. We're lucky if users read fatal
error messages. People don't have time to trawl through documentation
before trying something. They read about some cool new compilation mode on
Reddit (scanning just the post titles of course), them try it. It's not
that they're dumb. They've busy. It doesn't matter whether some file
somewhere says a scenario isn't supported: users are going to try that
scenario anyway if it plausibly looks like it might work, and when it
doesn't, they're going to think less of the whole project. I'd feel much
better if pgtk simply refused to start under X (explaining that it's not
supported) than silently give users a poor experience.
[-- Attachment #2: Type: text/html, Size: 2075 bytes --]
next prev parent reply other threads:[~2022-08-07 4:59 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-06 0:54 bug#57012: Activating versus raising frames Daniel Colascione
2022-08-06 1:44 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-08-06 23:57 ` Daniel Colascione
2022-08-07 1:55 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-08-07 2:07 ` Daniel Colascione
2022-08-07 2:45 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-08-07 2:52 ` Daniel Colascione
2022-08-07 3:02 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-08-07 3:11 ` Daniel Colascione
2022-08-07 3:29 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-08-07 4:10 ` Daniel Colascione
2022-08-07 4:29 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-08-07 4:59 ` Daniel Colascione [this message]
2022-08-07 5:27 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-10-20 11:30 ` 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
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=18276abbdd8.2829.cc5b3318d7e9908e2c46732289705cb0@dancol.org \
--to=dancol@dancol.org \
--cc=57012@debbugs.gnu.org \
--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 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).