Mail Archives: cygwin/2003/01/24/20:33:35
Boy I just don't GET IT!!!!!! Anyone who wants to use ANY cmd.exe
command, including start just needs to use cmd /c
ANY-WINDOWS-CMD-COMMAND-HERE
HOW EASY IS THAT?????
Maybe adding this insight to the FAQ might be helpful - for those who
FAIL to read the SIMPLE output from cmd /? ...
Of course - will such people read the FAQ "BEFORE" bothering the busy
folks on this list????
NOT!!!!!!!!!!!!!
Brian Kelly
PS (One can also use cmd /c to run CYGWIN utilities - even something
like
cmd /c start cmd /c rm -rf * which will run as separate process
enabling you to return to the command line. VERY COOL - for those who
READ DOCUMENTATION!! Of course - we didn't mention "fork" ... Windows
folks eat with their hands - primitive savages that they are )
-----Original Message-----
From: cygwin-owner AT cygwin DOT com [mailto:cygwin-owner AT cygwin DOT com] On Behalf
Of Max Bowsher
Sent: Friday, January 24, 2003 7:02 PM
To: caelum AT debian DOT org; cygwin AT cygwin DOT com
Subject: Re: idea for a new project, libntcmd
Rafael Kitover wrote:
>>> 2) support cmd.exe builtins like del/copy/exists/etc, and execute
>>> dos batch files. Things like if and goto, because they're only
>>> useful in batch, would present little problem as well.
>>
>> Yuk! Why?
>
> Often when I go between cmd and zsh, I get my copy/cp del/rm mixed up.
> This would also apply to folks who have to use both the unix and
> windows command lines on a regular occasion.
Solution: Don't use cmd ;-)
No, seriously, wouldn't shell aliases and/or stub .exes or batch files
give
you most of this functionality *right now*?
> Also to support simple
> Makefiles, batch files etc. in various packages.
I have to ask: Why try to coerce a makefile designed for a cmd.exe shell
into running with bash?
> Making aliases or shell functions would not work well, because those
> are not propagated to subprocesses.
Aliases, no, unless you put them in your shell's startup file. In bash
at
least, you can 'export -f' functions.
>>> This would allow better interaction between the windows and cygwin
>>> worlds, and also be convenient for windows users new to unix.
>>
>> Really? Or would it simply delay them learning the knowledge to
>> function in
>> an environment that does not make specific allowances for them?
>
> Well, the goal would be for new cygwin users, who often have little
> knowledge of UNIX, to have more space to get comfortable in learning
> the environment.
Chris answered this perfectly.
Anyway, a compatibility package of shell scripts or stub exes ought to
be
easy to acheive, and has the advantage of working with all shells.
>>> It should also allow for running windows makefiles
>>> as-is.
>>
>> This feels more like MSYS territory than Cygwin.
>
> This would be useful for MSYS, which is a fork of Cygwin too of
> course. We don't want MSYS to diverge too greatly, especially since
> Cygwin is a perfectly functional environment for building mingw
> programs.
Define "We" ;-)
>>> Thoughts? Is this interesting/crazy/impossible?
>>
>> Well, you're getting a biased opinion here - I hate cmd. But I think
>> this
>> has 2 flaws:
>>
>> 1) You want to make bash play nice with Windows paths - what about
>> all those
>> supplementary tools that makefiles often invoke?
>
> If a makefile uses visual studio or borland tools, we'd assume the
> user has those installed and in their paths. Perhaps some simple
> wrappers for some visual studio command line tools could also be made
> to use the cygwin equivalents.
But then why does this makefile want to run under Cygwin make and bash??
Max.
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Bug reporting: http://cygwin.com/bugs.html
Documentation: http://cygwin.com/docs.html
FAQ: http://cygwin.com/faq/
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Bug reporting: http://cygwin.com/bugs.html
Documentation: http://cygwin.com/docs.html
FAQ: http://cygwin.com/faq/
- Raw text -