Closed dandante closed 11 years ago
I agree. This bug really bites, totally ruins my workflow. It went away when I reinstalled the R bundle but today just magically reappeared. Desperately needs a permanent fix.
Textmate 1.5.11 OS X 10.7.4
Thanks Mike
Note: This command has been disabled in 2.0, this commit disables it in 1.x as well. Make sure you are using the 1.x branch:
If there is no executable called 'R' in my PATH shell variable (as defined in TextMate/Preferences/Advanced/Shell Variables), if I am editing a .R file and I type:
foo(
TextMate will hang. It's trying to look up the function definition for foo() but it can't find an R in its path.
Similarly if there happens to be an executable called R in the path but it's not the "real" R, TextMate will hang when I type what it thinks is a function invocation.
IMO this is a bug. I am able to edit R files with syntax highlighting, etc., and things should not crash when I type in a possible function name. I should not be required to have R installed and in my path.
If you are wondering why I don't have an R binary in my path, it's because I work with different versions of R and when I invoke R I want to be sure which version I am running, so I have aliases for R212, R213, etc. I know that other members of the R development community do the same.
TextMate 1.5.10 (1623), Mac OS 10.6.5.
Thanks Dan