GNU bug report logs - #35051
Fwd: grep

Previous Next

Package: grep;

Reported by: Todd Hoatson <todd.hoatson <at> gmail.com>

Date: Sat, 30 Mar 2019 17:57:02 UTC

Severity: normal

Tags: moreinfo

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

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

View this report as an mbox folder, status mbox, maintainer mbox


Report forwarded to bug-grep <at> gnu.org:
bug#35051; Package grep. (Sat, 30 Mar 2019 17:57:02 GMT) Full text and rfc822 format available.

Acknowledgement sent to Todd Hoatson <todd.hoatson <at> gmail.com>:
New bug report received and forwarded. Copy sent to bug-grep <at> gnu.org. (Sat, 30 Mar 2019 17:57:02 GMT) Full text and rfc822 format available.

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

From: Todd Hoatson <todd.hoatson <at> gmail.com>
To: bug-grep <at> gnu.org
Subject: Fwd: grep
Date: Sat, 30 Mar 2019 11:46:50 -0500
[Message part 1 (text/plain, inline)]
Hi, I have run into problems when trying to use GNU grep for (what I
thought would be) a fairly straight-forward text-search task.

The problem has been thoroughly described on stack-overflow:
https://stackoverflow.com/questions/55407034/how-to-find-c-sharp-class-names-with-regex
<https://stackoverflow.com/questions/55407034/how-to-find-c-sharp-class-names-with-regex?noredirect=1#comment97578340_55407034>

Full Disclosure:  On stack-overflow, pretty much the only responses I got
were criticisms of what I was trying to do or my choice of grep to do it.
Then, 5 people banded together to label my post as "On Hold", with the
explanation:  "Please edit the question to limit it to a specific problem
with enough detail to identify an adequate answer. Avoid asking multiple
distinct questions at once."

In my view, I did my best to ask a detailed, limited question about how to
get grep to work or what I was doing wrong in my use of grep.  They offered
suggestions that failed to work and then became offended with me for
pointing this out to them.

Please take a look at my question and let me know if you can help me.  If
it turns out that you feel my question was indeed inappropriate, I would
appreciate any effort to explain it to me.

thanks,
Todd Hoatson


-- 
Todd Hoatson
Mobile: 763-291-3312
Email:   todd.hoatson <at> gmail.com
www.linkedin.com/in/toddhoatson
[Message part 2 (text/html, inline)]

Information forwarded to bug-grep <at> gnu.org:
bug#35051; Package grep. (Thu, 02 Jan 2020 09:26:02 GMT) Full text and rfc822 format available.

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

From: Paul Eggert <eggert <at> cs.ucla.edu>
To: Todd Hoatson <todd.hoatson <at> gmail.com>
Cc: 35051 <at> debbugs.gnu.org
Subject: Re: Fwd: grep
Date: Thu, 2 Jan 2020 01:25:29 -0800
Re <https://bugs.gnu.org/35051>:
Unfortunately the stackoverflow URLs you sent no longer work. If you have a
specific, self-contained bug report about grep, please follow up here.




Added tag(s) moreinfo. Request was from Paul Eggert <eggert <at> cs.ucla.edu> to control <at> debbugs.gnu.org. (Thu, 02 Jan 2020 09:26:02 GMT) Full text and rfc822 format available.

This bug report was last modified 4 years and 116 days ago.

Previous Next


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