From: Bogdan Hlevca <bhlevca@adexa.com>
Subject: ediff-files from command line ?
Date: Mon, 27 Jan 2003 15:19:26 -0500 [thread overview]
Message-ID: <%ugZ9.248018$C8.834913@nnrp1.uunet.ca> (raw)
Hi,
I'd like to automate an ediff process for a post run test analysis.
Apparently with -f command line argument you can pass only functions
without arguments.
ediff-files requires arguments and it will fail when trying to do:
$ emacs -f ediff-files "file1" "file2"
I could do: $ emacs "file1" "file2" and then issue the command M-x
ediff-buffers and followed by 2 other key strokes, but this is not much
of an automation.
Any help/ideea would be appreciated.
Thanks,
Bogdan
next reply other threads:[~2003-01-27 20:19 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-27 20:19 Bogdan Hlevca [this message]
2003-01-27 22:51 ` ediff-files from command line ? Kevin Rodgers
2003-01-31 23:36 ` Jeffery B. Rancier
[not found] ` <mailman.1288.1044056408.21513.help-gnu-emacs@gnu.org>
2003-02-01 18:56 ` Benjamin Riefenstahl
2003-02-03 17:23 ` Kevin Rodgers
2003-02-03 18:04 ` Jeffery B. Rancier
[not found] <zqgZ9.248016$C8.834913@nnrp1.uunet.ca>
2003-01-27 22:10 ` Who indeed?
2003-01-27 22:58 ` Bogdan Hlevca
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='%ugZ9.248018$C8.834913@nnrp1.uunet.ca' \
--to=bhlevca@adexa.com \
/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).