From: Michael Heerdegen <michael_heerdegen@web.de>
To: jonetsu <jonetsu@teksavvy.com>
Cc: help-gnu-emacs@gnu.org
Subject: Re: Four questions about ediff
Date: Tue, 10 Dec 2019 03:26:52 +0100 [thread overview]
Message-ID: <87eexc530z.fsf@web.de> (raw)
In-Reply-To: <20191209075857.72ed482b@mistral> (jonetsu@teksavvy.com's message of "Mon, 9 Dec 2019 07:58:57 -0500")
jonetsu <jonetsu@teksavvy.com> writes:
> I found ztree which is a much better way to go about making directory
> diffs that the default ediff.
There is also dircmp. It uses rsync for directory comparison. I guess
that makes it quite fast, but that means comparison is not under control
of Emacs.
I think it still offers most of what you want. Filters are not
supported, but I guess that could be added.
I also think that it would be nice to improve Ediff in this regard.
Personally I don't like to hack Ediff, though, it was always not nice
when I tried that.
Michael.
prev parent reply other threads:[~2019-12-10 2:26 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-30 22:59 Four questions about ediff jonetsu
2019-11-03 13:47 ` jonetsu
2019-11-03 15:26 ` Óscar Fuentes
2019-11-04 23:06 ` jonetsu
2019-12-09 12:58 ` jonetsu
2019-12-10 2:26 ` Michael Heerdegen [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=87eexc530z.fsf@web.de \
--to=michael_heerdegen@web.de \
--cc=help-gnu-emacs@gnu.org \
--cc=jonetsu@teksavvy.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).