From: Po Lu via "Bug reports for GNU Emacs, the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
To: Daniel Colascione <dancol@dancol.org>
Cc: 57012@debbugs.gnu.org
Subject: bug#57012: Activating versus raising frames
Date: Sun, 07 Aug 2022 13:27:40 +0800 [thread overview]
Message-ID: <87bkswy65v.fsf@yahoo.com> (raw)
In-Reply-To: <18276abbdd8.2829.cc5b3318d7e9908e2c46732289705cb0@dancol.org> (Daniel Colascione's message of "Sun, 07 Aug 2022 00:59:03 -0400")
Daniel Colascione <dancol@dancol.org> writes:
> 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.
How about adding a warning to configure.ac instead? Do you think those
users will read that?
next prev parent reply other threads:[~2022-08-07 5:27 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
2022-08-07 5:27 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors [this message]
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=87bkswy65v.fsf@yahoo.com \
--to=bug-gnu-emacs@gnu.org \
--cc=57012@debbugs.gnu.org \
--cc=dancol@dancol.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).