public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
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: Tue, 5 Jul 2022 12:17:47 +0900	[thread overview]
Message-ID: <20220705121747.4ab92c43cf4b9fa706bf28f0@nifty.ne.jp> (raw)
In-Reply-To: <CAGHpTBKVMMpWOfqnMqESf0Zfr5ia8wy3FHMz7RZfPTobK5NdbQ@mail.gmail.com>

On Mon, 4 Jul 2022 08:57:09 +0300
Orgad Shaneh wrote:
> Sure,
> 
> Install VS Code and Node.JS.
> 
> Clone this repository: https://github.com/orgads/cygtest
> 
> Open the directory in VS Code and run (F5). Wait for it to finish,
> then run again.
> 
> I've noticed that even the first execution has some mistyped
> characters (moved from ** to ##):
> 
> waitForDeb**u**gge**r**
> "exe**c**Path":"C:\\Program Fil**es**\\nodejs\\node.exe"
> "autoAttachMod##urces##e":"always"
> 
> And on the second run:
> "inspecto**r**Ipc":"\\\\.\\pipe\\node-cdp.9412-8.sock","##r##deferredMode":false
> 
> $  /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.9412-7.sock","deferredMode":false,"waitForDebgge":"","exePath":"C:\\Program
> Fil\\nodejs\\node.exe","onlyEntrypoint":false,"autoAttachModurcese":"always","fileCallback":"C:\\Users\\orgads\\AppData\\Local\\Temp\\node-debug-callback-c57206c2f20dca1d"}'
> C:\\Program\ Files\\nodejs\\node.exe index.js
> hi
> 
> $  cd f:\\Projects\\cygtest ; /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={"inspectoIpc":"\\\\.\\pipe\\node-cdp.9412-8.sock","rdeferredMode":false,"waitForDebugger":"","execPath":"C:\\Program
> Files\\nodejs\\node.exe","onlyEntrypoint":false,"autoAttachMode":"always","fileCallback":"C:\\Users\\orgads\\AppData\\Local\\Temp\\node-debug-callback-fab5a0d7b63917c7"}'
> C:\\Program\ Files\\nodejs\\node.exe index.js
> hi

Thanks.

Could you please test if the commit
https://www.cygwin.com/git/?p=newlib-cygwin.git;a=commitdiff;h=521dfff143f9533533d161f37b73a92147c88e7c
fixes the issue?

-- 
Takashi Yano <takashi.yano@nifty.ne.jp>

  reply	other threads:[~2022-07-05  3:18 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
2022-07-04  5:57                     ` Orgad Shaneh
2022-07-05  3:17                       ` Takashi Yano [this message]
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=20220705121747.4ab92c43cf4b9fa706bf28f0@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).