Re: Bug: Cannot kill Nodejs process using ctrl + c
- From
Stefan Beller <sbeller@google.com>
- Date
- Jun 27, 2017, 03:15 UTC
- Message-ID
- <CAGZ79kZ94Qh4CzCUWNYQQU5EB+Oky13gcp09tBKSYoCaFvqOuA@mail.gmail.com>
- In-Reply-To
- <CAHaNChdhg-nHv34-jgumeKw8iJXaXwfY2DAe797nRXPU1VzT3Q@mail.gmail.com>
I miss-read your email.
So you are not running Git, but only talk about the (Git-)bash that is conveniently bundled with Git for Windows? For that I recommend https://github.com/git-for-windows/git/issues/new
Johannes Schindelin the GfW maintainer is cc'd here as well, but AFAICT he prefers Github issues.
On Mon, Jun 26, 2017 at 8:08 PM, Gyandeep Singh <gyandeeps@gmail.com> wrote:
Show 28 quoted lines
> 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?