unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Benjamin Riefenstahl <Benjamin.Riefenstahl@epost.de>
Cc: Emacs development <emacs-devel@gnu.org>
Subject: Re: Build error: "nmake info" in "emacs/man"
Date: Fri, 10 Sep 2004 20:08:23 +0200	[thread overview]
Message-ID: <m3mzzygfoo.fsf@seneca.benny.turtle-trading.net> (raw)
In-Reply-To: <v9k6v244se.fsf@marauder.physik.uni-ulm.de> (Reiner Steib's message of "Fri, 10 Sep 2004 15:44:33 +0200")

Hi Reiner,

Reiner Steib <4.uce.03.r.s@nurfuerspam.de> writes:
> Are you sure that `&' gives you the desired behavior?  At least with
> bash on GNU/Linux, the makeinfo command would be execute in the
> previous directory instead of $(srcdir), I think:

The difference is the shell used.  & is documented as a command
separator for CMD.EXE.   I don't know if COMMAND.COM also supports it
(on 98/Me). 

benny

  reply	other threads:[~2004-09-10 18:08 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-09-08  6:10 Build error: "nmake info" in "emacs/man" Dhruva Krishnamurthy
2004-09-08 12:58 ` Reiner Steib
2004-09-08 15:24 ` Eli Zaretskii
2004-09-08 16:59   ` Reiner Steib
2004-09-09  3:47     ` Eli Zaretskii
2004-09-09  4:58       ` Dhruva Krishnamurthy
2004-09-09 19:06         ` Eli Zaretskii
2004-09-10  5:57           ` Dhruva Krishnamurthy
2004-09-10  7:36             ` Jason Rumney
2004-09-10  9:22               ` Eli Zaretskii
2004-09-10  9:38                 ` Dhruva Krishnamurthy
2004-09-10 11:20                   ` Jason Rumney
2004-09-10 12:51                     ` Dhruva Krishnamurthy
2004-09-10 13:44                       ` Reiner Steib
2004-09-10 18:08                         ` Benjamin Riefenstahl [this message]
2004-09-10 19:11                           ` Peter 'Luna' Runestig
2004-09-11 13:57                             ` Benjamin Riefenstahl
2004-09-09 10:44       ` Reiner Steib
2004-09-09 19:14         ` Eli Zaretskii
2004-09-09  7:34     ` Peter 'Luna' Runestig

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=m3mzzygfoo.fsf@seneca.benny.turtle-trading.net \
    --to=benjamin.riefenstahl@epost.de \
    --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).