Bug 424201 - grep-mode confuses me
grep-mode confuses me
Product: Fedora
Classification: Fedora
Component: emacs (Show other bugs)
All Linux
low Severity low
: ---
: ---
Assigned To: Daniel Novotny
Fedora Extras Quality Assurance
Depends On:
  Show dependency treegraph
Reported: 2007-12-13 15:55 EST by David Woodhouse
Modified: 2009-01-09 00:30 EST (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2009-01-09 00:30:22 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description David Woodhouse 2007-12-13 15:55:49 EST
I use M-x grep to give me a shiny buffer where I can click on the hits and be
taken directly to the line in question.

If given a command such as:
 grep -nH -e lbs_prepare_and_send_command *.[ch] 
.. it works nicely.

When I modify the command to:
 grep -nH -e lbs_prepare_and_send_command *.[ch]  | grep -v WAIT
... it doesn't work. When I click on the files, I get a 'file open' dialog box
instead. Piping through 'cat' works, and through another 'grep' as long as it's
not 'grep -v'. Confused.
Comment 1 David Woodhouse 2007-12-13 16:42:14 EST
Ah, emacs sets $GREP_OPTIONS, $GREP_COLOR, $GREP_COLORS environment variables
which somehow cause the second grep to confuse it. This works:

 grep -nH -e lbs_prepare_and_send_command *.[ch] | GREP_OPTIONS= grep -v WAITFOR

Comment 2 Chip Coldwell 2007-12-14 11:43:55 EST

(setq grep-highlight-matches nil)

Comment 4 Bug Zapper 2008-11-26 03:59:37 EST
This message is a reminder that Fedora 8 is nearing its end of life.
Approximately 30 (thirty) days from now Fedora will stop maintaining
and issuing updates for Fedora 8.  It is Fedora's policy to close all
bug reports from releases that are no longer maintained.  At that time
this bug will be closed as WONTFIX if it remains open with a Fedora 
'version' of '8'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version prior to Fedora 8's end of life.

Bug Reporter: Thank you for reporting this issue and we are sorry that 
we may not be able to fix it before Fedora 8 is end of life.  If you 
would still like to see this bug fixed and are able to reproduce it 
against a later version of Fedora please change the 'version' of this 
bug to the applicable version.  If you are unable to change the version, 
please add a comment here and someone will do it for you.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events.  Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

The process we are following is described here: 
Comment 5 Bug Zapper 2009-01-09 00:30:22 EST
Fedora 8 changed to end-of-life (EOL) status on 2009-01-07. Fedora 8 is 
no longer maintained, which means that it will not receive any further 
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of 
Fedora please feel free to reopen this bug against that version.

Thank you for reporting this bug and we are sorry it could not be fixed.

Note You need to log in before you can comment on or make changes to this bug.