From: Kevin Rodgers <ihs_4664@yahoo.com>
Subject: Re: display information in seperate buffer
Date: Thu, 30 Jun 2005 11:01:39 -0600 [thread overview]
Message-ID: <da183l$ab8$1@sea.gmane.org> (raw)
In-Reply-To: <slrndc7g0q.153.fab@node1.ddorf.de>
Fabian Braennstroem wrote:
> One question to multi-occur, right now it displays the
> matching lines for the given regexp for the chosen files, which is
> fine, but am I able to run some kine of ediff so multi-occur
> highlights the different listed lines, e.g.:
>
> 20 matches for "inlet" in buffer: *Occur*<2>
> 35: inletvelocity = 10 [m/s]
> 38: inlet = 2
> 9 matches for "inlet" in buffer: keps_small_301.out
> 36: inletvelocity = 20 [m/s]
> 40: inlet = 2
>
> So it would highlight the lines containing 'inletvelocity'!?
Run ediff-buffers normally, then use `#f' to focus it on the differences
you're interested in (those that match "inletvelocity").
--
Kevin Rodgers
prev parent reply other threads:[~2005-06-30 17:01 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-28 10:04 display information in seperate buffer Fabian Braennstroem
2005-06-29 7:18 ` Emilio Lopes
[not found] ` <mailman.1563.1120030207.2857.help-gnu-emacs@gnu.org>
2005-06-29 14:36 ` Fabian Braennstroem
2005-06-30 9:42 ` Fabian Braennstroem
2005-06-30 17:01 ` Kevin Rodgers [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='da183l$ab8$1@sea.gmane.org' \
--to=ihs_4664@yahoo.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.
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).