GNU bug report logs - #21498
macos: `ps -ef | grep "test"` in eshell beeps

Previous Next

To add a comment to this bug, you must first unarchive it, by sending
a message to control AT debbugs.gnu.org, with unarchive 21498 in the body.
You can then email your comments to 21498 AT debbugs.gnu.org in the normal way.

Toggle the display of automated, internal messages from the tracker.

Message #5 received at submit <at> debbugs.gnu.org (full text, mbox):

From: Sum Proxy <sum.proxy <at> gmail.com>
To: bug-gnu-emacs <at> gnu.org
Subject: ps -ef | grep "test" in eshell gives a beep
Date: Wed, 16 Sep 2015 16:42:17 +0300

It also hangs with some of the output.
Emacs version:
GNU Emacs 24.4.1 (x86_64-apple-darwin13.4.0, NS apple-appkit-1265.21) of 2014-10-21 on builder10-9.porkrind.org
eshell version 2.4.2

Please let me know why this happens and how to fix it. 
Thanks.

Message #8 received at 21498 <at> debbugs.gnu.org (full text, mbox):

From: Marcin Borkowski <mbork <at> mbork.pl>
To: 21498 <at> debbugs.gnu.org
Cc: Sum Proxy <sum.proxy <at> gmail.com>
Subject: Re: bug#21498: ps -ef | grep "test" in eshell gives a beep
Date: Fri, 08 Jan 2016 09:27:02 +0100

Hello,

I would be thankful if you could check whether the problem persists in
latest Emacs.  If yes, please lay out the steps to reproduce your
problem.  I tried

  ps -ef | grep "test"

in Eshell and it seemed to work fine on the development version of
Emacs; it is possible that the problem disappeared and the bug can be
closed.

Best regards,
Marcin Borkowski

On 2015-09-16, at 17:42, Sum Proxy <sum.proxy <at> gmail.com> wrote:

> It also hangs with some of the output.
> Emacs version:
> GNU Emacs 24.4.1 (x86_64-apple-darwin13.4.0, NS apple-appkit-1265.21) of 2014-10-21 on builder10-9.porkrind.org
> eshell version 2.4.2
>
> Please let me know why this happens and how to fix it. 
> Thanks.

Message #11 received at 21498 <at> debbugs.gnu.org (full text, mbox):

From: Marcin Borkowski <mbork <at> mbork.pl>
To: Sum Proxy <sum.proxy <at> gmail.com>,21498 <at> debbugs.gnu.org
Subject: Re: bug#21498: ps -ef | grep "test" in eshell gives a beep
Date: Fri, 08 Jan 2016 10:37:11 +0100

On 2016-01-08, at 10:15, Sum Proxy <sum.proxy <at> gmail.com> wrote:

> I just downloaded and built the latest version from git://git.savannah.gnu.org/emacs.git which is
> GNU Emacs 25.1.50.1 (x86_64-apple-darwin15.2.0, NS appkit-1404.34 Version 10.11.2 (Build 15C50))
>  of 2016-01-08
> And found that the behavior still persists. What kind of input (if any) do you need from me to keep working on it?

Thank you a lot for your prompt response!  Since I am on GNU/Linux, and
after your reply I am pretty confident that this is Mac OS-specific,
I will have to leave it to others for further investigation.  Also, you
might want to evaluate this form: (info "(emacs)Checklist") and make
sure to follow the instructions there (in particular, check whether the
problem appears with emacs -Q).

> Thanks

Thank you for cooperation, and I hope this issue will be resolved!

-- 
Marcin Borkowski               This email was proudly sent
http://mbork.pl                from my Emacs.

Message #14 received at 21498 <at> debbugs.gnu.org (full text, mbox):

From: Marcin Borkowski <mbork <at> mbork.pl>
To: 21498 <at> debbugs.gnu.org
Subject: Fwd: Re: bug#21498: ps -ef | grep "test" in eshell gives a beep
Date: Mon, 11 Jan 2016 18:41:39 +0100

Forwarding a message from the submitter, confirming that the bug still
occurs in latest Emacs release, without a config file.

