Re: Emacs vista build failures

[David Kastrup <dak@gnu.org>]

Eli Zaretskii <eliz@gnu.org> writes:

>> From: David Kastrup <dak@gnu.org>
>> Date: Tue, 22 Jul 2008 16:34:58 +0200
>> Cc: hannes@saeurebad.de, emacs-devel@gnu.org
>> 
>> Eli Zaretskii <eliz@gnu.org> writes:
>> 
>> >> From: David Kastrup <dak@gnu.org>
>> >> Cc: hannes@saeurebad.de,  emacs-devel@gnu.org
>> >> Date: Tue, 22 Jul 2008 15:24:38 +0200
>> >> 
>> >> Yes, since COMMAND.COM and CMD.EXE behave quite differently, and also
>> >> differently on different versions of Windows.
>> >
>> > And zsh behaves differently from Bash which behaves differently from
>> > the Borne shell.
>> 
>> Not in the basic Bourne shell features.
>
> And COMMAND.COM behaves like CMD.EXE ``in the basic DOS shell
> features''.

The % quoting is different.  Particularly when you get into loops.
Command line parameters are different.  There are other things.

> This can go on forever, you know.  Your bias and lack of objective
> comparison are obvious.  No need to continue.

Sure, I get to different results than you after having worked with
everything.  Naturally that makes me biased.

>> >> So tell me: How to you quote the word (written as Lisp string) 
>> >> "\"goof\" " to the typical Windows shell?
>> >
>> > See the Emacs makefiles for Windows.
>> 
>> They don't quote such words.
>
> Yes, they do, see for example `check-declare' in lisp/makefile.w32-in.

So why don't you just tell me?  You are the expert on Windows, having
tested it thoroughly and found it easy to use.  Just tell me how to pass
the string "\"goof\" " from the command line to a Windows batch file so
that it assigns it to a single positional parameter, including the
quotes and the trailing spaces?

>> I have worked with DOS beginning with version 1.0 when they were
>> still mainly working with FCBs rather than file descriptors, and I
>> have worked with CP/M, and I have worked with UNIX on various
>> processors and OS/2.  I have done quite a bit of assembly and system
>> programming in all of those systems (many of that for pay), so I know
>> a lot of the inheritage, memory and system layouts, and I know a lot
>> of the implementations, and what system calls were done with what
>> sort of data structures when what sort of features were implemented
>> imitating features from elsewhere.
>
> Sorry, I'm not interested in a pissing contest.

Don't question my qualifications if you don't want to hear them.

-- 
David Kastrup