From: "Carlo Hogeveen" 
There is a bug allright, but an other one than described :-)
A repeatfind() repeats the previous find() without the "g" option
(if it was specified).
Therefore after a find() in a line or block or file 
with option "c" or "l" or "" the repeatfind() stops 
at the end of the line or block or file.
Most people tend to agree upon where the end of a line or block 
or file is located (and stays located!).
However the "a" option tells TSE to search in the ring of files.
Where is the end of a ring?
The "real" bug is, that find() option "ga" starts searching 
from the begin of the current file, as if that is the
begin of the ring!
It would be shocking, if it wasn't so handy :-)
Carlo
----------
> From: David Marcus 
> To: tsepro@semware.com
> Subject: Re: Possible Bug in Find()
> Date: donderdag 17 april 1997 1:11
> 
> cfalsone@athens.bitwise.net wrote on Wed, 16 Apr 1997 14:51:33 +0000:
> 
> ! I belive I may have found a bug in Find() when going across multiple 
> ! files. In order to see this bug do the following:
> ! 
> ! 1. Create 3 files (e32 f1 f2 f3). 
> ! 2. Enter the word "hello" in each file.
> ! 3. Now do a find on "ll". Specify "ga" as the find options.
> ! 4. Once it finds the first one, keep doing RepeatFind() 
> !    (Find/Again).
> ! 
> ! Notice how it keeps cycling thru all the files. IMHO, I find this to
> ! be a bug. Once it gets back to the first file, shouldn't it display a
> ! message that it can't find anymore? Am I whacked or what?
> 
> Or what .
> Each find is conducted independently. Each repeat find is also
> conducted independently except for picking up string and options from
> the last find(). Because of the independence, each find simply ...
> finds.
> 
> :)avid
---
---------------