Hiya,
Out of interest, what is meant by improving cmd.exe compatibility?
Jason
On Mon, Mar 3, 2008 at 3:38 PM, Ann & Jason Edmeades us@edmeades.me.uk wrote:
Hiya,
Out of interest, what is meant by improving cmd.exe compatibility?
Add support for all the cmd.exe switches and all the dos batch programming constructs?
Does this also include applications that dump data to cmd.exe will have it show now instead of not as is current?
(Ie Eve Online starts with a console, under windows it will list a bunch of starting information for the game in cmd, under wine the box remains empty unless their is a memory error. The same is the case for several server applications.)
On Tue, Mar 4, 2008 at 9:52 AM, Lei Zhang thestig@google.com wrote:
On Mon, Mar 3, 2008 at 3:38 PM, Ann & Jason Edmeades us@edmeades.me.uk wrote:
Hiya,
Out of interest, what is meant by improving cmd.exe compatibility?
Add support for all the cmd.exe switches and all the dos batch programming constructs?
Out of interest, what is meant by improving cmd.exe compatibility?
Add support for all the cmd.exe switches and all the dos batch programming constructs?
I do track bugzilla for any cmd.exe issues regularly and aside from one which I started work on, I don't know of any other batch issues. I spent quite a bit of time working on cmd.exe compatibility, including adding the newer 'odd' syntax (e.g. %~$PATH:i) and getting it as close to native as possible. Additionally, the 'missing' commands are almost all external applications, not inbuilt to the command shell.
I do know of some differences, but few apps require complex batch. You can download some complex batch which require specific text to come out from specific commands, but if no real app needs them, its not worth persuing yet.
Jason