From: Vagn Johansen <vagn.johansen@gmail.com>
To: Chong Yidong <cyd@stupidchicken.com>
Cc: 8895@debbugs.gnu.org
Subject: bug#8895: 24.0.50; Entering Directory matching no longer works in grep-mode
Date: Tue, 20 Sep 2011 16:45:31 +0200 [thread overview]
Message-ID: <CAH682F04ierOJhK_q+a99Rtx5RtPHMN4Qx7-kpGy-Dvr3GH_1w@mail.gmail.com> (raw)
In-Reply-To: <87hb489wkj.fsf@stupidchicken.com>
On Mon, Sep 19, 2011 at 9:11 PM, Chong Yidong <cyd@stupidchicken.com> wrote:
> Vagn Johansen <vagn.johansen@gmail.com> writes:
>
>> Yes, sort of . I call (grep COMMAND-ARGS) with an external program
>> (written by me) which write the "Entering directory" message.
>
> In that case, you should use grep-mode-hook to set
> compilation-directory-matcher accordingly. For us to cater to
> non-standard grep programs is a path to madness.
You can easily support "non-standard grep programs" by using a
standard expected output format. You already supported my program
because the bug I reported is a *regression*. I have been grepping
happily for many years with my program (within emacs).
My "non-standard grep program" follows the "standard" set forth by GNU
Make which prints out for example
make: Entering directory `/u/vj/project1'
when run with make -C ~/project1
Maybe I have been lucky that grep-mode was built upon compilation-mode
so that I got
this additional feature, but I do not see it as "path to madness" if
you select *one* format
for parsing entering/leaving a directory information in grep output.
But yes, I should be able to use grep-mode-hook.
Regards
Vagn
prev parent reply other threads:[~2011-09-20 14:45 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-18 21:24 bug#8895: 24.0.50; Entering Directory matching no longer works in grep-mode Vagn Johansen
2011-09-18 18:28 ` Chong Yidong
2011-09-18 19:59 ` Vagn Johansen
2011-09-19 19:11 ` Chong Yidong
2011-09-20 14:45 ` Vagn Johansen [this message]
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAH682F04ierOJhK_q+a99Rtx5RtPHMN4Qx7-kpGy-Dvr3GH_1w@mail.gmail.com \
--to=vagn.johansen@gmail.com \
--cc=8895@debbugs.gnu.org \
--cc=cyd@stupidchicken.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 public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).