| ---Quote---
|| Most of us already have filters (eternal programs) to deal with
|| EOLs, it would be just a simple convenience to be able to do it
|| internally.
| ---End Quote---
| There's no reason a filter would have to be an external (look at
| TEE).
I doubt anyone considers TEE to be a filter. Yes, I am well aware that it
could be in a plug-in (as Vince already offered to do), but some users (not
I) are leary of using plug-ins that are not Microsoft certified as internal
features would be.
| ---Quote---
|| However, TYPE already has the /L, /X and /XS options to change its
|| display formats, and it has few options, thus adding these options
|| would still leave TYPE as one of the simplest commands.
| ---End Quote---
| Two problems with that assertion:
|
| 1) You'd needlessly limit it to only TYPE output, and
|
| 2) TYPE is probably the fourth most complicated command already, as
| it also includes HEAD and TAIL.
I agree with #1, and considered expanding the request to ECHO, TEXT,
HEAD and TAIL. I decided against the expanded request for simplicity, not
being aware of #2. In view of #2 I now make the additional suggestion to add
TYPE's /L, /X and /XS options to HEAD and TAIL.
Furthermore, HEAD/TAIL/TYPE already deal with codeset switching and with
accepting various styles of EOL in the source data (for selecting lines in
HEAD/TAIL, or printing line numbers in TYPE). My request would add to
command parsing the need to dynamically override the default codeset, and to
select the output EOL style. In the data processing portion it would add a
switch to replace the EOL found in the source with the one selected by the
user.
--
Steve