unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Michael Kifer <kifer@cs.sunysb.edu>
To: Juri Linkov <juri@jurta.org>
Cc: Chong Yidong <cyd@stupidchicken.com>, David Kastrup <dak@gnu.org>,
	Michael Kifer <kifer@cs.stonybrook.edu>,
	emacs-devel@gnu.org
Subject: Re: Ediff-patch-file with wrong default buffer (was: Fix info display of images)
Date: Mon, 14 Dec 2009 00:43:25 -0500	[thread overview]
Message-ID: <20091214004325.61e9afe3@kiferserv> (raw)
In-Reply-To: <87ocm2p1vf.fsf_-_@mail.jurta.org>



On Mon, 14 Dec 2009 07:14:12 +0200
Juri Linkov <juri@jurta.org> wrote:

> >> This is not just improvement, but a plain bug fix.  I suggest to
> >> install it.
> >>
> >> Since IIUC currently CVS is read-only, you could create a bug report
> >> in the bug database to guarantee your bug fix is not lost and fixed in
> >> the next release.
> >
> > It is not read-only yet, I think.  Please go ahead and install the
> > patch.
> 
> Installed.
> 
> BTW, there is some regression in Ediff.
> 
> Running `ediff-patch-file' in a buffer with the patch used to propose
> the name of the current buffer by default, but now it proposes some
> irrelevant buffer name.
> 
> This bug can be reproduced by opening the initial David's message with the
> patch in this thread and typing `M-x ediff-patch-file'.  To the question
> "Is the patch already in a buffer" type `y'.  After that in the prompt
> "Buffer that holds the patch" it provides some other buffer by default.
> It used to provide the current buffer by default.
> 
> Maybe the reason is that Ediff recognizes buffers with patches only
> in the CVS format?  In this case Ediff should be fixed to support
> other formats since we are switching from CVS now.


I haven't looked at the ediff patch, which you are referring to, but, FYI,
Ediff only looks at the current buffer, the next, and the previous, window, and
the other-buffer. It does not attempt to search for the best possible buffer.
In those buffers that it looks at, it tries to see if it has a diff or a context
diff. This is controlled by ediff-context-diff-label-regexp.

So, either the patch that you are referring to broke the above behavior or the
current buffer does not match ediff-context-diff-label-regexp.





  reply	other threads:[~2009-12-14  5:43 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-12-05 23:48 Fix info display of images David Kastrup
2009-12-07 17:55 ` Juri Linkov
2009-12-07 20:28   ` David Kastrup
2009-12-13 11:09     ` David Kastrup
2009-12-13 18:31       ` Juri Linkov
2009-12-14  4:16         ` Chong Yidong
2009-12-14  5:14           ` Ediff-patch-file with wrong default buffer (was: Fix info display of images) Juri Linkov
2009-12-14  5:43             ` Michael Kifer [this message]
2009-12-14  5:47               ` Ediff-patch-file with wrong default buffer Juri Linkov
2009-12-14  6:15                 ` Michael Kifer
2009-12-14  6:54                   ` Juri Linkov
2010-02-02  0:31                     ` Juri Linkov
2010-02-02  2:34                       ` Stefan Monnier
2010-02-02 22:38                         ` Juri Linkov
2010-02-02  0:33                     ` Juri Linkov
2009-12-14  9:35                 ` Andreas Schwab

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=20091214004325.61e9afe3@kiferserv \
    --to=kifer@cs.sunysb.edu \
    --cc=cyd@stupidchicken.com \
    --cc=dak@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=juri@jurta.org \
    --cc=kifer@cs.stonybrook.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).