From: Eli Zaretskii <eliz@gnu.org>
To: Daniel Colascione <dan.colascione@gmail.com>
Cc: emacs-devel@gnu.org
Subject: Re: Fixing Windows and DOS command line argument quoting
Date: Mon, 25 Apr 2011 12:35:52 +0300 [thread overview]
Message-ID: <83r58qad1j.fsf@gnu.org> (raw)
In-Reply-To: <4DB53599.8040703@gmail.com>
> Date: Mon, 25 Apr 2011 01:49:29 -0700
> From: Daniel Colascione <dan.colascione@gmail.com>
> CC: emacs-devel@gnu.org
>
> > . Please leave the `ms-dos' quoting as it was before. (Your research
> > and blog are not valid for the MS-DOS, a.k.a. DJGPP, build of
> > Emacs, which uses its own private way of passing and decoding
> > command lines, bypassing MS runtime and OS facilities. The
> > problems you mention in your blog do not exist in the MS-DOS
> > build.) Please make the new quoting method effective for the
> > `windows-nt' case alone.
>
> What happens when MS-DOS Emacs executes a non-DJGPP program?
I'm not interested in what happens in that case. It is a mess anyway,
because of the vastly different quoting features supported by the
stock DOS/Windows shells. Your method will work only on Windows NT
family, and only if the DJGPP library succeeds in forcing the OS to
use cmd.exe as the shell. (AFAIK, normally, Windows still loads
command.com for DOS programs.)
Anyway, DJGPP users know very well that to have a viable and stable
environment, they should use DJGPP programs in preference to the other
kind. If they don't, all bets are off, and the 126-character limit on
command lines doesn't leave you enough space to safely quote commands
anyway. The current quoting method worked well for the last 12 years,
so it ought to be good enough for these marginal cases.
> Doesn't it ever pass arguments through the command interpreter?
Only when the command explicitly invokes the shell, or some of its
non-trivial internal commands, or batch files. Otherwise, everything
is done internally, including pipes and redirections.
> It's been a very
> long time since I've used MS-DOS, and I don't know its command
> interpreter's behavior differs from that of NT's cmd.exe.
It is VERY different, especially where quoting is considered.
next prev parent reply other threads:[~2011-04-25 9:35 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-25 2:09 Fixing Windows and DOS command line argument quoting Daniel Colascione
2011-04-25 6:41 ` Eli Zaretskii
2011-04-25 8:49 ` Daniel Colascione
2011-04-25 8:58 ` Jason Rumney
2011-04-25 9:15 ` Eli Zaretskii
2011-04-25 9:22 ` Daniel Colascione
2011-04-25 17:56 ` Daniel Colascione
2011-04-25 18:47 ` Eli Zaretskii
2011-04-26 10:44 ` Daniel Colascione
2011-04-26 17:50 ` Eli Zaretskii
2011-04-25 9:35 ` Eli Zaretskii [this message]
2011-04-25 18:24 ` Daniel Colascione
2011-04-25 18:48 ` Eli Zaretskii
-- strict thread matches above, loose matches on Subject: below --
2011-04-27 0:58 Ben Key
2011-04-27 1:25 ` Daniel Colascione
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=83r58qad1j.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=dan.colascione@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).