From: Takashi Yano <takashi.yano@nifty.ne.jp>
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: Mon, 4 Jul 2022 08:40:54 +0900 [thread overview]
Message-ID: <20220704084054.390c9a1007838e83d0ffea5a@nifty.ne.jp> (raw)
In-Reply-To: <CAGHpTBJkx=2MvkXoMk3aHrkiWj=sKM+rJ7vvW861x3koP1T2bQ@mail.gmail.com>
On Sun, 3 Jul 2022 16:02:46 +0300
Orgad Shaneh wrote:
> On Sun, Jul 3, 2022 at 2:18 AM Takashi Yano <takashi.yano@nifty.ne.jp> wrote:
> >
> > On Sat, 2 Jul 2022 08:34:06 +0900
> > Takashi Yano wrote:
> > > Thanks. I could reproduce the issue. I will submit a patch
> > > for this issue shortly.
> >
> > Does the patch I pushd to cygwin-3_3-branch solve the
> > VS Code issue?
>
>
> Hi Takashi,
>
> Thank you.
>
> I think it is a bit better, and the paste issue is solved, but VS Code
> still mistypes a few characters, and discards some quite long
> sections.
Perhaps, VS code issue is a separate issue from the issue of
pasting long text.
Could you please let me know the steps how to reproduce the
issue?
--
Takashi Yano <takashi.yano@nifty.ne.jp>
next prev parent reply other threads:[~2022-07-03 23:41 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
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 [this message]
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=20220704084054.390c9a1007838e83d0ffea5a@nifty.ne.jp \
--to=takashi.yano@nifty.ne.jp \
--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).