|
Post by Robert on Aug 17, 2023 9:09:40 GMT -5
Hi George,
As part of the recent LOCATE issues, I tried using LOCATE in FM. It doesn't seem to work right. When I say LOC ABC (and the files are in name order) and there are a bunch of files starting with ABC, it seems to do this:
1. Find first file with prefix ABC
2. Press F5 = RLOCFIND
3. FM display is repositioned randomly, no "ABC" file found, no message either
4. Press F5 again. "Bottom of list reached".
FM LOC doesn't seem to really work at all.
I thought I would use FM FIND instead. This command seems to have been added as an afterthought. I didn't even know you could do FIND in FM until I looked it up.
All you can do with it is find an exact match of a full file name. Since I can scroll through the list, and now have a scroll bar (thanks BTW), I am not sure that FM FIND in its current form is even needed any more.
Maybe if I could use a file pattern (or, RegEx?) to find file names, it would be helpful. Or even X / NX using a pattern/RegEx, kind of like you can do in Edit. I found myself wanting to say FIND ABC* or FIND "ABC*" but no.
Yes, addressing any of this is another big PITN (or other acronym, your choice). Maybe a back-burner item, if there's any room on the burner.
R
|
|
|
Post by George on Aug 18, 2023 9:14:06 GMT -5
Robert: Again, FM commands, even those with the same name as Edit commands are NOT THE SAME. The Help file reminds you of that.
I know you think they should be the same for consistency, but that's another whole project.
FIND/RFIND/RLOCFIND work properly and search from the top screen line downward.
LOCATE does the same, but there is no RLOC command. If you use RLOCFIND, it will simply become an RFIND (which is supported). That's why your RLOCFIND after a LOC seemed to be random.
The only oddity I noticed is that LOC puts the found line on line 2 and FIND puts the found line on line 1.
George
|
|
|
Post by Robert on Aug 18, 2023 13:34:28 GMT -5
I think part of my confusion is that the Help seems to suggest that the FIND argument is a whole string, as if I have to search for a whole file name. I just tested this, and I see now that it's doing a scan to find the string anywhere in the file name, and then RLOCFIND is then 'finding' that substring anywhere in subsequent files, just like a plain old RFIND.
So, to get what I need, all I have to do is FIND and then F5.
Was clear as mud, now the mud is a little less murky.
And do I think everything should be consistent? Of course; I have consistently said so :-))
But time is money, and you can't do everything. Got it.
Thanks for clearing this up.
R
|
|