git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Steven Penny <svnpenn@gmail.com>
To: Johannes Schindelin <Johannes.Schindelin@gmx.de>
Cc: git@vger.kernel.org
Subject: Re: Change Native Windows shell
Date: Mon, 8 Jun 2020 18:14:05 -0500	[thread overview]
Message-ID: <CAAXzdLVmuONmow6cB-kko8-CkP2sA=UfpPBkiXqSCuTacGsFWA@mail.gmail.com> (raw)
In-Reply-To: <nycvar.QRO.7.76.6.2006081935530.482@ZVAVAG-DN14RQO.ybpnyqbznva>

On Mon, Jun 8, 2020 at 5:46 PM Johannes Schindelin wrote:
> That assumes that PowerShell is installed, which is not guaranteed,
> either.
>
> Besides, quoting rules are most likely different with PowerShell than what
> Git assumes, so you will have to take care of that, too.
>
> Finally, there are plenty of tips out there in the internet that simply
> expect a POSIX shell to execute those script snippets. Any user would be
> completely (and unnnecessarily) puzzled if those snippets won't work with
> their Git for Windows.
>
> In short: it would be unwise for me to accept this change into Git for
> Windows, at least as-is.

I found a workaround. It seems as long as PAGER or similar is not get, then
Git just tries to call `less.exe`. I didnt realize when I first posted this,
but native Windows Less is available:

https://github.com/jftuga/less-Windows/releases

So I am just bundling that with my Windows native Git:

https://github.com/nu8/gulf/releases

  reply	other threads:[~2020-06-09  0:36 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-06-04 23:33 Change Native Windows shell Steven Penny
2020-06-05  0:00 ` brian m. carlson
2020-06-05  4:21   ` Steven Penny
2020-06-05  4:39     ` Jonathan Nieder
2020-06-08 17:39     ` Johannes Schindelin
2020-06-08 23:14       ` Steven Penny [this message]
2020-06-09  6:12         ` Johannes Schindelin

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: http://vger.kernel.org/majordomo-info.html

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='CAAXzdLVmuONmow6cB-kko8-CkP2sA=UfpPBkiXqSCuTacGsFWA@mail.gmail.com' \
    --to=svnpenn@gmail.com \
    --cc=Johannes.Schindelin@gmx.de \
    --cc=git@vger.kernel.org \
    /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://80x24.org/mirrors/git.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).