From: Lars Ingebrigtsen <larsi@gnus.org>
To: Stefan Kangas <stefan@marxist.se>
Cc: 21498@debbugs.gnu.org, Marcin Borkowski <mbork@mbork.pl>,
Sum Proxy <sum.proxy@gmail.com>
Subject: bug#21498: macos: `ps -ef | grep "test"` in eshell beeps
Date: Thu, 02 Dec 2021 10:28:20 +0100 [thread overview]
Message-ID: <87czmf73uz.fsf_-_@gnus.org> (raw)
In-Reply-To: <87zhh94wzw.fsf@marxist.se> (Stefan Kangas's message of "Wed, 06 Nov 2019 02:25:07 +0100")
Stefan Kangas <stefan@marxist.se> writes:
> The recipe can in my case be simplified to:
>
> 0. emacs -Q
> 1. M-x eshell
> 2. echo foo | grep foo
>
> Results: I see the line "foo" printed, then it stalls until I kill it
> with C-c.
>
> I never see the beep the OP talks about, but I see the same stalling
> as above when I say 'ps -ef | grep "test"'.
>
> Perhaps this is caused by some difference between BSD grep and GNU
> grep.
I re-tested this in Emacs 29 with the current Macos, and the bug is
still present there.
--
(domestic pets only, the antidote for overdose, milk.)
bloggy blog: http://lars.ingebrigtsen.no
next prev parent reply other threads:[~2021-12-02 9:28 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-16 13:42 bug#21498: ps -ef | grep "test" in eshell gives a beep Sum Proxy
2016-01-08 8:27 ` Marcin Borkowski
[not found] ` <228BD249-9B51-4CF5-BB6E-3274598B647C@gmail.com>
[not found] ` <8E672BF7-96D1-4ECE-A4E9-B1CC39E102AA@gmail.com>
2016-01-08 9:37 ` Marcin Borkowski
[not found] ` <72EA8F77-51D6-480D-ACD4-CF46542539A8@gmail.com>
2016-01-11 17:41 ` bug#21498: Fwd: " Marcin Borkowski
2019-11-06 1:25 ` Stefan Kangas
2021-12-02 9:28 ` Lars Ingebrigtsen [this message]
2024-07-25 13:36 ` bug#21498: macos: `ps -ef | grep "test"` in eshell beeps Stefan Kangas
2024-07-25 15:53 ` Jim Porter
2024-07-26 22:19 ` Stefan Kangas
2024-07-26 22:28 ` Jim Porter
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=87czmf73uz.fsf_-_@gnus.org \
--to=larsi@gnus.org \
--cc=21498@debbugs.gnu.org \
--cc=mbork@mbork.pl \
--cc=stefan@marxist.se \
--cc=sum.proxy@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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.