|
 |
On 8/27/2013 3:57 PM, clipka wrote:
> Am 27.08.2013 23:19, schrieb Patrick Elliott:
>> On 8/27/2013 3:31 AM, Stephen wrote:
>>> "Fractracer" <lg.### [at] gmail com> wrote:
>>>
>>>>
>>>> I remember win95, a good user interface with DOS - where is DOS now?
>>>
>>> Hidden in the command prompt box: cmd.exe
>>>
>>>
>>>
>>>
>> Uh. No. That is a shell, yes, and it "sort of" works like DOS, but.. its
>> oddly missing like.. every single added program that ever came with, it,
>> including "basic" ones, like ways to make your "shell" wait for a
>> keypress, or any other damn thing at all. And, of course, since they
>> *don't* want you to actually use it, they never added in any of the
>> features that might have gotten into it (if they had stolen them from
>> say 4DOS, or others), before Win3.11 came around.
>
> Well, they /did/ add support for blanks in command parameters at least.
> And for long filenames, thank God and all the angels! (Cursed be every
> piece of software that still makes any use of 8.3 filenames! - They're
> /still/ in Windows for backward compatibility.)
>
> As for them not wanting you to use it, what they do want you to use
> nowadays is the PowerShell. Not that I've ever heard of anyone using it
> to solve any scripting tasks though: They either seem to be using .bat
> files for cmd.exe, or asking you to install python.
>
Except that it can't bloody make up its mind when it works, and doesn't,
some times. You get the same problem though trying to manually edit
links. If you don't put "" around certain things the OS, despite
supposedly knowing about bloody spaces in file names, freaks out and
won't save it. Because, you know, the GUI should get just as confused by
such names as the cmd.exe program does... lol
Post a reply to this message
|
|
