From: Daniel Colascione <dan.colascione@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: jasonr@gnu.org, emacs-devel@gnu.org
Subject: Re: Fixing Windows and DOS command line argument quoting
Date: Tue, 26 Apr 2011 03:44:31 -0700 [thread overview]
Message-ID: <4DB6A20F.2050106@gmail.com> (raw)
In-Reply-To: <837hai9nir.fsf@gnu.org>
[-- Attachment #1: Type: text/plain, Size: 711 bytes --]
On 4/25/11 11:47 AM, Eli Zaretskii wrote:
>> Date: Mon, 25 Apr 2011 10:56:07 -0700
>> From: Daniel Colascione <dan.colascione@gmail.com>
>> I'd like to remove this path in the trunk and see whether the new
>> 8192-character length limitation is a problem in practice.
>
> No, I don't think it's a good idea. 8K is too low by any measure; we
> already hit the shell limitations once or twice when related problems
> were discussed.
All right.
> What are the disadvantages of detecting quoted command lines and
> sending only those through the shell?
Besides complexity, none. I've implemented this approach, making the
necessary changes to cmdproxy.c and subr.el, and updated the trunk.
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 195 bytes --]
next prev parent reply other threads:[~2011-04-26 10:44 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 [this message]
2011-04-26 17:50 ` Eli Zaretskii
2011-04-25 9:35 ` Eli Zaretskii
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4DB6A20F.2050106@gmail.com \
--to=dan.colascione@gmail.com \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=jasonr@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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.