unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: help-gnu-emacs@gnu.org
Subject: Re: Starting emacs in ediff mode.
Date: Sat, 26 Jan 2008 10:44:17 +0200	[thread overview]
Message-ID: <ubq79m0wu.fsf@gnu.org> (raw)
In-Reply-To: <f7ccd24b0801250903v4743e262l4bdd69634ec497e9@mail.gmail.com> (lekktu@gmail.com)

> Date: Fri, 25 Jan 2008 18:03:30 +0100
> From: "Juanma Barranquero" <lekktu@gmail.com>
> Cc: help-gnu-emacs@gnu.org
> 
> > > >    emacs --eval "(ediff-files \"file_1\" \"file_2\")"
> 
> I think Lennart is saying that if file_1 and file_2 are relative,

Really?  It works for me with relative file names (of course, I used
"-q" as well, so if someone changes directory in their .emacs, that
could be a problem).

> Emacs does not find them, and if they are absolute, the backslashes in
> the paths cause problems (at the very least, they must be escaped
> themselves).

Or use forward slashes; nothing new here.

> > I don't see how is this relevant to the OP's question: if they already
> > have Emacs running, they could simply invoke Ediff from within that
> > Emacs session.  And if Emacs is not running, what's the advantage of
> > using emacsclient?
> 
> Lennart's patched emacsclient starts Emacs automatically.

That's fine, but I asked what was the _advantage_ of using
emacsclient instead of invoking Emacs itself?

  reply	other threads:[~2008-01-26  8:44 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 [this message]
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
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=ubq79m0wu.fsf@gnu.org \
    --to=eliz@gnu.org \
    --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).