From: Dmitry Gutov <dmitry@gutov.dev>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 65763@debbugs.gnu.org, pogonyshev@gmail.com
Subject: bug#65763: Error opening a file from a Git working directory if Git is not installed
Date: Wed, 6 Sep 2023 18:59:00 +0300 [thread overview]
Message-ID: <6a42daae-db48-4c81-8121-79515ac94bf9@gutov.dev> (raw)
In-Reply-To: <83jzt31ez5.fsf@gnu.org>
On 06/09/2023 18:46, Eli Zaretskii wrote:
> I prefer to emit the messages, just make them more user-friendly
> ("searching for program" "no such file or directory" is not very
> friendly, IMO), and suppress the error signaling even when
> debug-on-error is non-nil. The reason is simple: we are talking only
> about Git not being installed or accessible here, but the problems
> could be different and more obscure: Git could be present but
> inoperable for some weird misconfiguration reason, or some other
> problem could happen. So "if it is not installed, just silently don't
> do anything" is not a complete solution, and the "silently" part loses
> information which users may wish to have presented to them.
That also sounds good to me.
next prev parent reply other threads:[~2023-09-06 15:59 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-05 18:54 bug#65763: Error opening a file from a Git working directory if Git is not installed Paul Pogonyshev
2023-09-05 19:44 ` Eli Zaretskii
2023-09-05 20:06 ` Paul Pogonyshev
2023-09-05 20:14 ` Paul Pogonyshev
2023-09-06 2:25 ` Eli Zaretskii
2023-09-06 7:29 ` Paul Pogonyshev
2023-09-06 12:13 ` Eli Zaretskii
2023-09-06 12:35 ` Dmitry Gutov
2023-09-06 12:49 ` Paul Pogonyshev
2023-09-06 12:52 ` Dmitry Gutov
2023-09-06 13:11 ` Paul Pogonyshev
2023-09-06 14:31 ` Dmitry Gutov
2023-09-06 15:46 ` Eli Zaretskii
2023-09-06 15:59 ` Dmitry Gutov [this message]
2023-09-10 6:26 ` Eli Zaretskii
2023-09-10 13:21 ` Dmitry Gutov
2023-09-10 13:40 ` Eli Zaretskii
2023-09-10 17:36 ` Paul Pogonyshev
2023-09-10 17:52 ` Eli Zaretskii
2023-09-06 13:06 ` 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=6a42daae-db48-4c81-8121-79515ac94bf9@gutov.dev \
--to=dmitry@gutov.dev \
--cc=65763@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=pogonyshev@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).