public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Corinna Vinschen <corinna-cygwin@cygwin.com>
To: cygwin@cygwin.com
Subject: Re: Fails to launch batch script in some directories
Date: Fri, 20 Apr 2018 13:11:00 -0000	[thread overview]
Message-ID: <20180420131111.GS15911@calimero.vinschen.de> (raw)
In-Reply-To: <76873039-f459-5534-ce8a-bb8fcbd35274@gmail.com>

[-- Attachment #1: Type: text/plain, Size: 895 bytes --]

On Apr 20 14:33, David Macek wrote:
> Whoa, an interesting bug.  I'm forwarding this to the Cygwin mailing list for reference.  I might take a deeper look over the weekend if no-one beats me to it.
> 
> It seems like running batch files (.bat, .cmd) inside a directory with an at sign and a space (such as '@ x' or 'x @') fails.
> 
> /w/temp/@ x$ ./hello.bat
> 'W:\temp\@' is not recognized as an internal or external command,
> operable program or batch file.

Funny.  That's very likely a bug in the @file handling in function
insert_file() in dcrt0.cc.  This is basically stone-age old code
to pamper starting Cygwin tools with too long commandl ines from cmd.

I'm looking forward with what you're coming up with.


Corinna

-- 
Corinna Vinschen                  Please, send mails regarding Cygwin to
Cygwin Maintainer                 cygwin AT cygwin DOT com
Red Hat

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

  reply	other threads:[~2018-04-20 13:11 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <Alexpux/MSYS2-packages/issues/1225@github.com>
2018-04-20 12:33 ` David Macek
2018-04-20 13:11   ` Corinna Vinschen [this message]
2018-04-21 15:39     ` Brian Inglis
2018-04-23  6:43       ` David Macek
2018-04-23  8:45         ` Corinna Vinschen
2018-04-23 17:20           ` Brian Inglis
2018-04-24  7:55             ` Corinna Vinschen
2018-04-20 13:11   ` Brian Inglis

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=20180420131111.GS15911@calimero.vinschen.de \
    --to=corinna-cygwin@cygwin.com \
    --cc=cygwin@cygwin.com \
    /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.
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).