Re: [Freedos-user] ...and about FreeCon this time
The problem is that there's a limit to what one can ask to a FreeDOS tool: if it breaks MS-DOS compatibility. If DATE/T is taken as an option by MS-DOS COMMAND.COM, so should FreeCOM. You don't know how many batch programs could stop working with that change. Aitor 2012/4/11 Zbigniew zbigniew2...@gmail.com 2012/4/11, Tom Ehlert t...@drivesnapshot.de: 2. Could it be made to use slash as separator in pathnames, just like 4DOS allows both slash and backslash? Every Linux/BSD user will appreciate that. whats supposed to happen on C:DATE/T /T is probably an option DATE\T probably some program in subdirectory DATE shall be executed My personal vote would be for bringing a little more order, I mean: to suppress recognizing such input as option, if slash is directly after some string of characters - in such case path recognition should be assumed. -- regards, Zbigniew -- Better than sec? Nothing is better than sec when it comes to monitoring Big Data applications. Try Boundary one-second resolution app monitoring today. Free. http://p.sf.net/sfu/Boundary-dev2dev ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user -- Master Java SE, Java EE, Eclipse, Spring, Hibernate, JavaScript, jQuery and much more. Keep your Java skills current with LearnJavaNow - 200+ hours of step-by-step video tutorials by Java experts. SALE $49.99 this month only -- learn more at: http://p.sf.net/sfu/learnmore_122612 ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
[Freedos-user] ...and about FreeCon this time
1. Its history records empty lines (e.g. when one hits Enter) - I think, there's no need for that. It should record a line only in case, when after eliminating blank characters (CR, LF, space...) from both ends, its length still remains 0. 2. Could it be made to use slash as separator in pathnames, just like 4DOS allows both slash and backslash? Every Linux/BSD user will appreciate that. P.S. On the contrary: to 4DOS could be added line completion, which works nicely in FreeCon. -- Z. -- Better than sec? Nothing is better than sec when it comes to monitoring Big Data applications. Try Boundary one-second resolution app monitoring today. Free. http://p.sf.net/sfu/Boundary-dev2dev ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] ...and about FreeCon this time
Hallo Herr Zbigniew, am 11. April 2012 um 19:19 schrieben Sie: 1. Its history records empty lines (e.g. when one hits Enter) - I think, there's no need for that. It should record a line only in case, when after eliminating blank characters (CR, LF, space...) from both ends, its length still remains 0. right. 2. Could it be made to use slash as separator in pathnames, just like 4DOS allows both slash and backslash? Every Linux/BSD user will appreciate that. whats supposed to happen on C:DATE/T /T is probably an option DATE\T probably some program in subdirectory DATE shall be executed P.S. On the contrary: to 4DOS could be added line completion, which works nicely in FreeCon. nobody's perfect ;) Mit freundlichen Grüßen/Kind regards Tom Ehlert +49-241-79886 -- Better than sec? Nothing is better than sec when it comes to monitoring Big Data applications. Try Boundary one-second resolution app monitoring today. Free. http://p.sf.net/sfu/Boundary-dev2dev ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] ...and about FreeCon this time
Hi, On Wed, Apr 11, 2012 at 12:19 PM, Zbigniew zbigniew2...@gmail.com wrote: 1. Its history records empty lines (e.g. when one hits Enter) - I think, there's no need for that. It should record a line only in case, when after eliminating blank characters (CR, LF, space...) from both ends, its length still remains 0. Good to know, thanks for the feedback, but ... a). there is no maintainer for 4DOS b). it doesn't compile (easily), and OpenWatcom isn't supported 2. Could it be made to use slash as separator in pathnames, just like 4DOS allows both slash and backslash? Every Linux/BSD user will appreciate that. Just use DJGPP and/or its (old) GNU Bash 2.05b. :-) P.S. On the contrary: to 4DOS could be added line completion, which works nicely in FreeCon. Doesn't it already have it? Up-arrow or F9 should do something, but I don't regularly use 4DOS, so I can't remember exactly. You'll have to be more specific (or search the online help). -- Better than sec? Nothing is better than sec when it comes to monitoring Big Data applications. Try Boundary one-second resolution app monitoring today. Free. http://p.sf.net/sfu/Boundary-dev2dev ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] ...and about FreeCon this time
2012/4/11, Tom Ehlert t...@drivesnapshot.de: 2. Could it be made to use slash as separator in pathnames, just like 4DOS allows both slash and backslash? Every Linux/BSD user will appreciate that. whats supposed to happen on C:DATE/T /T is probably an option DATE\T probably some program in subdirectory DATE shall be executed My personal vote would be for bringing a little more order, I mean: to suppress recognizing such input as option, if slash is directly after some string of characters - in such case path recognition should be assumed. -- regards, Zbigniew -- Better than sec? Nothing is better than sec when it comes to monitoring Big Data applications. Try Boundary one-second resolution app monitoring today. Free. http://p.sf.net/sfu/Boundary-dev2dev ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] ...and about FreeCon this time
My personal vote would be for bringing a little more order, I mean: to suppress recognizing such input as option, if slash is directly after some string of characters - in such case path recognition should be assumed. Problem with that is that I've seen programs that _require_ the options to beginning immediately after the program name. E.g.: DATE /T returns an error, while DATE/Tworks like it should Theoretically, either should be OK, but that simply isn't always the case. Basically, what you're suggesting is simply not possible in the general case, and gets even uglier when LFN's are involved. BTW, your suggestion could go the other way too: why can't *nix change to accept either - or / (or nothing, like many DOS programs allow) to start an option, and either / or \ for a path separator? -- Better than sec? Nothing is better than sec when it comes to monitoring Big Data applications. Try Boundary one-second resolution app monitoring today. Free. http://p.sf.net/sfu/Boundary-dev2dev ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] ...and about FreeCon this time
Some DOS *apps* cared and choked on it, so I wrote Korn shell alias wrappers to reset the option delimiter char to / before running them, and set it back to - when they exited. Like I said, this is why it won't work in the _general_ case. There are situations and programs where it can work, and others where it can't. You had to write temporary scripts to skirt around the issue for certain applications, which was precisely my point. You are correct that it can be _made_ to work, but it takes customization for individual programs, and even knowledge on behalf of the user to make sure they think about what they are doing. -- View this message in context: http://old.nabble.com/...and-about-FreeCon-this-time-tp33670275p33671896.html Sent from the FreeDOS - User mailing list archive at Nabble.com. -- Better than sec? Nothing is better than sec when it comes to monitoring Big Data applications. Try Boundary one-second resolution app monitoring today. Free. http://p.sf.net/sfu/Boundary-dev2dev ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] ...and about FreeCon this time
On Wed, Apr 11, 2012 at 5:51 PM, BretJ bretj...@juno.com wrote: Some DOS *apps* cared and choked on it, so I wrote Korn shell alias wrappers to reset the option delimiter char to / before running them, and set it back to - when they exited. Like I said, this is why it won't work in the _general_ case. There are situations and programs where it can work, and others where it can't. You had to write temporary scripts to skirt around the issue for certain applications, which was precisely my point. You are correct that it can be _made_ to work, but it takes customization for individual programs, and even knowledge on behalf of the user to make sure they think about what they are doing. But my experience has been that that's pretty much always the case, anywhere. I personally felt the DOS apps that needed that treatment were not programmed as well as might have been: if DOS would let you use either character, the program should have as well, rather than having hard-coded ideas of what was what. But *most* things *did* work. There were only a handful pf programs that needed that treatment, so it wasn't a big imposition to write some wrapper functions. __ Dennis https://plus.google.com/u/0/105128793974319004519 -- Better than sec? Nothing is better than sec when it comes to monitoring Big Data applications. Try Boundary one-second resolution app monitoring today. Free. http://p.sf.net/sfu/Boundary-dev2dev ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
