Re: parameters - problem with echo

"Arkady V.Belousov" <[email protected]> Wed, 13 Nov 2002 22:28:31 +0300 (MSK)
Newsgroups gmane.os.freedos.devel,gmane.spam.detected
Message-ID <[email protected]>
X-Comment-To: [email protected]

Hi!

13-=EE=CF=D1-2002 13:18 [email protected] ([email protected]) wrote to
[email protected]:

>>      There is reversed question: MS-DOS not removes leading spaces. This=

>> allows this to format output by spaces:
fo> That's why the first line reads:
fo> "It's actually a known bug."

     Bug of whom/which? FreeCOM? Kernel?

fo> What else could I have written?? Maybe a bug fix.

     This will be right position, especially if spaces trimmed by FreeCOM.

fo> And it's also a widely roaming myth that the first character on the
fo> command line is a space: THIS IS NONSENSE!

     So this mean that author of zecho is wrong when uncopnditionally
removes first byte. But this is another question.

fo> That MS COMMAND passes on leading spaces is also a dump decision

     "Dump decision"?! Why? I think sometime this is useful if spaces are
significant characters (as for echo), so this is/was (at least) not wrong
decision.

fo> of that past hacker making the thing, gosh. BUT IT IS A BUG,

     "BUG"?!

fo> BUT I RANGE IT LOW IN THE TO-DO LIST, for various reasons.
fo> If I get provided a bugfix, this stuff might show up soon.