On Fri, 09 Nov 2001 20:22:39 -0400, Glenn McCorkle wrote: > On Thu, 08 Nov 2001 03:11:26 -0400, Clarence Verge wrote:
>> Ahah! That means it IS Insight that ignores the existence of the already >> generated index then ? >> Don't you wish this had come up before your recent improvement to Insight ? >> <G> > Nope. > Insight can't make the decision one way or the other as to > either "ignoring" it or paying attention to it. > (all insight does is to go right ahead and do what core tells it to do) > Core makes the determination as to whether or not to have > insight create the index file. > 1) file exists..... display it. > 2) file does not exist..... tell insight to create it. > 3) file exists but for some unknown reason core did not see it.... tell > insight to create it > (therefore overwriting the one that was already there) > Maybe it's a "full-cache". That is illogical, Mr Spock. If I hit "I" (after creating an index), a new index is NEVER created. If I select a message and view it, thereby getting an "INDEX" button, and hit that button, a new index is ALWAYS created. If instead I had hit "I" there will be no new index. If instead I hit "ESC" (for back) SOMETIMES a new index is created. Seems to me the cache is just as full in all the above conditions. ;-) Also seems to me that core is the thing interpreting both hotkey "I" and the button argument file://inbox.dgi. Seems they do not resolve to the same thing. i.e. ok, Insight re-creates the index when core exercises the line in mime.cfg. That's fair. But shouldn't core check to see if the index exists first ? It seems do that on the "I" hotkey. :) - Clarence Verge - Back to using Arachne V1.62 ....
