[Re special reg imports into w98]
that is a unicode hex of those strings. i used them, because regedit
can not handle newlines within string values. i modified those zip
packages at
http://jsimlo.sk/notepad/filters.php ...added txt files
with those strings... could you please review them and try to export
them under regedit4? (....i have only the xp's regedit5 available...)
I worked through some quick testings. Not in depth, but enough to provide
a little progress over my previous responses.
The original consolidated reg file that I posted worked fine as a starting
point. Next, to have that multiline syntax description field available in
Ted's interface, I copied into Ted the texts you provided, via Settings >
Filters > Modify. The registry changes stick upon closing. The bad news
is that the export of the resulting key does not come out in a regedit4
compatible .reg file. That newlines problem that you speak of. The file
does not follow the structure that regedit needs. Instead of "valuename=
"value," it has free-floating plain text, ignored by regedit on attempted
import. So, all we can do is enter the description fields for the filters
manually. But that seems ok. If we are adding other various commandline
tools that interest us, we will there too be engaging in the manual steps
of pasting their syntax help into Ted's description field.
As to the filters working, once more fully configured... Yes. That solved
what turned out to be the essential problem I'd had. Not having the syntax
provided in my face for what to enter for the variables.
I tried the grep command. Seemed fine, in essence. Just a couple of minor
issues, such as the linebreaks getting mangled in the output; plus some
non-ascii mystery chars. But I didn't cross-compare with running it straight
from a command window, or do more than a couple of passing tests.
I also tried the Cut command. Instead of rtfm'ing on what that one's about,
I just handed it the simple parameter of --help. The resulting output into
Ted's document windwo was fine.
The one filter that acted strangely was dir. When I'd tried it before,
I'd lift it with "cmd /c dir ..." I have a w2000 command emulator in
my path with that name; this got called up, and all was fine.
Then today, I tried it with setting it to call my w98 default, command.com,
instead. The funky result with command.com is that there is an output window
that says, "Waiting for command to finish .. dir /b" and it hangs there
forever. Forever or until I hit the cancel button.
After hitting the cancel button, then the dir output loads into Ted's
window, acting innocent, as if the whole stuck window incident had never
occurred. I've not the least idea why this behavior.
Btw, I tried it both with /c and /k. The latter launches a second instance
of Ted. But both have that window hanging there until one hits cancel. Odd
bit.
p.s. i have started with the RE version
I hope you will post a link for downloading the RE version. I mean, if
I were to expend my concentrations on configuring my Ted settings to
enable it call various commandline tools for text processing, I'd want the
benefit of being able to do it on real files, not 40k sample-sizers.
