From: Eric Sunshine <sunshine@sunshineco.com>
To: Jeff King <peff@peff.net>
Cc: Junio C Hamano <gitster@pobox.com>,
"brian m. carlson" <sandals@crustytoothpaste.net>,
M Douglas McIlroy <m.douglas.mcilroy@dartmouth.edu>,
Git List <git@vger.kernel.org>
Subject: Re: default editor
Date: Sun, 7 Feb 2021 16:57:07 -0500 [thread overview]
Message-ID: <CAPig+cQ=nR7O+uNAufB7ohKN2ZoUP6n1aLbZBz2jeFKMFbaAcA@mail.gmail.com> (raw)
In-Reply-To: <YCAzcs1e08Qnk2wa@coredump.intra.peff.net>
On Sun, Feb 7, 2021 at 1:38 PM Jeff King <peff@peff.net> wrote:
> The "2l" was bogus (there is no line 2). It seems likely that an
> interactive user might make at least one invalid command while editing.
> Some versions (like GNU ed) have a "-l" option to loosen the exit code.
Cygwin `ed` does support `-l`, so that's helpful, although it still
fails the "test editor" button in the Git-For-Windows installer
program since the installer calls `ed` with a Windows style path
rather than a Unix style path which Cygwin `ed` doesn't understand. It
is possible to skip "test editor" and continue Git-For-Windows
installation without testing. The bigger problem after that, at least
in my testing, is that when `git` from Git-For-Windows itself
eventually launches Cygwin `ed` at commit time, it bombs with:
0 [main] ed (2444) C:\cygwin64\bin\ed.exe: *** fatal error -
cygheap base mismatch detected - 0x18034C408/0x180347408.
In fact, Cygwin `ed` crashes with that same problem even just being
launched from the MSYS shell provided by Git-For-Windows due to bad
interaction between the DLL's. On the other hand, Cygwin `ed` launches
just fine from the Cygwin shell as one would expect.
By the way, it's also possible to install Cygwin's Git from the Cygwin
installer rather than attempting to use the Git provided by the
Git-For-Windows project. The combination of Cygwin `ed` and Cygwin
`git` works just fine (in my tests) once you configure `ed` as the Git
editor either by setting GIT_EDITOR or EDITOR environment variables to
`ed -l` or by configuring git itself:
git config --global --add core.config 'ed -l'
(You would want to uninstall Git-For-Windows, too, if you have it installed.)
next prev parent reply other threads:[~2021-02-07 21:58 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-07 13:24 default editor M Douglas McIlroy
2021-02-07 17:35 ` brian m. carlson
2021-02-07 18:12 ` Junio C Hamano
2021-02-07 18:37 ` Jeff King
2021-02-07 19:09 ` brian m. carlson
2021-02-07 21:57 ` Eric Sunshine [this message]
2021-02-08 10:03 ` Adam Dinwoodie
2021-02-11 15:15 ` M Douglas McIlroy
2021-02-12 6:03 ` Eric Sunshine
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='CAPig+cQ=nR7O+uNAufB7ohKN2ZoUP6n1aLbZBz2jeFKMFbaAcA@mail.gmail.com' \
--to=sunshine@sunshineco.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=m.douglas.mcilroy@dartmouth.edu \
--cc=peff@peff.net \
--cc=sandals@crustytoothpaste.net \
/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;
as well as URLs for NNTP newsgroup(s).