On 1/31/2012 9:52 AM, nemesis wrote:
> Invisible<voi### [at] devnull>  wrote:
>>>>> Btw, if you use bash,
>>>>
>>>> Nope. CMD.EXE.
>>>
>>> oh, a masochist. My bad...
>>
>> It's the standard command interpreter on Windows. Shame it sucks, but hey.
>
> yeah, you can also use the (sub)standard text editor that comes with it and
> likewise for browser, image editor, shame whip etc...
>
>
Used to use 4Dos to extend that thing, but I refuse to pay what they 
want, just to add some color masking of file types, and a few commands, 
how ever useful, that MS never bothered to. MS decided a "better" 
solution was to create a command line "scripting host", which lacks the 
sandboxing that prevents it running some system commands instead regular 
applications. However, since they never gave anyone a damn clue it 
exists, or provided any easy way to figure out how the hell to use it... lol

Post a reply to this message