From: <agkozak@gmail.com>
To: <zsh-workers@zsh.org>
Cc: "'Jun T'" <takimoto-j@kba.biglobe.ne.jp>
Subject: Re: Possible ZSH bug involving piping ls to less (MSYS2 & Cygwin)
Date: Tue, 26 Jan 2021 18:44:54 -0800 [thread overview]
Message-ID: <00ca01d6f456$656e4aa0$304adfe0$@gmail.com> (raw)
I'm pretty sure it's been happening intermittently for quite a while, but I
couldn't say for sure when it started. Sorry.
I found a discussion on GitHub of a similar problem where git was being
piped to tig:
https://github.com/jonas/tig/issues/951
They seem to think they know exactly when the problem started, but I can't
confirm that.
The workaround of using a subshell seems to help, i.e.
ls --color | (less -R)
Alex
-----Original Message-----
From: Jun T <takimoto-j@kba.biglobe.ne.jp>
Sent: Monday, January 25, 2021 5:50 PM
To: zsh-workers@zsh.org
Cc: Alexandros Kozak <agkozak@gmail.com>
Subject: Re: Possible ZSH bug involving piping ls to less (MSYS2 & Cygwin)
> 2021/01/19 4:08, agkozak@gmail.com wrote:
>
> Using zsh v5.8 on both MSYS2 and Cygwin and a plain vanilla shell (no
> dotfiles):
>
> If I run
>
> ls --color | less -R
>
> frequently I get
>
> zsh: done ls --color |
> zsh: suspended (tty output) less -R
>
> On rare occasions I can get this to happen with a simple
>
> ls | less
>
> but using the --color option seems to make it happen considerably more
> often. It happens quite frequently on MSYS2; it is harder to reproduce
> on Cygwin, but it does happen.
Yes, it happens quite frequently on MSYS2.
Has this been happening for a long time, or started to happen rather
recently?
(my experience on MSYS2 is quite limited)
next reply other threads:[~2021-01-27 2:45 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-27 2:44 agkozak [this message]
2021-01-27 10:14 ` Jun T
2021-01-28 10:42 ` Jun T
-- strict thread matches above, loose matches on Subject: below --
2021-01-18 19:08 agkozak
2021-01-26 1:49 ` Jun T
2022-09-13 8:49 ` Jun T
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='00ca01d6f456$656e4aa0$304adfe0$@gmail.com' \
--to=agkozak@gmail.com \
--cc=takimoto-j@kba.biglobe.ne.jp \
--cc=zsh-workers@zsh.org \
/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.
Code repositories for project(s) associated with this public inbox
https://git.vuxu.org/mirror/zsh/
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 NNTP newsgroup(s).