From: sandro dentella <sandro@e-den.it>
To: Thierry Volpiatto <thierry.volpiatto@gmail.com>
Cc: help-gnu-emacs@gnu.org
Subject: Re: ediff & No newline at end of file
Date: Sat, 21 Jun 2008 10:45:52 +0200 [thread overview]
Message-ID: <20080621084552.GA4217@ubuntu> (raw)
In-Reply-To: <871w2r2no5.fsf@thievol.homelinux.org>
On Sat, Jun 21, 2008 at 10:32:42AM +0200, Thierry Volpiatto wrote:
> sandro dentella <sandro@e-den.it> writes:
>
> > On 21 Giu, 07:03, Thierry Volpiatto <thierry.volpia...@gmail.com>
> > wrote:
> >> Hi,
> >> that will not correct your problem but help in the future.
> >>
> >> ,----
> >> | ;; Add newline at end of files
> >> | (setq require-final-newline t)
> >> `----
> >> Now when you edit a file and you save it it will have a newline at end.
> >
> >
> > I already have it, the fact is that I use if with files generated by
> > others as well...
> You can easily write a small function that take as args file1 and file2
> and modify these files before calling ediff.
> something like:
my wrote my 'emadiff' as:
for f in $1 $2
do
if [ $(tail -n1 $f|wc -c |sed 's/ //') -gt 0 ] ; then
echo -e "\n" >> $f
fi
done
#gnuclient --eval "(ediff-buffers \"$f1\" \"$f2\")" $f1 $f2
emacs --eval "(ediff-files \"$1\" \"$2\")"
so does exactly what you suggest, but I think is a workaround that I'd like
to avoid. It seems strange to me that emacs just stops working when it could
just issue a waring on nothing at all. I'd expect a configuration parameter
to silent it as there's a configuration parameter that says "add a newline
at the end".
Thanks anyhow
sandro
*:-)
next prev parent reply other threads:[~2008-06-21 8:45 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-20 9:40 ediff & No newline at end of file sandro dentella
2008-06-20 9:44 ` sandro dentella
2008-06-21 5:03 ` Thierry Volpiatto
[not found] ` <mailman.13646.1214024246.18990.help-gnu-emacs@gnu.org>
2008-06-21 7:28 ` sandro dentella
2008-06-21 8:32 ` Thierry Volpiatto
2008-06-21 8:45 ` sandro dentella [this message]
2008-06-21 14:47 ` Kevin Rodgers
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20080621084552.GA4217@ubuntu \
--to=sandro@e-den.it \
--cc=help-gnu-emacs@gnu.org \
--cc=thierry.volpiatto@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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.