From: Eli Zaretskii <eliz@gnu.org>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: lekktu@gmail.com, emacs-devel@gnu.org
Subject: Re: emacs-repository-{version|branch} on Windows
Date: Sat, 05 Nov 2022 08:24:57 +0200 [thread overview]
Message-ID: <83pme1535y.fsf@gnu.org> (raw)
In-Reply-To: <jwv8rkqto3t.fsf-monnier+emacs@gnu.org> (message from Stefan Monnier on Fri, 04 Nov 2022 17:20:31 -0400)
> From: Stefan Monnier <monnier@iro.umontreal.ca>
> Cc: lekktu@gmail.com, emacs-devel@gnu.org
> Date: Fri, 04 Nov 2022 17:20:31 -0400
>
> >> Maybe the better way forward is to tweak the code so it doesn't silence
> >> this kind of error.
> > Then you'd hit a much worse extremity: that the user is annoyed by
> > problems most of them don't understand and don't want to know about.
>
> Not necessarily, depends when/where we show the error. AFAIK this code
> is run while building Emacs, so emitting an error during compilation
> wouldn't be too intrusive (as long as it doesn't prevent the build from
> succeeding).
> Or we could put the error message into those vars.
Those errors show in each and every file-related operation.
next prev parent reply other threads:[~2022-11-05 6:24 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-04 18:24 emacs-repository-{version|branch} on Windows Juanma Barranquero
2022-11-04 18:36 ` Juanma Barranquero
2022-11-04 18:51 ` Eli Zaretskii
2022-11-04 18:58 ` Juanma Barranquero
2022-11-04 19:28 ` Stefan Monnier
2022-11-04 20:08 ` Juanma Barranquero
2022-11-04 20:29 ` Eli Zaretskii
2022-11-04 20:42 ` Juanma Barranquero
2022-11-04 20:47 ` Stefan Monnier
2022-11-04 20:56 ` Eli Zaretskii
2022-11-04 21:09 ` Juanma Barranquero
2022-11-04 21:20 ` Stefan Monnier
2022-11-05 6:24 ` Eli Zaretskii [this message]
2022-11-05 11:43 ` Juanma Barranquero
2022-11-05 12:36 ` Eli Zaretskii
2022-11-05 13:20 ` Juanma Barranquero
2022-11-05 15:19 ` Stefan Monnier
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=83pme1535y.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=lekktu@gmail.com \
--cc=monnier@iro.umontreal.ca \
/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).