On 2016-01-08, at 11:37, Sum Proxy <sum.proxy <at> gmail.com> wrote:

> I checked for the issue in the latest version with -Q and confirm that it’s there.
> Thanks
>
>> 8 янв. 2016 г., в 12:37, Marcin Borkowski <mbork <at> mbork.pl> написал(а):
>> 
>> 
>> On 2016-01-08, at 10:15, Sum Proxy <sum.proxy <at> gmail.com> wrote:
>> 
>>> I just downloaded and built the latest version from git://git.savannah.gnu.org/emacs.git which is
>>> GNU Emacs 25.1.50.1 (x86_64-apple-darwin15.2.0, NS appkit-1404.34 Version 10.11.2 (Build 15C50))
>>> of 2016-01-08
>>> And found that the behavior still persists. What kind of input (if any) do you need from me to keep working on it?

-- 
Marcin Borkowski
http://octd.wmi.amu.edu.pl/en/Marcin_Borkowski
Faculty of Mathematics and Computer Science
Adam Mickiewicz University

Message #17 received at 21498 <at> debbugs.gnu.org (full text, mbox):

From: Stefan Kangas <stefan <at> marxist.se>
To: Marcin Borkowski <mbork <at> mbork.pl>
Cc: 21498 <at> debbugs.gnu.org, Sum Proxy <sum.proxy <at> gmail.com>
Subject: Re: bug#21498: Fwd: Re: bug#21498: ps -ef | grep "test" in eshell
 gives a beep
Date: Wed, 06 Nov 2019 02:25:07 +0100

found 21498 27.0.50
thanks

Marcin Borkowski <mbork <at> mbork.pl> writes:

> Forwarding a message from the submitter, confirming that the bug still
> occurs in latest Emacs release, without a config file.

I can't reproduce this on GNU/Linux, but I can reproduce it on macOS
using Emacs 27.

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.

Best regards,
Stefan Kangas

Message #26 received at 21498 <at> debbugs.gnu.org (full text, mbox):

From: Lars Ingebrigtsen <larsi <at> gnus.org>
To: Stefan Kangas <stefan <at> marxist.se>
Cc: 21498 <at> debbugs.gnu.org, Marcin Borkowski <mbork <at> mbork.pl>,
 Sum Proxy <sum.proxy <at> gmail.com>
Subject: Re: bug#21498: macos: `ps -ef | grep "test"` in eshell beeps
Date: Thu, 02 Dec 2021 10:28:20 +0100

Stefan Kangas <stefan <at> 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

Message #29 received at 21498 <at> debbugs.gnu.org (full text, mbox):

From: Stefan Kangas <stefankangas <at> gmail.com>
To: Lars Ingebrigtsen <larsi <at> gnus.org>
Cc: Jim Porter <jporterbugs <at> gmail.com>, 21498 <at> debbugs.gnu.org,
 Marcin Borkowski <mbork <at> mbork.pl>, Sum Proxy <sum.proxy <at> gmail.com>
Subject: Re: bug#21498: macos: `ps -ef | grep "test"` in eshell beeps
Date: Thu, 25 Jul 2024 13:36:47 +0000

found 21498 30.0.60
found 21498 31.0.50
thanks

Lars Ingebrigtsen <larsi <at> gnus.org> writes:

> Stefan Kangas <stefankangas <at> gmail.com> 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.

I've tested this on Emacs 30 on mac OS 14.5, and the bug is still
present.  I now get this backtrace, however:

