This is the mail archive of the
cygwin
mailing list for the Cygwin project.
Re: The Beauty of Cygstart
- From: Igor Peshansky <pechtcha at cs dot nyu dot edu>
- To: zzapper <david at tvis dot co dot uk>
- Cc: cygwin at cygwin dot com
- Date: Fri, 24 Mar 2006 08:55:41 -0500 (EST)
- Subject: Re: The Beauty of Cygstart
- References: <Xns979067AC0328Czzappergmailcom@80.91.229.5>
- Reply-to: cygwin at cygwin dot com
On Fri, 24 Mar 2006, zzapper wrote:
> zzapper <david@XXXX.XX.XX> wrote in Xns979065E51F443zzappergmailcom@80.91.229.5:">news:Xns979065E51F443zzappergmailcom@80.91.229.5:
Even it if's your own, <http://cygwin.com/acronyms/#PCYMTNQREAIYR>.
> Whoops forget the vital & (launch in own process)
>
> function cs() {cygstart *$1* &}
> function csn() {cygstart "$(/bin/ls -t *.* | head -1)" &}
> function csl() { cygstart.exe *$(history -1 | sed "s/.* //g")* & }
The "&" isn't needed for cygstart, as it simply tells the shell to execute
the proper association and exits. The only point at which backgrounding
would help is the short time it takes for the shell to figure out what the
association is (nearly instantaneous on my machine).
FWIW, another use for cygstart is to launch a Cygwin application in a new
window (e.g., I use "cygstart bash" quite a bit) and to launch some
Windows application without leaving the Cygwin exec stub process behind
(e.g., "cygstart setup" is very very useful).
HTH,
Igor
--
http://cs.nyu.edu/~pechtcha/
|\ _,,,---,,_ pechtcha@cs.nyu.edu | igor@watson.ibm.com
ZZZzz /,`.-'`' -. ;-;;,_ Igor Peshansky, Ph.D. (name changed!)
|,4- ) )-,_. ,\ ( `'-' old name: Igor Pechtchanski
'---''(_/--' `-'\_) fL a.k.a JaguaR-R-R-r-r-r-.-.-. Meow!
"Las! je suis sot... -Mais non, tu ne l'es pas, puisque tu t'en rends compte."
"But no -- you are no fool; you call yourself a fool, there's proof enough in
that!" -- Rostand, "Cyrano de Bergerac"
--
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/