From: "brian m. carlson" <sandals@crustytoothpaste.net>
To: John <john@quantbo.com>, git@vger.kernel.org
Subject: Re: GFW fails with ST3 on Windows 11
Date: Fri, 27 Oct 2023 11:24:32 +0000 [thread overview]
Message-ID: <ZTud8HxDxK1UgLCR@tapette.crustytoothpaste.net> (raw)
In-Reply-To: <e1de1948-8604-4c8f-961b-d214efa4ed84@app.fastmail.com>
[-- Attachment #1: Type: text/plain, Size: 2221 bytes --]
On 2023-10-27 at 09:59:47, John wrote:
> Brian,
>
> Thanks very much for your suggestions. Unfortunately, after each command, I continue to get the same error messages noted in my original email.
>
> Any Windows 11 experts out there--please help.
>
> John
>
> On Fri, 27 Oct 2023, at 16:25, brian m. carlson wrote:
> > On 2023-10-27 at 07:31:32, John wrote:
> >> I have been using Sublime Text 3 as the editor on Git for Windows for years, on Windows 10. I recently purchased a Windows 11 machine. On that machine, when I give GFW the following command, I get the response shown:
> >>
> >> $ git commit -a
> >> […]
> >> hint: Waiting for your editor to close the file… C:\Program Files\Sublime Text 3\sublime_text.exe: C:Program: command not found
> >> error: There was a problem with the editor ‘C:\Program Files\Sublime Text 3\sublime_text.exe’.
> >> Please supply the message using either -m or -F option.
> >
> > I think the "command not found" indicates that you may have specified
> > your editor incorrectly. In Git Bash, can you try the following
> > commands, one at a time, and then commit between each one to see if one
> > of them works?
> >
> > git config --global core.editor '"C:/Program Files/Sublime Text
> > 3/sublime_text.exe"'
> > git config --global core.editor '"C:\Program Files\Sublime Text
> > 3\sublime_text.exe"'
> >
> > I believe that both should work here.
> >
> > My guess is that this is the situation hinted at in the FAQ[0], where,
> > because the editor is passed to the shell (bash), you need to use double
> > quotes to prevent it from thinking that you have a program named
> > "C:\Program" with arguments "Files\Sublime", "Text", and
> > "3\sublime_text.exe".
> >
> > Hopefully this works; if not, please let us know, and hopefully someone
> > on the list who uses Windows can provide some help. I'm afraid that, as
> > a Linux user, I'm not able to provide more than a guess here.
> >
> > [0] https://git-scm.com/docs/gitfaq#configure-editor
It looks like this was sent to just me and not the list, so forwarding
it back for additional assistance.
--
brian m. carlson (he/him or they/them)
Toronto, Ontario, CA
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 263 bytes --]
next prev parent reply other threads:[~2023-10-27 11:24 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-27 7:31 GFW fails with ST3 on Windows 11 John
2023-10-27 9:25 ` brian m. carlson
[not found] ` <e1de1948-8604-4c8f-961b-d214efa4ed84@app.fastmail.com>
2023-10-27 11:24 ` brian m. carlson [this message]
2023-10-27 12:29 ` Konstantin Khomoutov
2023-10-27 12:37 ` Konstantin Khomoutov
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=ZTud8HxDxK1UgLCR@tapette.crustytoothpaste.net \
--to=sandals@crustytoothpaste.net \
--cc=git@vger.kernel.org \
--cc=john@quantbo.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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox