public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Orgad Shaneh <orgads@gmail.com>
To: Takashi Yano <takashi.yano@nifty.ne.jp>
Cc: cygwin@cygwin.com, Johannes Schindelin <Johannes.Schindelin@gmx.de>
Subject: Re: VS Code is missing a few characters when running launch task in Git Bash
Date: Sun, 3 Jul 2022 16:02:46 +0300	[thread overview]
Message-ID: <CAGHpTBJkx=2MvkXoMk3aHrkiWj=sKM+rJ7vvW861x3koP1T2bQ@mail.gmail.com> (raw)
In-Reply-To: <20220703081728.a6050dd874181f3810a48a94@nifty.ne.jp>

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.

Examples:
Good:
$  cd F:\\Projects\\VoiceAIConnector/session-manager/dist ;
/usr/bin/env 'NODE_OPTIONS=--require
"c:/Users/orgads/AppData/Local/Programs/Microsoft VS
Code/resources/app/extensions/ms-vscode.js-debug/src/bootloader.bundle.js"
--inspect-publish-uid=http'
'VSCODE_INSPECTOR_OPTIONS={"inspectorIpc":"\\\\.\\pipe\\node-cdp.2260-6.sock","deferredMode":false,"waitForDebugger":"","execPath":"C:\\Program
Files\\nodejs\\node.exe","onlyEntrypoint":false,"autoAttachMode":"always","fileCallback":"C:\\Users\\orgads\\AppData\\Local\\Temp\\node-debug-callback-92e9f97c5ea0c8b4"}'
C:\\Program\ Files\\nodejs\\node.exe
.\\..\\node_modules\\mocha\\bin\\_mocha --timeout 0 -r
tsconfig-paths/register test/unit-test/ssml.test.js

Bad 1:
All the part between the stars is gone (offsets are counted from the $
in the "good" command):
* Offset 187-209: ms-vsc**ode.js-debug/src/bootl**oader.bundle.js
* Offset 373-417: "execPath":"C:\\Progr**am Files\\nodejs\\node**.exe"
* Offset 603-625: C:\\Program\ Files\\nodejs\\node.e**xe
.\\..\\node_modules**\\mocha\\bin\\_mocha

$  cd F:\\Projects\\VoiceAIConnector/session-manager/dist ;
/usr/bin/env 'NODE_OPTIONS=--require
"c:/Users/orgads/AppData/Local/Programs/Microsoft VS
Code/resources/app/extensions/ms-vscoader.bundle.js"
--inspect-publish-uid=http'
'VSCODE_INSPECTOR_OPTIONS={"inspectorIpc":"\\\\.\\pipe\\node-cdp.2260-6.sock","deferredMode":false,"waitForDebugger":"","execPath":"C:\\Progr.exe","onlyEntrypoint":false,"autoAttachMode":"always","fileCallback":"C:\\Users\\orgads\\AppData\\Local\\Temp\\node-debug-callback-49cb84aaa44af289"}'
C:\\Program\ Files\\nodejs\\node.e\\mocha\\bin\\_mocha --timeout 0 -r
tsconfig-paths/register test/unit-test/ssml.test.js

Bad 2:
Same + b jumped from ** to ## (offset 568 -> 586 in this command):
\\mocha\\**in\\_mocha --timeo##b##ut 0 -r
$  cd F:\\Projects\\VoiceAIConnector/session-manager/dist ;
/usr/bin/env 'NODE_OPTIONS=--require
"c:/Users/orgads/AppData/Local/Programs/Microsoft VS
Code/resources/app/extensions/ms-vscoader.bundle.js"
--inspect-publish-uid=http'
'VSCODE_INSPECTOR_OPTIONS={"inspectorIpc":"\\\\.\\pipe\\node-cdp.2260-7.sock","deferredMode":false,"waitForDebugger":"","execPath":"C:\\Progr.exe","onlyEntrypoint":false,"autoAttachMode":"always","fileCallback":"C:\\Users\\orgads\\AppData\\Local\\Temp\\node-debug-callback-945eb8360380780f"}'
C:\\Program\ Files\\nodejs\\node.e\\mocha\\in\\_mocha --timeobut 0 -r
tsconfig-paths/register test/unit-test/ssml.test.js

Bad 3:
Same as 1 + s and e jumped from ** to ## (offsets 201 and 209 ->
229-230): ms-vscoader.bundle.j**" --insp**ct-publish-uid=http'##se##
$  cd F:\\Projects\\VoiceAIConnector/session-manager/dist ;
/usr/bin/env 'NODE_OPTIONS=--require
"c:/Users/orgads/AppData/Local/Programs/Microsoft VS
Code/resources/app/extensions/ms-vscoader.bundle.j"
--inspct-publish-uid=http'se
'VSCODE_INSPECTOR_OPTIONS={"inspectorIpc":"\\\\.\\pipe\\node-cdp.2260-8.sock","deferredMode":false,"waitForDebugger":"","execPath":"C:\\Progr.exe","onlyEntrypoint":false,"autoAttachMode":"always","fileCallback":"C:\\Users\\orgads\\AppData\\Local\\Temp\\node-debug-callback-dcc14f60d807e31f"}'
C:\\Program\ Files\\nodejs\\node.e\\mocha\\bin\\_mocha --timeout 0 -r
tsconfig-paths/register test/unit-test/loader.js

The binary was built here:
https://github.com/msys2/msys2-runtime/pull/96/checks (Artifacts ->
install).

- Orgad

  reply	other threads:[~2022-07-03 13:02 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 [this message]
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='CAGHpTBJkx=2MvkXoMk3aHrkiWj=sKM+rJ7vvW861x3koP1T2bQ@mail.gmail.com' \
    --to=orgads@gmail.com \
    --cc=Johannes.Schindelin@gmx.de \
    --cc=cygwin@cygwin.com \
    --cc=takashi.yano@nifty.ne.jp \
    /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).