Debugger entered--Lisp error: (void-function eshell-set-exit-info)
  eshell-set-exit-info(0 t)
  #f(compiled-function () #<bytecode 0x1cf599f366a88a85>)()
  eshell-sentinel(#<process grep> "finished\n")

Copying in Jim Porter, in case he has any ideas.

Message #36 received at 21498 <at> debbugs.gnu.org (full text, mbox):

From: Jim Porter <jporterbugs <at> gmail.com>
To: Stefan Kangas <stefankangas <at> gmail.com>, Lars Ingebrigtsen <larsi <at> gnus.org>
Cc: 21498 <at> debbugs.gnu.org, Marcin Borkowski <mbork <at> mbork.pl>,
 Sum Proxy <sum.proxy <at> gmail.com>
Subject: Re: bug#21498: macos: `ps -ef | grep "test"` in eshell beeps
Date: Thu, 25 Jul 2024 08:53:44 -0700

On 7/25/2024 6:36 AM, Stefan Kangas wrote:
> I've tested this on Emacs 30 on mac OS 14.5, and the bug is still
> present.  I now get this backtrace, however:
> 
> Debugger entered--Lisp error: (void-function eshell-set-exit-info)
>    eshell-set-exit-info(0 t)
>    #f(compiled-function () #<bytecode 0x1cf599f366a88a85>)()
>    eshell-sentinel(#<process grep> "finished\n")
> 
> Copying in Jim Porter, in case he has any ideas.

Is this in Emacs 30? 'eshell-set-exit-info' doesn't exist anywhere in 
Emacs 30 (it's new in 31). Is there something amiss in your build?

If this is with Emacs 31, then I don't see how this error could be 
occurring either. 'eshell-set-exit-info' is just an ordinary function in 
another file, which is always 'require'd when Eshell starts. (If it 
really weren't defined properly, then I'd expect most of the Eshell test 
suite to fail - on all platforms - and it passes for me.)

If you resolve the 'eshell-set-exit-info' issue and the original bug is 
still there, could you try running the Eshell command "eshell-debug 
process" and then run the buggy Eshell command again? This should print 
a bunch of logs about process handling to the "*eshell last cmd*" 
buffer. If I can take a look at that output, I might see something of 
interest.

Message #39 received at 21498 <at> debbugs.gnu.org (full text, mbox):

From: Stefan Kangas <stefankangas <at> gmail.com>
To: Jim Porter <jporterbugs <at> gmail.com>, Lars Ingebrigtsen <larsi <at> gnus.org>
Cc: 21498 <at> debbugs.gnu.org, Marcin Borkowski <mbork <at> mbork.pl>,
 Sum Proxy <sum.proxy <at> gmail.com>
Subject: Re: bug#21498: macos: `ps -ef | grep "test"` in eshell beeps
Date: Fri, 26 Jul 2024 18:19:48 -0400

close 21498 30.1
thanks

Jim Porter <jporterbugs <at> gmail.com> writes:

> On 7/25/2024 6:36 AM, Stefan Kangas wrote:
>> I've tested this on Emacs 30 on mac OS 14.5, and the bug is still
>> present.  I now get this backtrace, however:
>>
>> Debugger entered--Lisp error: (void-function eshell-set-exit-info)
>>    eshell-set-exit-info(0 t)
>>    #f(compiled-function () #<bytecode 0x1cf599f366a88a85>)()
>>    eshell-sentinel(#<process grep> "finished\n")
>>
>> Copying in Jim Porter, in case he has any ideas.
>
> Is this in Emacs 30? 'eshell-set-exit-info' doesn't exist anywhere in
> Emacs 30 (it's new in 31). Is there something amiss in your build?

Hmm, it seems like there was indeed something amiss in my build.

I've retested the recipe on Emacs 30 and Emacs 31, and it works in both
versions.  So I believe this bug has been fixed, and I'm closing it now.

Thanks!

Message #44 received at 21498 <at> debbugs.gnu.org (full text, mbox):

From: Jim Porter <jporterbugs <at> gmail.com>
To: Stefan Kangas <stefankangas <at> gmail.com>, Lars Ingebrigtsen <larsi <at> gnus.org>
Cc: 21498 <at> debbugs.gnu.org, Marcin Borkowski <mbork <at> mbork.pl>,
 Sum Proxy <sum.proxy <at> gmail.com>
Subject: Re: bug#21498: macos: `ps -ef | grep "test"` in eshell beeps
Date: Fri, 26 Jul 2024 15:28:48 -0700

On 7/26/2024 3:19 PM, Stefan Kangas wrote:
> Hmm, it seems like there was indeed something amiss in my build.
> 
> I've retested the recipe on Emacs 30 and Emacs 31, and it works in both
> versions.  So I believe this bug has been fixed, and I'm closing it now.

Including the beeping? If so, excellent!

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.