unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: DaLoverhino <DaLoveRhino@hotmail.com>
To: help-gnu-emacs@gnu.org
Subject: Re: Starting emacs in ediff mode.
Date: Thu, 24 Jan 2008 08:40:48 -0800 (PST)	[thread overview]
Message-ID: <560a3e25-00da-4f6e-9f1a-8f62ac298bd8@c4g2000hsg.googlegroups.com> (raw)
In-Reply-To: mailman.6460.1201142559.18990.help-gnu-emacs@gnu.org

On Jan 23, 9:42 pm, Kevin Rodgers <kevin.d.rodg...@gmail.com> wrote:
> DaLoverhino wrote:
> > Hello.  I would like to use emacs as I would use say diff or sdiff.
>
> > Is there a way to start emacs in ediff mode and pass along with it
> > through the command line, the two files I want to ediff?  If the
> > command line is unwieldy, I can always wrap it up in a script.
>
> emacs --eval '(ediff-files "file_1" "file_2")'
>
> --
> Kevin Rodgers
> Denver, Colorado, USA

Thanks.  It works from the command line, but when I put it in a shell,
it doesn't seem to work.  Do you know what is going on?

#!/bin/bash

fileA=$1
fileB=$2

if [[ -z "$fileA" && -z "$fileB" ]]
then
  echo "Need two files to ediff."
  exit 1
fi



evalArg="'(ediff-files \"$fileA\" \"$fileB\" )'"

echo emacs --geometry 150x80 --eval $evalArg

emacs --geometry 150x80 --eval $evalArg

exit 0

  parent reply	other threads:[~2008-01-24 16:40 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-01-24  0:51 Starting emacs in ediff mode DaLoverhino
2008-01-24  2:42 ` Kevin Rodgers
2008-01-24 16:50   ` Lennart Borgman (gmail)
2008-01-25  9:45     ` Eli Zaretskii
2008-01-25 14:55       ` Lennart Borgman (gmail)
2008-01-25 16:48         ` Eli Zaretskii
2008-01-25 17:03           ` Juanma Barranquero
2008-01-26  8:44             ` Eli Zaretskii
2008-01-26 13:46               ` Juanma Barranquero
2008-01-26 14:21                 ` Lennart Borgman (gmail)
     [not found]                 ` <mailman.6567.1201357297.18990.help-gnu-emacs@gnu.org>
2008-01-26 19:50                   ` Stefan Monnier
2008-01-26 20:52                     ` Lennart Borgman (gmail)
2008-01-26 21:55                       ` Stefan Monnier
     [not found]             ` <mailman.6561.1201337056.18990.help-gnu-emacs@gnu.org>
2008-01-27 13:17               ` Richard G Riley
2008-01-27 14:55                 ` Juanma Barranquero
2008-01-27 15:13                   ` Lennart Borgman (gmail)
2008-01-27 22:25                     ` Juanma Barranquero
2008-01-28 16:00                   ` reader
2008-01-28 16:36                     ` Thierry Volpiatto
2008-01-28 16:43                       ` Juanma Barranquero
     [not found]                 ` <mailman.6605.1201445728.18990.help-gnu-emacs@gnu.org>
2008-01-28 11:32                   ` Richard G Riley
     [not found]         ` <mailman.6531.1201279722.18990.help-gnu-emacs@gnu.org>
2008-01-25 20:58           ` DaLoverhino
2008-01-26  7:08             ` Thierry Volpiatto
     [not found] ` <mailman.6460.1201142559.18990.help-gnu-emacs@gnu.org>
2008-01-24 16:40   ` DaLoverhino [this message]
2008-01-24 18:03     ` Thien-Thi Nguyen
2008-01-24 18:50     ` Rob Wolfe
2008-01-25 20:51       ` DaLoverhino

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=560a3e25-00da-4f6e-9f1a-8f62ac298bd8@c4g2000hsg.googlegroups.com \
    --to=daloverhino@hotmail.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).