GNU bug report logs - #50270
Suggestion

Previous Next

To reply to this bug, email your comments to 50270 AT debbugs.gnu.org.

the display of automated, internal messages from the tracker.

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

From: Ojas Zanpure <ojaszanpure <at> gmail.com>
To: bug-grep <at> gnu.org
Subject: Re: Suggestion
Date: 2021年8月30日 17:44:49 +0530

[Message part 1 (text/plain, inline)]

Hi,
I am a new linux user and I have used grep a couple of times, and I had a
suggestion. Whenever I search for something using grep and it doesn't find
any results, it doesn't return anything. My suggestion is, instead of just
sending the user nothing, how about having a message like, "No results
matching those parameters". It might be confusing for a beginner whether he
executed the command correctly, if he doesn't see anything on screen.
Regards,
Ojas

[Message part 2 (text/html, inline)]

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

From: Paul Eggert <eggert <at> cs.ucla.edu>
To: Ojas Zanpure <ojaszanpure <at> gmail.com>
Cc: 50270 <at> debbugs.gnu.org
Subject: Re: bug#50270: Suggestion
Date: 2021年8月30日 11:35:51 -0700

On 8/30/21 5:14 AM, Ojas Zanpure wrote:
> It might be confusing for a beginner whether he
> executed the command correctly, if he doesn't see anything on screen.
True. However, grep's behavior here is standardized by POSIX and a lot 
of people rely on it, so I don't think we can change it.
If there's any consolation, 'grep' is intended for experts (and you are 
now an expert ;-).

Previous Next

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