git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: "brian m. carlson" <sandals@crustytoothpaste.net>
To: theking2@king.ma
Cc: git@vger.kernel.org
Subject: Re: Offer Windows Terminal as option for terminal emulation
Date: Fri, 7 Jan 2022 10:23:04 +0000	[thread overview]
Message-ID: <YdgUiNL653Ib8iul@camp.crustytoothpaste.net> (raw)
In-Reply-To: <d45a1072c8fec95896cf82b5620f7219@king.ma>

[-- Attachment #1: Type: text/plain, Size: 1162 bytes --]

On 2022-01-07 at 08:12:08, theking2@king.ma wrote:
> Since Windows 11 an acceptable terminal program comes with the OS as
> replacement for cmd.exe. There is no need to install yet another terminal
> emulator MinTTY

Hey,

It looks like you probably wanted to write to the Git for Windows
project, and I'd recommend their issue tracker at
https://github.com/git-for-windows/git/issues.  As a non-Windows user, I
don't know why this decision has been made and whether there were any
reasons for doing it, but it's a part of Git for Windows and not Git
proper.

I do know that in the past, Windows Terminal has had some serious
compliance bugs: it claimed to be xterm-256color (instead of the correct
ms-terminal) and failed to implement enough features that it broke Vim
in many cases, which obviously wouldn't be suitable.

However, I think that's been fixed, and it may function correctly now
that it's supportable as an option, but you'd have to ask the Git for
Windows project why they don't have that option.  They may be delighted
to off an option to have less code.
-- 
brian m. carlson (he/him or they/them)
Toronto, Ontario, CA

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 262 bytes --]

      reply	other threads:[~2022-01-07 10:23 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-07  8:12 Offer Windows Terminal as option for terminal emulation theking2
2022-01-07 10:23 ` brian m. carlson [this message]

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=YdgUiNL653Ib8iul@camp.crustytoothpaste.net \
    --to=sandals@crustytoothpaste.net \
    --cc=git@vger.kernel.org \
    --cc=theking2@king.ma \
    /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).