unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: "David Robinow" <drobinow@gmail.com>
To: emacs-devel@gnu.org
Subject: Re: Makefile bug in generating mh-loaddefs.el?
Date: Wed, 4 Jul 2007 19:06:38 -0400	[thread overview]
Message-ID: <4eb0089f0707041606h45f9eb54y64ef982f9f3ed179@mail.gmail.com> (raw)
In-Reply-To: <usl83dfp8.fsf@gnu.org>

On 7/4/07, Eli Zaretskii <eliz@gnu.org> wrote:
> > From: Bill Wohler <wohler@newt.com>
> > Date: Tue, 03 Jul 2007 21:44:56 -0700
> >
> > Tom's approach--writing to a temporary file and moving it at the
> > end--seems to answer all issues.
> But its implementation would be complicated on Windows, because we'd
> be reluctant to request the user to have yet another non-standard
> program (mv.exe) to be installed.
 I'm surprised by this comment.
 1) Windows uses a completely different makefile. One could choose not
to implement the feature on Windows.

 2) cp.exe and rm.exe are already required. Wouldn't the user already
have mv.exe from the same location as cp.exe and rm.exe?

3) What's wrong with "MV = move" in nmake.defs?
 For that matter, why not use copy and del instead of cp and rm ?

Am I missing something?

  reply	other threads:[~2007-07-04 23:06 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-07-03 18:42 Makefile bug in generating mh-loaddefs.el? Dan Nicolaescu
2007-07-03 20:00 ` Eli Zaretskii
2007-07-03 20:14   ` David Kastrup
2007-07-03 20:25     ` Tom Tromey
2007-07-03 20:55   ` Dan Nicolaescu
2007-07-04  3:17     ` Eli Zaretskii
2007-07-04  4:44       ` Bill Wohler
2007-07-04  6:21         ` David Kastrup
2007-07-04  8:46           ` Stephen J. Turnbull
2007-07-04 14:16           ` Tom Tromey
2007-07-04 14:19             ` Tom Tromey
2007-07-04 21:25         ` Eli Zaretskii
2007-07-04 23:06           ` David Robinow [this message]
2007-07-05  3:28             ` Eli Zaretskii

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=4eb0089f0707041606h45f9eb54y64ef982f9f3ed179@mail.gmail.com \
    --to=drobinow@gmail.com \
    --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).