Re: sed bug?

[Bob Proulx]

Eli Zaretskii wrote:
> Bob Proulx wrote:
> > The MS command interpreter passes the *.txt argument directly to the
> > program the program is expected to expand it.  This is related to a
> > very short limit (IIRC 128 characters or something close to that
> > limit) for command line arguments in MS systems.
> 
> The fact that the MS shell does not expand wildcards has nothing to do
> with the command-line length limit.  Not anymore, anyway: current MS
> shells can handle at least 4K characters, and normally more (32K).

Really?  Wow.  They are moving forward! :-)

> > So.  What does that mean?  It means that when programs are ported to
> > MS the author doing the software port must make a decision.  They need
> > to decide should they include code to expand arguments or not?
> 
> No, they don't: that code is linked in by default.

If so then why didn't Scott's case expand the file globs for him?  On
MS are the quotes included in the command line option arguments too?
That's weird.  But in that case should he try this?

  sed -f x.sed "..\test files\"*.txt

Using backslashes really looks strange to me though.  It looks like a
\t TAB and \" quoted double-qoute.

Bob