From: Michael Heerdegen <michael_heerdegen@web.de>
To: help-gnu-emacs@gnu.org
Subject: Re: how to ediff with the diff buffers in separate frames?
Date: Wed, 26 Mar 2014 16:08:02 +0100 [thread overview]
Message-ID: <878urxroa5.fsf@web.de> (raw)
In-Reply-To: 53324DF7.3000907@iankelling.org
Ian Kelling <ian@iankelling.org> writes:
> > By default, Ediff should reuse your two frames when they are already
> > displaying the buffers to diff. Is that the case for you? If yes, I'm
> > not sure I understand your intention.
>
> No. That doesn't happen. Perhaps it is a problem with the dev version
> of emacs I'm using. I will investigate further. Thanks.
AFAIK, there are two possible reasons for that:
1. Have a look at `ediff-get-visible-buffer-window'. This is the
function that tries to find a frame (with a window) already displaying a
buffer to diff. Depending on your setup, it could be the case that one
of your frames is not "visible". For me, this is the case for example
when the frame is on another virtual desktop. Change this defun to see
whether this is the problem in your case:
(defun ediff-get-visible-buffer-window (buff)
(if (ediff-buffer-live-p buff)
(if (featurep 'xemacs)
(get-buffer-window buff t)
(get-buffer-window buff t))))
;; change this argument ^
2. There is a feature called "wide display". If it is enabled, ediff
always uses a two windowed frame. I'm not sure how it works and if it
is turned automatically.
Michael.
next prev parent reply other threads:[~2014-03-26 15:08 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-21 10:44 how to ediff with the diff buffers in separate frames? Ian Kelling
2014-03-21 11:23 ` Michael Heerdegen
2014-03-22 0:13 ` Ian Kelling
2014-03-24 22:32 ` Michael Heerdegen
2014-03-24 22:41 ` Drew Adams
2014-03-26 3:48 ` Ian Kelling
2014-03-26 13:31 ` Drew Adams
2014-03-26 15:08 ` Michael Heerdegen [this message]
2014-03-21 11:36 ` Eric Abrahamsen
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=878urxroa5.fsf@web.de \
--to=michael_heerdegen@web.de \
--cc=help-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 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.