unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: Bob Doolittle <Robert.Doolittle@Sun.COM>
To: "Lennart Borgman gmail - lennart.borgman@gmail.com"
	<+fredf+bobdsun+f8d8cd63cb.lennart.borgman#gmail.com@spamgourmet.com>
Cc: help-gnu-emacs@gnu.org
Subject: Re: Looking for an ediff window setup function - two files in new frames
Date: Sat, 03 Mar 2007 19:23:56 -0500	[thread overview]
Message-ID: <45EA119C.2040501@Sun.COM> (raw)
In-Reply-To: <45EA085D.9000603@gmail.com>

Lennart Borgman gmail - lennart.borgman@gmail.com wrote:
> fredf.bobdsun@antichef.net wrote:
>> Does anybody have or know the whereabouts of an elisp
>> ediff-window-setup-function which makes two new
>> frames to display the files being diff'd?  It should then
>> delete the frames when the ediff completes/quits.
>>
>> This seems like it'd be highly desirable and is probably
>> already written somewhere.  I want this because I'm
>> driving the ediff from gnuclient and using an existing
>> version of emacs.
>>
>> Thanks,
>>   Bob
>
>
> Couldn't you just call make-frame-command first in the function you 
> call from gnuclient and then call ediff?
>
> Or just do the call in two steops from gnuclient?

In my case there's a chance (not a certainty) the files are already open 
in existing
frames, so this doesn't work.  I'm a pretty crude elisp hacker, but I 
did write a function
to make-frame and then find-file in that frame for each file first, but 
I couldn't get the
cleanup to work (couldn't find a suitable hook in ediff where the 
buffers/frames weren't
active).  It seems it would be easier in a window-setup-function, since 
this is its job.

-Bob

      reply	other threads:[~2007-03-04  0:23 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-03-03 23:34 Looking for an ediff window setup function - two files in new frames fredf.bobdsun
2007-03-03 23:44 ` Lennart Borgman (gmail)
2007-03-04  0:23   ` Bob Doolittle [this message]

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=45EA119C.2040501@Sun.COM \
    --to=robert.doolittle@sun.com \
    --cc=+fredf+bobdsun+f8d8cd63cb.lennart.borgman#gmail.com@spamgourmet.com \
    --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.
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).