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
> 2012/4/
On Wed, Apr 11, 2012 at 5:51 PM, BretJ 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
> 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
On Wed, Apr 11, 2012 at 3:31 PM, Bret Johnson wrote:
>> But no, it would almost never use '/' because that is the Directory
>> Separator (or whatever you want to call it). Also, '\' is the quote
>> character for the shell, hence "My\ File\ Name.txt". Also, I think
>> *nix (or at least Linux) can u
2012/4/11, Bret Johnson :
> That was basically my point. *nix has conventions/standards that it uses,
> and so does DOS, and they are not the same. Trying to make one "look like"
> the other, especially with so much history and "freedom" allowed by DOS,
> just won't work.
I would to remind here
> But no, it would almost never use '/' because that is the Directory
> Separator (or whatever you want to call it). Also, '\' is the quote
> character for the shell, hence "My\ File\ Name.txt". Also, I think
> *nix (or at least Linux) can use any character for filenames except
> NUL, i.e. "..." is
2012/4/11, Bret Johnson :
>> 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 pr
Hi,
On Wed, Apr 11, 2012 at 2:00 PM, Bret Johnson wrote:
>> 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.
>
> Proble
> 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
i think it's an excellent idea to get the "/" character as a directory
seperator...
( i t s h o u l d b e a n o p t i o n . )
..
eufdp...@yahoo.com
eufdp...@yahoo.com
eufdp...@yahoo.com
eufdp...@yahoo.com
eu
2012/4/11, Rugxulo :
> Good to know, thanks for the feedback, but ...
>
> a). there is no maintainer for 4DOS
It seems, there's no hope for handling that timer-related issues too soon.
> b). it doesn't compile (easily), and OpenWatcom isn't supported
...it's even worse. O_O
>> 2. Could it be m
2012/4/11, Tom Ehlert :
>> 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
Hi,
On Wed, Apr 11, 2012 at 12:19 PM, Zbigniew 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 stil
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 leng
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 p
15 matches
Mail list logo
