unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Drew Adams via "Bug reports for GNU Emacs, the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: "tclwarrior@gmail.com" <tclwarrior@gmail.com>,
	"corwin@bru.st" <corwin@bru.st>,
	"71801@debbugs.gnu.org" <71801@debbugs.gnu.org>
Subject: bug#71801: emacs 29.4 windows binaries
Date: Sat, 6 Jul 2024 16:33:30 +0000	[thread overview]
Message-ID: <SJ0PR10MB54883B66E05C662220450A59F3D82@SJ0PR10MB5488.namprd10.prod.outlook.com> (raw)
In-Reply-To: <86sewm332e.fsf@gnu.org>

> If the user is the one who set up the
> development and run-time environment, then the user should fix it to
> be fully operable.  If the user just installed a binary distro, he/she
> should take this up to whoever produced the distro.
...
> It is a problem with the Emacs installation.  Who should fix it
> depends on how and by whom Emacs was built and installed.  Emacs
> itself cannot know that.
...
> Users who don't understand the warning will do what they always do:
> search the Internet or ask on known forums.
...
> > I don't understand the message, and it sounds
> > like someone needs to know something about
> > Emacs builds, its dependencies, and perhaps
> > native compilation.
> 
> That's okay.  Some warnings will invariably left not understood by
> some of the users, especially if they (users) lack background
> knowledge about what happens in that case.  The usual remedy is to
> ask.

Thank you for the more complete explanation.

Since there's no way for Emacs to know whether
the user seeing such a warning is one kind or
the other, consider including info such as this
in the warning (or linked from it, if it needs
to be a one-liner):

  There's a problem with this Emacs installation.
  If you installed a binary distro then please
  report it to whoever produced the distro.





  reply	other threads:[~2024-07-06 16:33 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-06-27 13:27 bug#71801: emacs 29.4 windows binaries Ali M.
2024-06-27 15:00 ` Eli Zaretskii
2024-06-27 19:34   ` Corwin Brust
2024-06-27 22:27     ` Drew Adams via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-07-05 11:56       ` Corwin Brust
2024-07-05 16:04         ` Drew Adams via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-07-05 18:25           ` Eli Zaretskii
2024-07-05 19:33             ` Drew Adams via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-07-05 21:52               ` Corwin Brust
2024-07-05 22:38                 ` Drew Adams via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-07-06 10:01                 ` Corwin Brust
2024-07-06 15:58                   ` Drew Adams via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-07-06  6:04               ` Eli Zaretskii
2024-07-06 15:33                 ` Drew Adams via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-07-06 16:20                   ` Eli Zaretskii
2024-07-06 16:33                     ` Drew Adams via Bug reports for GNU Emacs, the Swiss army knife of text editors [this message]
2024-07-06 16:49                       ` Corwin Brust
2024-07-06 17:26                         ` Eli Zaretskii

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=SJ0PR10MB54883B66E05C662220450A59F3D82@SJ0PR10MB5488.namprd10.prod.outlook.com \
    --to=bug-gnu-emacs@gnu.org \
    --cc=71801@debbugs.gnu.org \
    --cc=corwin@bru.st \
    --cc=drew.adams@oracle.com \
    --cc=eliz@gnu.org \
    --cc=tclwarrior@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 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).