From: Werner LEMBERG <wl@gnu.org>
To: bug-gnu-emacs@gnu.org
Subject: bug#4328: ediff chokes on `No newline at end of file'
Date: Thu, 03 Sep 2009 13:27:58 +0200 (CEST) [thread overview]
Message-ID: <20090903.132758.219619836.wl@gnu.org> (raw)
[CVS of 2009-06-11]
If I compare two files, and the second of them misses a newline at its
end, I get
ediff-prepare-error-list: Errors in diff output.
Diff output is in #<buffer *ediff-diff<2>*>
in the echo area, and
\ No newline at end of file
is displayed.
IMHO, this is a bit harsh, and ediff should be able to cope with this
situation.
Werner
next reply other threads:[~2009-09-03 11:27 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-03 11:27 Werner LEMBERG [this message]
2009-09-03 18:47 ` bug#4328: ediff chokes on `No newline at end of file' Glenn Morris
2009-09-04 7:31 ` Werner LEMBERG
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=20090903.132758.219619836.wl@gnu.org \
--to=wl@gnu.org \
--cc=4328@emacsbugs.donarmstrong.com \
--cc=bug-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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.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).