public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Adam Dinwoodie <adam@dinwoodie.org>
To: cygwin@cygwin.com
Cc: Orgad Shaneh <orgads@gmail.com>,
	Johannes Schindelin <Johannes.Schindelin@gmx.de>
Subject: Re: VS Code is missing a few characters when running launch task in Git Bash
Date: Fri, 27 May 2022 08:59:49 +0100	[thread overview]
Message-ID: <20220527075949.caeyh2d65fhmumss@lucy.dinwoodie.org> (raw)
In-Reply-To: <CAGHpTBK=NbN4DAzgJC-KrDMNYXBAxNYXDn7gCPrHGSNwXp+Z5g@mail.gmail.com>

On Fri, May 27, 2022 at 10:15:18AM +0300, Orgad Shaneh wrote:
> Hi,
> 
> I'm using Git Bash as the default terminal in VS Code. Using Git for
> Windows 2.36.1 with the latest runtime, based on cygwin 3.5.0.

Hi Orgad,

Git for Windows and Git Bash are based in part on Cygwin, but they're
downstream projects that aren't supported by the Cygwin mailing list:
the Git for Windows folks have made changes to the Cygwin code for their
use case, which they're 100% welcome to do, but which mean the folk on
the Cygwin mailing list just don't have the knowledge or experience to
help.

If you can show problems with Cygwin, be that with the Cygwin DLL,
Cygwin's Bash or Cygwin's Git, the Cygwin mailing lists are definitely
the right place to ask for help.  But unless you can demonstrate the
problem using Cygwin packages without any downstream modifications, this
list isn't going to be able to help you.

Based on https://gitforwindows.org/ I suspect your best bet for getting
help here is either (a) asking on the Git for Windows mailing list at
https://groups.google.com/g/git-for-windows, or (b) raising an issue at
https://github.com/git-for-windows/git.

HTH

Adam
Cygwin Git maintainer

  reply	other threads:[~2022-05-27  7:59 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-27  7:15 Orgad Shaneh
2022-05-27  7:59 ` Adam Dinwoodie [this message]
2022-05-27  8:06   ` Orgad Shaneh
2022-05-27 12:22     ` Orgad Shaneh
2022-05-27 12:43       ` Takashi Yano
2022-05-29  6:00         ` Orgad Shaneh
2022-06-30 22:02           ` Orgad Shaneh
2022-06-30 22:08             ` Orgad Shaneh
2022-07-01 14:14               ` Johannes Schindelin
2022-07-01 23:34             ` Takashi Yano
2022-07-02 23:17               ` Takashi Yano
2022-07-03 13:02                 ` Orgad Shaneh
2022-07-03 23:40                   ` Takashi Yano
2022-07-04  5:57                     ` Orgad Shaneh
2022-07-05  3:17                       ` Takashi Yano
2022-07-05 11:18                         ` Orgad Shaneh

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=20220527075949.caeyh2d65fhmumss@lucy.dinwoodie.org \
    --to=adam@dinwoodie.org \
    --cc=Johannes.Schindelin@gmx.de \
    --cc=cygwin@cygwin.com \
    --cc=orgads@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.
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).