all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Juri Linkov <juri@jurta.org>
To: Ted Zlatanov <tzz@lifelogs.com>
Cc: emacs-devel@gnu.org
Subject: Re: harmonize grep, occur and compile
Date: Sun, 25 Nov 2007 17:31:51 +0200	[thread overview]
Message-ID: <871waecpv4.fsf@jurta.org> (raw)
In-Reply-To: <86r6igby2h.fsf@lifelogs.com> (Ted Zlatanov's message of "Fri, 23 Nov 2007 12:45:26 -0600")

> MK> grep, occur and compile all enables the user to jump to postions in
> MK> files or buffers. Occur has the ability to stay in the *occur*-buffer
> MK> while showing the occurence point is at using
> MK> occur-mode-display-occurrence. The line is centered in the buffer that
> MK> occured was started from.
>
> MK> It would be nice if this line could be highlighted as compile use to do.
>
> MK> This way the user can do a broad occur and then walk around in the
> MK> resulting buffer and cherrypick lines that he is interested in. It
> MK> will the be easy to find this line in its original context.
>
> I generally "walk around" the list of matches with next-error and
> previous-error which work in all three types of buffers you are
> interested in.  I've even mapped those to / and * on my keypad, I use
> them so often.  You can use those commands in the original buffer,
> without jumping to the list of matches.
>
> I hope this helps.  It doesn't answer your highlighting question, but I
> find I don't need highlighting when I just jump to the right location
> every time.

There is a special face `next-error'.  So why not to use it to highlight
occur matches as they are already highlighted for compile/grep?

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

      reply	other threads:[~2007-11-25 15:31 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-11-23 11:49 harmonize grep, occur and compile Matzi Kratzi
2007-11-23 18:45 ` Ted Zlatanov
2007-11-25 15:31   ` Juri Linkov [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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=871waecpv4.fsf@jurta.org \
    --to=juri@jurta.org \
    --cc=emacs-devel@gnu.org \
    --cc=tzz@lifelogs.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 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.