unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Stefan Monnier <monnier@iro.umontreal.ca>
To: Jambunathan K <kjambunathan@gmail.com>
Cc: 13549@debbugs.gnu.org
Subject: bug#13549: 24.3.50; FR: Improve grep output (show function names, when possible)
Date: Fri, 25 Jan 2013 13:55:08 -0500	[thread overview]
Message-ID: <jwvwqv1rtkb.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <87a9rxux7q.fsf@gmail.com> (Jambunathan K.'s message of "Fri, 25 Jan 2013 20:27:29 +0530")

> I used the following local modification to compile.el to sneak in the
> function names.
> The modification is in `compilation-parse-errors' which seems to be a
> font-lock handler.

It's not quite a font-lock handler: it's a function that can get called
to parse errors when needed.  It is triggered by font-lock, indeed, but
also by next-error (e.g. tho often font-lock will have done the work of
parsing already).

> I call `which-function' within this context.  Is it justified?

I'm not sure what you mean by "justified", but I see no particular
reason why it shouldn't work.

Your suggestion is interesting, and clearly since it is specific to
`grep' it should be moved to grep.el (maybe as a font-lock-keyword?).

It would need to be an option, since for some uses it doesn't make much
sense (especially considering the performance impact it can have, and
the amount of screen real-estate it requires).


        Stefan






  parent reply	other threads:[~2013-01-25 18:55 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-01-25 14:57 bug#13549: 24.3.50; FR: Improve grep output (show function names, when possible) Jambunathan K
2013-01-25 15:05 ` Jambunathan K
2013-01-25 17:32 ` Glenn Morris
2013-01-25 18:55 ` Stefan Monnier [this message]
2013-02-03 13:49 ` Jambunathan K
2013-05-22 20:44 ` Juri Linkov
2013-05-22 22:03   ` Stefan Monnier
2013-05-24 20:55     ` Juri Linkov
2013-05-25 13:08       ` Jambunathan K

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=jwvwqv1rtkb.fsf-monnier+emacs@gnu.org \
    --to=monnier@iro.umontreal.ca \
    --cc=13549@debbugs.gnu.org \
    --cc=kjambunathan@gmail.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).