From: Stephen Leake <stephen_leake@stephe-leake.org>
To: emacs-devel@gnu.org
Subject: Re: batch-byte-compile broken in 24.3.93?
Date: Wed, 10 Sep 2014 15:19:15 -0500 [thread overview]
Message-ID: <85vbovut30.fsf@stephe-leake.org> (raw)
In-Reply-To: <83ha0f9zeq.fsf@gnu.org> (Eli Zaretskii's message of "Wed, 10 Sep 2014 20:08:13 +0300")
Eli Zaretskii <eliz@gnu.org> writes:
> Does this work from a cmd window? (Of course, you will have to
> replace '..' quoting with "..".)
my bad; I was running this from a Makefile, and had Cygwin Emacs first
in PATH. With PATH fixed, all is well.
Sorry for the noise
--
-- Stephe
prev parent reply other threads:[~2014-09-10 20:19 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-10 13:06 batch-byte-compile broken in 24.3.93? Stephen Leake
2014-09-10 17:08 ` Eli Zaretskii
2014-09-10 20:19 ` Stephen Leake [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=85vbovut30.fsf@stephe-leake.org \
--to=stephen_leake@stephe-leake.org \
--cc=emacs-devel@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 public inbox
https://git.savannah.gnu.org/cgit/emacs.git
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).