Hi - For the last week or so, the contents of the Go to Symbol window have been totally scrambled for me in all the languages I’ve tried. Sometimes (After restarting TM) the Go to Symbol window contains the entire file on one line without linebreaks. Other times there are many lines, each with several lines worth of source in them, but no clear relation to any of the function definitions in the file.
I suspect this is a corrupted settings file somewhere; I’ve got my TM settings synced to Dropbox so when two different machines are open at the same time a number of things go screwy. I wasn’t sure how to start debugging this one though short of going spelunking in the source.
Is anybody familiar enough with the inner workings of this command to point me to what settings might be corrupted?
Cheers, Evan
Example:
In the C code at the bottom, I would usually expect to see 4 lines in the list of symbols:
``` #include <stdio.h> void other(); int main(){ void other(){ ```
Instead, I get the entire contents of the file on one line: ```#include <stdio.h>void other();int main(){printf("line 1 after 'main' symbol\n");printf("line 2 after 'main' symbol\n");other();}void other(){printf("line 1 after 'other' symbol\n");printf("line 2 after 'other' symbol\n");}```
Source file: ``` #include <stdio.h>
void other();
int main(){ printf("line 1 after 'main' symbol\n"); printf("line 2 after 'main' symbol\n"); other(); }
void other(){ printf("line 1 after 'other' symbol\n"); printf("line 2 after 'other' symbol\n"); } ```
On 19 May 2016, at 22:38, Evan Jones wrote:
Hi - For the last week or so, the contents of the Go to Symbol window have been totally scrambled for me in all the languages I’ve tried. Sometimes (After restarting TM) the Go to Symbol window contains the entire file on one line without linebreaks. Other times there are many lines, each with several lines worth of source in them, but no clear relation to any of the function definitions in the file.
I suspect this is a corrupted settings file somewhere […]
The default setting to include symbols in the list is in the Source bundle, so you can check if you have customizations done for this bundle.
The setting in question is `showInSymbolList` so if you use ⌃⌘T (Bundles → Select Bundle Item…) then you can switch to Settings and enter this setting to see where it might be set.
With caret on a function name in C++ then there should be just one match for this.
Thanks so much, Allan. I’d installed a bundle (Javascript Next ) that seemed to be trampling on the settings from the Source bundle. Your tip let me identify that, deactivate the competing settings, and everything looks good now. Cheers!
On May 20, 2016, at 10:20 AM, Allan Odgaard mailinglist@textmate.org wrote:
On 19 May 2016, at 22:38, Evan Jones wrote:
Hi - For the last week or so, the contents of the Go to Symbol window have been totally scrambled for me in all the languages I’ve tried. Sometimes (After restarting TM) the Go to Symbol window contains the entire file on one line without linebreaks. Other times there are many lines, each with several lines worth of source in them, but no clear relation to any of the function definitions in the file.
I suspect this is a corrupted settings file somewhere […]
The default setting to include symbols in the list is in the Source bundle, so you can check if you have customizations done for this bundle.
The setting in question is `showInSymbolList` so if you use ⌃⌘T (Bundles → Select Bundle Item…) then you can switch to Settings and enter this setting to see where it might be set.
With caret on a function name in C++ then there should be just one match for this.
<PastedImage.png> _______________________________________________ textmate mailing list textmate@lists.macromates.com http://lists.macromates.com/listinfo/textmate
Hi Evan,
On 20 May 2016 at 20:24, Evan Jones evan_t_jones@mac.com wrote:
Thanks so much, Allan. I’d installed a bundle (Javascript Next ) that seemed to be trampling on the settings from the Source bundle.
FYI, I have a PR open to turn JavaScript Next into a tmbundle natively. In case wanna try it:
git clone -b tmbundle https://github.com/mkhl/JavaScriptNext.tmLanguage.git "$HOME/Library/Application Support/Avian/Bundles/JavaScriptNext.tmbundle"
And FWIW, this bug doesn’t seem to have been removed upstream at some point.
Cheers, Martin
FYI, I have a PR open to turn JavaScript Next into a tmbundle natively. In case wanna try it: Btw, I found myself unsatisfied by JavaScript Next, so I made my own bundle that supports all the Babel features (ES6, 7, JSX) . Basically I've just converted the https://github.com/gandm/language-babel package to a TM bundle and removed unneeded captured spaces in the regex rules. I've been using it for the last month or so with no issues so far. https://github.com/Igor10k/JavaScript-Babel.tmbundle
On 24.05.2016, at 14:31 , Igor K me@igorkozlov.me wrote:
Btw, I found myself unsatisfied by JavaScript Next, so I made my own bundle that supports all the Babel features (ES6, 7, JSX). Basically I've just converted the https://github.com/gandm/language-babel package to a TM bundle and removed unneeded captured spaces in the regex rules.
Can you tell what didn’t work for you?
I’m using JavascriptNext without issues…
fabian
Can you tell what didn’t work for you? First and foremost JSX syntax is not supported. Besides that the syntax highlighting relies too much on non-default scope selectors and that means either use one of the two provided with the bundle themes or tweak and update any other theme you choose.