delorie.com/archives/browse.cgi   search  
Mail Archives: cygwin/2008/01/10/18:38:27

X-Recipient: archive-cygwin AT delorie DOT com
X-Spam-Check-By: sourceware.org
Date: Thu, 10 Jan 2008 18:37:27 -0500 (EST)
From: Igor Peshansky <pechtcha AT cs DOT nyu DOT edu>
Reply-To: cygwin AT cygwin DOT com
To: =?ISO-8859-1?Q?Sven_K=F6hler?= <skoehler AT upb DOT de>
cc: cygwin AT cygwin DOT com
Subject: Re: [BUG?] run.exe and pdflatex
In-Reply-To: <fm68kg$431$1@ger.gmane.org>
Message-ID: <Pine.GSO.4.63.0801101834410.13638@access1.cims.nyu.edu>
References: <fm5sat$o04$1 AT ger DOT gmane DOT org> <Pine DOT GSO DOT 4 DOT 63 DOT 0801101505510 DOT 8742 AT access1 DOT cims DOT nyu DOT edu> <fm62p7$frr$1 AT ger DOT gmane DOT org> <Pine DOT GSO DOT 4 DOT 63 DOT 0801101700480 DOT 8742 AT access1 DOT cims DOT nyu DOT edu> <4786A227 DOT 1090007 AT upb DOT de> <fm68kg$431$1 AT ger DOT gmane DOT org>
MIME-Version: 1.0
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Id: <cygwin.cygwin.com>
List-Unsubscribe: <mailto:cygwin-unsubscribe-archive-cygwin=delorie DOT com AT cygwin DOT com>
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com
Note-from-DJ: This may be spam

---559023410-1804928587-1200008247=:13638
Content-Type: TEXT/PLAIN; charset=ISO-8859-1
Content-Transfer-Encoding: 8BIT

On Fri, 11 Jan 2008, Sven Köhler wrote:

> > Now i wonder, if it's already safe or if it would be possible to use
> > cygwin API (for example execve) from run.exe. To fix all the issues,
> > run.exe really would have to use cygwin to start the command since only
> > that will resolv all the issues (analysing the shebang, following
> > symlinks, etc.).
>
> OK, we cannot use execve, right?  If we would, it would open yet another
> console window will be opened for the program we'd like to exec, right?

Exactly.

> So is there any cygwin call to analyse a path? A call, that simply
> returns the program to execute, the parameters to pass, etc.?
>
> It really would really be better pass all the work (finding shebang,
> etc.) to cygwin so that it's consistent.

Yes, there is a well-known extensively tested way of handling shell
scripts, symlinks, etc.  It's called "using a shell".  Just execve your
favorite shell (/bin/bash is most likely to be present in all installs,
and /bin/sh in Cygwin is the same as bash), and pass it the executable
path as an argument.
	Igor
-- 
				http://cs.nyu.edu/~pechtcha/
      |\      _,,,---,,_	    pechtcha AT cs DOT nyu DOT edu | igor AT watson DOT ibm DOT com
ZZZzz /,`.-'`'    -.  ;-;;,_		Igor Peshansky, Ph.D. (name changed!)
     |,4-  ) )-,_. ,\ (  `'-'		old name: Igor Pechtchanski
    '---''(_/--'  `-'\_) fL	a.k.a JaguaR-R-R-r-r-r-.-.-.  Meow!

"That which is hateful to you, do not do to your neighbor.  That is the whole
Torah; the rest is commentary.  Go and study it." -- Rabbi Hillel

---559023410-1804928587-1200008247=:13638
Content-Type: text/plain; charset=us-ascii

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

- Raw text -


  webmaster     delorie software   privacy  
  Copyright © 2019   by DJ Delorie     Updated Jul 2019