From: jonetsu <jonetsu@teksavvy.com>
To: help-gnu-emacs@gnu.org
Subject: Re: Four questions about ediff
Date: Mon, 4 Nov 2019 18:06:57 -0500 [thread overview]
Message-ID: <20191104180657.6e5c2822@mistral> (raw)
In-Reply-To: <871ruphtfq.fsf@telefonica.net>
On Sun, 03 Nov 2019 16:26:49 +0100
Óscar Fuentes <ofv@wanadoo.es> wrote:
> jonetsu <jonetsu@teksavvy.com> writes:
>
> [...]
> [...]
>
> File a feature request with M-x report-emacs-bug.
I would have thought that emacs, being of such flexibility, would have
had someone through the years fed up with those ediff prompts and
created some lisp code (a language I do not know) to circumvent them.
And so I bought a dedicated tool to do those long diffs that have to be
done.
I might file a FR also about this and the 3 other points mentioned at
the beginning of this thread. These are, I find, basic aspects in
doing any long diffs between folders and files. How old is ediff ? I
guess a FR can get filed, and maybe in emacs 32 ... :)
Cheers.
next prev parent reply other threads:[~2019-11-04 23:06 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 [this message]
2019-12-09 12:58 ` jonetsu
2019-12-10 2:26 ` Michael Heerdegen
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=20191104180657.6e5c2822@mistral \
--to=jonetsu@teksavvy.com \
--cc=help-gnu-emacs@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.
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).