Hi,
On Wed, 28 Jun 2017, Johannes Schindelin wrote:
> On Mon, 26 Jun 2017, Gyandeep Singh wrote:
>
> [... a bug report ...]
This bug report was reposted as
https://github.com/git-for-windows/git/issues/1219
In my opinion, it is too Windows-specific for the discussion to continue
Hi,
On Mon, 26 Jun 2017, Gyandeep Singh wrote:
> 3. hit "CTRL + c" (2 times) to kill the process.
> 4. If you look at taskmanager, then you will see a node.js process
> still running. or if you try to restart the server it will say port
> 300 already in use.
The way Ctrl+C is handled in Git for
Appreciate it. Thanks a lot.
Regards,
Gyandeep Singh
Website: http://gyandeeps.com
On Mon, Jun 26, 2017 at 10:15 PM, Stefan Beller wrote:
> 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
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
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
Which exact outputs of Git are invoked?
Does it change when giving slightly different options e.g. --no-pager?
Environment:
OS: Windows 7
Git: git version 2.13.1.windows.2
NodeJS: 8.1.2
Steps:
1. Create a js file with content
const http = require('http');
const fs = require('fs');
const port = 3000;
const app = http.createServer((req,res) => {
res.writeHead(200);
res.end("hi");
});
7 matches
Mail list logo