From: "Ehud Karni" <ehud@unix.mvs.co.il>
Subject: Re: Changes to emacs/lisp/progmodes/compile.el
Date: Sat, 13 Aug 2005 19:40:23 +0300 [thread overview]
Message-ID: <200508131640.j7DGeNsa022044@beta.mvs.co.il> (raw)
In-Reply-To: <871x4z3woc.fsf@pacem.orebokech.com> (message from Romain Francoise on Fri, 12 Aug 2005 19:13:55 +0200)
On Fri, 12 Aug 2005 19:13:55 +0200, Romain Francoise wrote:
>
> > [patch for compile.el]
>
> This line gets fontified as a match in grep mode, it doesn't look good.
>
> (The line looks like "Grep started at Fri Aug 12 19:05:29", the part up
> to the first colon gets the compilation-info face, the '05' part gets
> the compilation-line-number face, and the end of the line gets default.)
Grep has its own fortification (different from `compilation-mode').
The Patch bellow fix this (it fontifies the grep started/finished with
underline, instead of the current behavior where it is not fontified).
Ehud.
2005-08-06 Ehud Karni <ehud@unix.mvs.co.il>
* progmodes/grep.el (grep-mode-font-lock-keywords): change the
regular expression for highlighting grep started/finished.
diff -c lisp/progmodes/grep.el.~1.45.~ lisp/progmodes/grep.el
*** lisp/progmodes/grep.el.~1.45.~ Fri Aug 12 18:30:42 2005
--- lisp/progmodes/grep.el Sat Aug 13 17:04:58 2005
***************
*** 287,296 ****
(": \\(.+\\): \\(?:Permission denied\\|No such \\(?:file or directory\\|device or address\\)\\)$"
1 grep-error-face)
;; remove match from grep-regexp-alist before fontifying
! ("^Grep finished \\(?:(\\(matches found\\))\\|with \\(no matches found\\)\\).*"
(0 '(face nil message nil help-echo nil mouse-face nil) t)
! (1 compilation-info-face nil t)
! (2 compilation-warning-face nil t))
("^Grep \\(exited abnormally\\) with code \\([0-9]+\\).*"
(0 '(face nil message nil help-echo nil mouse-face nil) t)
(1 grep-error-face)
--- 287,297 ----
(": \\(.+\\): \\(?:Permission denied\\|No such \\(?:file or directory\\|device or address\\)\\)$"
1 grep-error-face)
;; remove match from grep-regexp-alist before fontifying
! ("^\\(Grep \\(start\\|finish\\)ed\\) \\(?:(\\(matches found\\))\\|with \\(no matches found\\)\\)?[ ]?at .*"
(0 '(face nil message nil help-echo nil mouse-face nil) t)
! (1 '(face underline))
! (3 compilation-info-face nil t)
! (4 compilation-warning-face nil t))
("^Grep \\(exited abnormally\\) with code \\([0-9]+\\).*"
(0 '(face nil message nil help-echo nil mouse-face nil) t)
(1 grep-error-face)
--
Ehud Karni Tel: +972-3-7966-561 /"\
Mivtach - Simon Fax: +972-3-7966-667 \ / ASCII Ribbon Campaign
Insurance agencies (USA) voice mail and X Against HTML Mail
http://www.mvs.co.il FAX: 1-815-5509341 / \
GnuPG: 98EA398D <http://www.keyserver.net/> Better Safe Than Sorry
parent reply other threads:[~2005-08-13 16:40 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <871x4z3woc.fsf@pacem.orebokech.com>]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200508131640.j7DGeNsa022044@beta.mvs.co.il \
--to=ehud@unix.mvs.co.il \
/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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.