unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Juri Linkov <juri@jurta.org>
Cc: emacs-devel@gnu.org
Subject: Re: Changes to emacs/lisp/progmodes/grep.el
Date: Fri, 02 Jul 2004 11:48:48 +0300	[thread overview]
Message-ID: <874qoq3i95.fsf@mail.jurta.org> (raw)
In-Reply-To: <20040702235848.255ecbbe@pfdabpc.inhouse.start.de> (Daniel Pfeiffer's message of "Fri, 2 Jul 2004 23:58:48 +0200")

dapfy@t-online.de (Daniel Pfeiffer) writes:
> Juri Linkov <juri@jurta.org> skribis:
>> Currently I set `compilation-error-screen-columns' to nil in
>> `grep-regexp-alist', but perhaps I should use `grep-error-screen-columns'?
>
> Ah ha!  Grep inherits from compilation, so all the like-named variables get
> passed through.  As for your setting this on every match, I don't see the
> point, not even setting this once.  This is an option, which means that people
> could set it to match the understanding of whatever external prog they use.

If grep output contains at least one escape sequence used to surround
the matching string, `compilation-error-screen-columns' should be set
to nil, because the rule in `grep-regexp-alist' calculates the column
positions of matches by subtracting the position of the first character
after the file name and line number from the position of the first escape
sequence, so these calculations are based on character positions, not
on screen columns.  This means that to find correct columns in the
source buffers compilation-error-screen-columns should be nil to
interpret calculated column numbers as characters.

>> +     (4 (list 'face nil 'invisible t 'intangible t))
>> +     (5 (list 'face compilation-column-face))
>> +     (6 (list 'face nil 'invisible t 'intangible t))
>
> I've simplified these a little and made the face customizable, defaulting to
> isearch's.

isearch-lazy-highlight-face makes more sense since it is already used
to highlight multiple matches in isearch mode which will be similar to
matches in the grep buffer.

>> diff -u -r1.322 compile.el
>> --- lisp/progmodes/compile.el	18 Jun 2004 23:00:46 -0000	1.322
>> +++ lisp/progmodes/compile.el	30 Jun 2004 03:35:13 -0000
>
>> +	(overlay-put compilation-highlight-overlay 'face next-error-face))
>
> This variable is undefined.

Sorry, that face is from another opera :-)

I posted only the relevant part of a whole patch which uses a new face
`next-error-face' and a new option `next-error-highlight' whose another
part I already posted earlier.

-- 
Juri Linkov
http://www.jurta.org/emacs/

  parent reply	other threads:[~2004-07-02  8:48 UTC|newest]

Thread overview: 43+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <E1BdGt8-0003Tg-Qb@lists.gnu.org>
2004-06-24 23:16 ` Changes to emacs/lisp/progmodes/grep.el Juri Linkov
2004-06-25 20:03   ` Daniel Pfeiffer
2004-06-26  0:03     ` Juri Linkov
2004-06-27 10:43       ` Daniel Pfeiffer
2004-06-26  6:03     ` Richard Stallman
2004-06-27 10:33       ` Daniel Pfeiffer
2004-06-27 11:58         ` Adrian Aichner
2004-06-28  2:23         ` Richard Stallman
2004-06-28  2:37           ` Miles Bader
2004-06-28  4:44           ` David Kastrup
2004-06-28  8:40             ` Daniel Pfeiffer
2004-06-28 18:00               ` Eli Zaretskii
2004-06-28 21:22                 ` Daniel Pfeiffer
2004-06-29  5:10                   ` Eli Zaretskii
2004-06-29 20:08                     ` Daniel Pfeiffer
2004-06-29 21:19                       ` Eli Zaretskii
2004-06-30  5:16                         ` Juri Linkov
2004-07-01 22:20                         ` Daniel Pfeiffer
2004-06-30  5:08                       ` Juri Linkov
2004-07-02 21:58                         ` Daniel Pfeiffer
2004-07-01 23:31                           ` Stefan
2004-07-01 23:38                             ` David Kastrup
2004-07-01 23:46                               ` Stefan
2004-07-03 18:20                               ` Richard Stallman
2004-07-04 10:47                                 ` Mark handling (Was: Changes to emacs/lisp/progmodes/grep.el) Daniel Pfeiffer
2004-07-05 16:56                                   ` Richard Stallman
2004-07-05 19:57                                     ` Daniel Pfeiffer
2004-07-06 22:00                                       ` Richard Stallman
2004-07-07 19:47                                         ` Daniel Pfeiffer
2004-07-08 23:18                                           ` Richard Stallman
2004-07-10 19:54                                             ` Daniel Pfeiffer
2004-07-06 22:00                                       ` Richard Stallman
2004-07-07 20:58                                         ` Richard Stallman
2004-07-02  0:20                             ` Transient mark mode (was: " Paul Pogonyshev
2004-07-03  8:28                             ` Changes to emacs/lisp/progmodes/grep.el Daniel Pfeiffer
2004-07-02  9:07                               ` Juri Linkov
2004-07-03 11:35                                 ` Daniel Pfeiffer
2004-07-02  8:48                           ` Juri Linkov [this message]
2004-07-06 16:55                         ` Juri Linkov
2004-07-06 18:16                           ` Luc Teirlinck
2004-07-07 20:57                           ` Richard Stallman
2004-06-30 18:52                       ` Richard Stallman
2004-07-01  5:08                         ` Juri Linkov

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=874qoq3i95.fsf@mail.jurta.org \
    --to=juri@jurta.org \
    --cc=emacs-devel@gnu.org \
    /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).