DomainKey-Signature: a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:mime-version:in-reply-to:references:date
	:message-id:subject:from:to:content-type; q=dns; s=default; b=TK
	LABr7q2IlTdz+AZd8u1U6+cMZiSsirHHJUIG9HUJMcJZWgoU7majCW9azv9o/ln3
	BlrsLcpEzwN1KlPpd4xJoI9cCtHqJqQy7bNqOtvP5TUdcAAVoUW5P35fibMIzrYt
	3QQB29igH24aNmf3PvZ6jbfDBRA+RuS0SWe9AcNj4=
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
MIME-Version: 1.0
In-Reply-To: <CAEF1h+WELCS56_5Up2UBKbQxAhj37Rs50p3gojSceLSfOHyu3w@mail.gmail.com>
References: <CAEF1h+WELCS56_5Up2UBKbQxAhj37Rs50p3gojSceLSfOHyu3w AT mail DOT gmail DOT com>
Date: Sat, 2 Apr 2016 12:34:10 -0700
Message-ID: <CAOC2fq_VRWLgHhPpK6PkAUXrtmxiDZx5tkwugD6jF9YgG5VKaw@mail.gmail.com>
Subject: Re: pass arguments enclosed with double quotes from bash shell to windows program
From: Michael Enright <mike AT kmcardiff DOT com>
To: cygwin AT cygwin DOT com
Content-Type: text/plain; charset=UTF-8

On Sat, Apr 2, 2016 at 11:59 AM, Cary Lewis wrote:
> I need to start acrobat from a bash shell.
>
> Acrobat needs some of its parameters to be enclosed with double
> quotes. This is needed to automatically open and print a pdf.
>
>
> If I try to do a \", then it passes the \" to the windows app.

I frequently use WinMerge, a graphical text file comparision program,
from the bash shell. Occasionally this involves a file in the current
directory vs a file at the end of a path full of spaces and slashes.
If this question had come up yesterday I could have looked at my
history for examples. My recollection is that the rules for expanding
arguments enclosed in single quotes are helpful. Single-quoted
arguments are processed much less by bash than even double-quoted
arguments. A simple example is if you need to put a backslash in an
environment variable, you don't have as many layers to fight if you
use single quotes export regex='search\$'. I also use $(cygpath) in
some fashion to convert the path since WinMerge is not a Cygwin
program. I get the full path to one of the files using tab completion,
and then I modify the path by surrounding it with the necessary
cygpath syntax to convert the path to a Windows path.

--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple