- May
- 3,515
- 5
1/ Ranges
1.1/ Order - Relax the requirement for range options to precede other
options. While this is essentially implemented in V11, it would be nice for
it to be generally applicable
1.2/ Multiple ranges of a given type (e.g., multiple exclusion ranges) -
currently cause errors. The options below would be useful:
1.2.1/ Cumulative ranges - for example, many of my aliases which process
hidden files contain /[!DESCRIPT.ION], disallowing me from adding additional
file exclusions. This concept would also be useful for other ranges, e.g.,
to look for files created within 10 min of either midnight or noon. A new
syntax would be needed, e.g., /+[!*.tmp] to also exclude *.tmp files. The
new syntax would guarantee backward compatibility.
1.2.2/ Overriding range - this would result in handling ranges more like
other options, where generally a second use of an option with different
suboptions overrides earlier use, as is done with /a: and /o:
2/ Extension of the "no junction" type iteration restrictions to all
commands, e.g. FFIND and FOR.
3/ New suboption P for the ordering option /o: - ordering by pathname. I
realize this will delay command completion, but the delay should be less
than that caused by the need to follow the command by an external sort
utility, and in case of FFIND returning file contents, the ability to
provide ordering by filenames including paths would eliminate the need for
very sophisticated and much slower sorting.
4/ Add /U unicode option to SETDOS to make switching between ASCII and
Unicode easier
5/ Add option to SETDOS to force command output case, e.g., /O:n - 0:mixed
case, 1: lower case, 2: upper case. This option could be combined with the
unicode option. The benefit of forcing case would be for output that needs
to be sorted or searched.
--
Steve
1.1/ Order - Relax the requirement for range options to precede other
options. While this is essentially implemented in V11, it would be nice for
it to be generally applicable
1.2/ Multiple ranges of a given type (e.g., multiple exclusion ranges) -
currently cause errors. The options below would be useful:
1.2.1/ Cumulative ranges - for example, many of my aliases which process
hidden files contain /[!DESCRIPT.ION], disallowing me from adding additional
file exclusions. This concept would also be useful for other ranges, e.g.,
to look for files created within 10 min of either midnight or noon. A new
syntax would be needed, e.g., /+[!*.tmp] to also exclude *.tmp files. The
new syntax would guarantee backward compatibility.
1.2.2/ Overriding range - this would result in handling ranges more like
other options, where generally a second use of an option with different
suboptions overrides earlier use, as is done with /a: and /o:
2/ Extension of the "no junction" type iteration restrictions to all
commands, e.g. FFIND and FOR.
3/ New suboption P for the ordering option /o: - ordering by pathname. I
realize this will delay command completion, but the delay should be less
than that caused by the need to follow the command by an external sort
utility, and in case of FFIND returning file contents, the ability to
provide ordering by filenames including paths would eliminate the need for
very sophisticated and much slower sorting.
4/ Add /U unicode option to SETDOS to make switching between ASCII and
Unicode easier
5/ Add option to SETDOS to force command output case, e.g., /O:n - 0:mixed
case, 1: lower case, 2: upper case. This option could be combined with the
unicode option. The benefit of forcing case would be for output that needs
to be sorted or searched.
--
Steve