From: Eli Zaretskii <eliz@gnu.org>
To: Stefan Monnier <monnier@iro.umontreal.ca>,
Kenichi Handa <handa@m17n.org>
Cc: 1183@emacsbugs.donarmstrong.com, bug-gnu-emacs@gnu.org,
kifer@cs.stonybrook.edu
Subject: bug#1183: 23.0.60; ediff-buffers is broken
Date: Fri, 17 Oct 2008 20:34:27 +0200 [thread overview]
Message-ID: <uvdvrkr4c.fsf@gnu.org> (raw)
In-Reply-To: <jwvskqvi5mx.fsf-monnier+emacsbugreports@gnu.org>
> From: Stefan Monnier <monnier@iro.umontreal.ca>
> Cc: 1183@emacsbugs.donarmstrong.com, bug-gnu-emacs@gnu.org, Michael Kifer <kifer@cs.stonybrook.edu>
> Date: Fri, 17 Oct 2008 12:02:11 -0400
>
> > In a discussion in Oct 2007, Stefan said that using the buffer's
> > encoding is wrong, see:
>
> > http://lists.gnu.org/archive/html/emacs-devel/2007-10/msg01381.html
>
> > Stefan wanted to use the equivalent of emacs-mule for Emacs 23 instead
> > of buffer's encoding, but do we have such an encoding now? Is
> > no-conversion-multibyte it? Or maybe utf-8 is good enough?
>
> As mentioned in the past, I think `no-conversion' should be killed
> because it's confusing. As for the problem at hand, utf-8-emacs-unix is
> what we want to use.
Suppose we write the temp files with utf-8-emacs-unix encoding--won't
that bite us when the output from Diff is then read with raw-text (see
ediff-exec-process)?
If raw-text won't work for utf-8-emacs output from Diff, is there a
better way than overriding the coding-system priorities with
`with-coding-priority'?
> > But first, we should decide whether we want such buffers to compare
> > equal or not.
>
> I believe we do, because it's called ediff-buffers. There's ediff-files
> for when you want to compare the files.
Don't you think having direct file comparison yield results that are
different from comparing buffers that visit those same files will be
confusing?
next prev parent reply other threads:[~2008-10-17 18:34 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <ur66ck3d4.fsf@gnu.org>
2008-10-16 18:47 ` bug#1183: 23.0.60; ediff-buffers is broken Drew Adams
2008-10-16 20:25 ` Eli Zaretskii
2008-10-16 20:45 ` Drew Adams
2008-10-16 21:15 ` Eli Zaretskii
2008-10-16 21:58 ` Drew Adams
2008-10-17 12:38 ` Eli Zaretskii
2008-10-17 14:36 ` Drew Adams
2008-10-17 16:02 ` Stefan Monnier
2008-10-17 16:48 ` Drew Adams
2008-10-17 17:05 ` Michael Kifer
2008-10-17 17:17 ` Drew Adams
2008-10-17 18:15 ` Eli Zaretskii
2008-10-17 18:35 ` Drew Adams
2008-10-18 3:17 ` Michael Kifer
2008-10-18 3:43 ` Drew Adams
2008-10-18 9:07 ` Eli Zaretskii
2008-10-19 2:17 ` Stefan Monnier
2008-10-19 7:17 ` Eli Zaretskii
2008-10-19 7:23 ` Eli Zaretskii
2008-10-19 8:32 ` Eli Zaretskii
2008-10-19 15:07 ` Drew Adams
2008-10-19 15:32 ` Eli Zaretskii
2008-10-17 18:19 ` Eli Zaretskii
2008-10-17 18:35 ` Drew Adams
2008-10-17 18:34 ` Eli Zaretskii [this message]
2008-10-19 2:21 ` Stefan Monnier
2008-10-19 15:40 ` bug#1183: marked as done (23.0.60; ediff-buffers is broken) Emacs bug Tracking System
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=uvdvrkr4c.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=1183@emacsbugs.donarmstrong.com \
--cc=bug-gnu-emacs@gnu.org \
--cc=handa@m17n.org \
--cc=kifer@cs.stonybrook.edu \
--cc=monnier@iro.umontreal.ca \
/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).