15 Nov
2016
15 Nov
'16
3:16 a.m.
On 9 Nov 2016, at 4:41, Carpii UK wrote:
I just had this happen again, but as Graham suggested, it seems to be due to my custom TM build.
'ps aux | grep textmate -i' confirmed both instances were from different paths.
I'm guessing after updating, TextMate just asks OSX to launch TextMate without an absolute path? So it seems to pick up my custom build, which is in home/build and hence in my $PATH
It does use an absolute path, but via x-man-page://1/open so in theory this command could use the absolute path to obtain the bundle identifier and then use that, but this would be strange.
I’ve added a note about this, so I may do some testing in the future.