Has the ranking code for ⌘T changed recently? Im on v2.0-alpha.9561
I've noticed recently when I try top quick open "view.php" its instead ranking "review.php" at the top, with "view.php" 2nd.
There are no files open when I attempt this, although Ive been working on review.php the past few days, so I wonder if theres some meta data which boosts the rank according to recent usage?
Thanks
On 11 Oct 2014, at 0:42, Carpii UK wrote:
Has the ranking code for ⌘T changed recently? Im on v2.0-alpha.9561
It has not.
I've noticed recently when I try top quick open "view.php" its instead ranking "review.php" at the top, with "view.php" 2nd.
There are no files open when I attempt this, although Ive been working on review.php the past few days, so I wonder if theres some meta data which boosts the rank according to recent usage?
It remembers “corrections” you make, you can see what it has stored via:
defaults read com.macromates.TextMate.preview
If you select “view.php” does it then not show this as top result in subsequent use?
It remembers “corrections” you make, you can see what it has stored via:
defaults read com.macromates.TextMate.preview
Thanks, thats useful
If you select “view.php” does it then not show this as top result in subsequent use?
It doesn't do it this morning. But yesterday I would close all files, then try to quick open "view" and it would rank review.php higher.
I *think* it has since recorded a correction for this too, so "view" now refers to view.php again.
When I look at my corrections there is a now one for "view" => "view.php" But also one for "view" => "review.php"
Is it guaranteed to give precedence to the correction most recently set? I wonder if maybe it should just prune the array so the "short" alias is always unique?
On 11 October 2014 13:44, Allan Odgaard mailinglist@textmate.org wrote:
On 11 Oct 2014, at 0:42, Carpii UK wrote:
I've noticed recently when I try top quick open "view.php" its instead
ranking "review.php" at the top, with "view.php" 2nd.
I just had this occur again, but I've a better understanding of it now...
Since I use ⌘T exclusively, I occasionally attempt to quick open files which are already open in a tab
At this point, because TM already has view.php open, it ranks view.php lower, leaving review.php as the top hit When I hit enter on that (which I do because I type quicker than I think), its then recording a new correction for "view" => review.php
I can't think of a workaround for this. Clearly TM is behaving as designed and its my workflow that's at fault, but at the same time I'd prefer CMD-T to behave identically regardless of the files I already have open
Is there a way to disable the saving of 'corrections' altogether?
Or I guess even better would be a way to disable de-ranking of files which are already open.
On 12 Oct 2014, at 0:31, Carpii UK wrote:
Is there a way to disable the saving of 'corrections' altogether?
Or I guess even better would be a way to disable de-ranking of files which are already open.
Not currently possible. The main reason for deranking is actually the case when there is no filter string (here we LRU-sort the files so ↩ gets us to previous file, so we do not want current file in this list).
But not having current file as “noise” is sometimes an advantage. I’ll add a note about this.
On 12 Oct 2014, at 9:56, Allan Odgaard wrote:
On 12 Oct 2014, at 0:31, Carpii UK wrote:
Is there a way to disable the saving of 'corrections' altogether?
Or I guess even better would be a way to disable de-ranking of files which are already open.
Not currently possible […]
In beta 5.4 the current document is no longer placed last, when there is a filter string.
Also, the filter string will now be applied to the full path, even when there is no slash, though matches that only touch the document name are ranked higher than those which touch the entire path.
-
Allan Odgaard -
Carpii UK