From: Takashi Yano <takashi.yano@nifty.ne.jp>
To: cygwin@cygwin.com
Cc: Orgad Shaneh <orgads@gmail.com>
Subject: Re: Console output hangs in the middle of a line
Date: Sun, 20 Feb 2022 23:34:00 +0900 [thread overview]
Message-ID: <20220220233400.4ddfa98ec32f831fad8b78c2@nifty.ne.jp> (raw)
In-Reply-To: <20220220232207.b7fc5f99b324b3e3be95c686@nifty.ne.jp>
On Sun, 20 Feb 2022 23:22:07 +0900
Takashi Yano wrote:
> If the script
>
> #!/bin/sh
> mkdir -p chunked
> cd chunked
> /cygdrive/c/Program\ Files/Git/mingw64/bin/git init
> mkdir -p abc/def/ghi/jkl def
> cd abc/def/ghi/jkl
> touch foo
> /cygdrive/c/Program\ Files/Git/mingw64/bin/git add foo
> seq 1 10000 | xargs touch
> cd ../../../../def
> seq 1 100000 | xargs touch
> cd ..
> time /cygdrive/c/Program\ Files/Git/mingw64/bin/git clean -dfx
>
> is used, the hang here:
> Removing abc/def/ghi/jkl/9878
> Removing abc/def/ghi/jkl<hangs 15sec>
> is more than 10sec.
>
> It seems that removing def/ takes the time,
> and the output stops before displying
> Removing abc/def/ghi/jkl/9879
> [...]
> Removing abc/def/ghi/jkl/9999
>
> I guess the output is just buffered in somewhere
> which is not flushed.
The same happens in command prompt which started from 'Git CMD'
icon. In this case, not only cygwin but also msys2 is not used.
Therefore, this is the problem of git executable itself in
Git-for-windows.
--
Takashi Yano <takashi.yano@nifty.ne.jp>
next prev parent reply other threads:[~2022-02-20 14:34 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-16 9:49 Orgad Shaneh
2022-02-16 9:59 ` Takashi Yano
2022-02-16 10:01 ` Takashi Yano
2022-02-20 11:43 ` Orgad Shaneh
2022-02-20 13:37 ` Takashi Yano
2022-02-20 13:43 ` Takashi Yano
2022-02-20 13:48 ` Takashi Yano
2022-02-20 13:51 ` Orgad Shaneh
2022-02-20 14:22 ` Takashi Yano
2022-02-20 14:34 ` Takashi Yano [this message]
2022-02-20 14:42 ` 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=20220220233400.4ddfa98ec32f831fad8b78c2@nifty.ne.jp \
--to=takashi.yano@nifty.ne.jp \
--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).