Two bugs?

[Harry Binswanger hb@xxxxxxxx]

I seem to have found two more bugs in XyDOS 4.018:
1. I recently reported on se/t being unreliable but now I have a problem
with se/f.
If the search string begins at the top of the file, se/f will not find it
(though se will).

E.g., if your file begins "This is a test"
and you move (manually or under program control) to the top of the file,
the following won't find a hit:
     se/f /This/

But this will:
    se /This/

What other se switches have problems?
2. Can one of the gurus tell me why this simple search program doesn't find
the string when run by hitting  while having "run test.pgm" on the
command line, but it does find the string when the cursor is placed at the
top of the file and then "run test. pgm" is eXeCuted (e.g., by hitting F9)???

≪sv01,  ;*; There's a cr-lf after that comma, which usually works fine in XPL
≫BX se /issue.≪pv01≫≪pv01≫/Q2 ≪ex≫

The text in the file it's run against is between the lines:
_______________________________
Blah, blah, blah 
In any case, I know of one place where she briefly addressed the issue.

Blah, blah, blah. 
______________________
There are two cr-lfs after "issue." And the same program works as expected
if you go to the start of the text and eXeCute it with F9. But it doesn't
find it if run while cursor is on the command-line. And, yes, I've made
sure that the cursor position was at the top of file before I went to the
command line.
But wait, there's more . . . I can successfully run it if it looks for only
one newline after "issue." I.e., the following works whichever way it's
executed:

≪sv01,    there's a newline after that comma, which usually works fine
≫BX se /issue.≪pv01≫/Q2 ≪ex≫
Not only does this work, but it leaves the cursor where you think it
would--i.e., on the blank line.
I use the workaround of putting newline characters directly into the
XPL--i.e.:

BX se /issue.[][]/Q2

where the little boxes are the reverse-video arrows.
I like this form of programming better, and my thanks to Robert and Carl
for having this in xywwweb.u2 from which I learned it, but I'd like to know
what's going on here to prevent other errors and errors in my older
programs which are coded the old way.


Harry Binswanger
hb@xxxxxxxx