git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: Bug: Cannot kill Nodejs process using ctrl + c

From
Gyandeep Singh <gyandeeps@gmail.com>
Date
Jun 27, 2017, 03:08 UTC
Message-ID
<CAHaNChdhg-nHv34-jgumeKw8iJXaXwfY2DAe797nRXPU1VzT3Q@mail.gmail.com>
In-Reply-To
<CAGZ79kYR_Vw454RBw7A7ygJdiOauzepVZXBb_CvsCoN9AGE-sA@mail.gmail.com>
Not sure what you mean by output. But its just goes back to normal like  this
Gyandeep@Gyandeep MINGW64 ~
$

It was working fine on first release of git 2.13. It broken with releases after that.

Will try with –no-pager flag and let you tomorrow.
Thanks

Gyandeep Regards,

Gyandeep Singh
Website: http://gyandeeps.com
On Mon, Jun 26, 2017 at 9:55 PM, Stefan Beller <sbeller@google.com> wrote:
> Which exact outputs of Git are invoked?
>
> Does it change when giving slightly different options e.g. --no-pager?
Previous: Stefan BellerNext: Stefan Beller
Message 3 of 7 in “Re: Bug: Cannot kill Nodejs process using ctrl + c”
  1. Gyandeep SinghJun 26, 2017
  2. Stefan BellerJun 27, 2017
  3. Gyandeep SinghJun 27, 2017
  4. Stefan BellerJun 27, 2017
  5. Gyandeep SinghJun 27, 2017
  6. Johannes SchindelinJun 28, 2017
  7. Johannes SchindelinJun 29, 2017

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.