unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Drew Adams <drew.adams@oracle.com>
Cc: 1183@emacsbugs.donarmstrong.com, bug-gnu-emacs@gnu.org,
	kifer@cs.stonybrook.edu, kifer@cs.sunysb.edu
Subject: bug#1183: 23.0.60; ediff-buffers is broken
Date: Sun, 19 Oct 2008 17:32:36 +0200	[thread overview]
Message-ID: <uprlwk3cb.fsf@gnu.org> (raw)
In-Reply-To: <005201c931fc$610aff00$0200a8c0@us.oracle.com>

> From: "Drew Adams" <drew.adams@oracle.com>
> Cc: <kifer@cs.sunysb.edu>, <1183@emacsbugs.donarmstrong.com>,
>         <bug-gnu-emacs@gnu.org>, <kifer@cs.stonybrook.edu>
> Date: Sun, 19 Oct 2008 08:07:17 -0700
> 
> > 	Fix Bug #1183:
> > 	* ediff-diff.el (ediff-exec-process): For buffer jobs, bind
> > 	coding-system-for-read to ediff-coding-system-for-write.
> > 	* ediff-util.el (ediff-make-temp-file): Unconditionally bind
> > 	coding-system-for-write to ediff-coding-system-for-write.
> > 	* ediff-init.el (ediff-coding-system-for-read): Doc fix.
> > 	(ediff-coding-system-for-write): Set to emacs-internal.
> 
> 
> Yes, it appears to be fixed, judging by the test case I sent.

Thanks for testing.  I closed the bug.






  reply	other threads:[~2008-10-19 15:32 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 [this message]
2008-10-17 18:19               ` Eli Zaretskii
2008-10-17 18:35                 ` Drew Adams
2008-10-17 18:34             ` Eli Zaretskii
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=uprlwk3cb.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=1183@emacsbugs.donarmstrong.com \
    --cc=bug-gnu-emacs@gnu.org \
    --cc=drew.adams@oracle.com \
    --cc=kifer@cs.stonybrook.edu \
    --cc=kifer@cs.sunysb.edu \
    /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).