From: Max Mikhanosha <max@openchat.com>
To: Michael Brand <michael.ch.brand@gmail.com>
Cc: Org Mode <emacs-orgmode@gnu.org>
Subject: Re: reveal the matches in grep-find or the diffs in ediff and hide the rest
Date: Sat, 21 Jan 2012 10:54:25 -0500 [thread overview]
Message-ID: <87lip1aw5q.wl%max@openchat.com> (raw)
In-Reply-To: <CALn3zojY3ksJTxsKCp9XkBxPAdOJM904uHGdC+vVQn5WpyYxvg@mail.gmail.com>
At Sat, 21 Jan 2012 16:24:12 +0100,
Michael Brand wrote:
>
> Hi all
>
> On Sat, Jan 21, 2012 at 13:59, Max Mikhanosha <max@openchat.com> wrote:
> > Then use M-x ediff-buffers, and you can navigate changes easily by
> > pressing n or p in ediff control panel. I just tried it out and it
> > worked pretty good. Only thing that could have worked better, is to
> > hook-up ediff with org-reveal or reveal-mode, so that it automatically
> > folds all unchanged stuff, and only reveals text in the highlighted
> > regions.
>
> hook-up org-reveal when using grep-find or pressing n or p in ediff
> control panel sounds like what I have been looking for for a long
> time.
>
> Is this documented? I couldn't find it in the Org manual, Emacs
> manual, Worg or EmacsWiki. Just enabling reveal-mode before
> ediff-buffers alone doesn't seem to do the trick. At least for
No enabling reveal-mode did not worked for me either, that's why i
wrote "the only thing that could have worked better".
reveal-mode actually works, if you C-x o from the Ediff control panel
buffer to one of the source buffers and then back again. So it
probably has a check inside of it, that only reveals if buffer is the
active one.
Should be possible to do some magics with defadvice to make it happen
regardless if buffer is current or not, if buffer is part of Ediff
session or some other special condition.
prev parent reply other threads:[~2012-01-21 15:54 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-21 15:24 reveal the matches in grep-find or the diffs in ediff and hide the rest Michael Brand
2012-01-21 15:54 ` Max Mikhanosha [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.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87lip1aw5q.wl%max@openchat.com \
--to=max@openchat.com \
--cc=emacs-orgmode@gnu.org \
--cc=michael.ch.brand@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/org-mode.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).