Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Randomly stops working #35

Closed
gmiwoj opened this issue Feb 21, 2018 · 6 comments
Closed

Randomly stops working #35

gmiwoj opened this issue Feb 21, 2018 · 6 comments

Comments

@gmiwoj
Copy link

gmiwoj commented Feb 21, 2018

Sometimes it works, then it stops working for no reason and it stays like this, only way i to get it back is to keep reloading, disabling and enabling shit, until it eventually pops back again when it feels like it.

this is my code from user settings

    "better-comments.multilineComments": true, 
    "better-comments.tags": [
        {
            "tag": "!",
            "color": "#FF2D00",
            "strikethrough": false
        },
        {
            "tag": "?",
            "color": "#3498DB",
            "strikethrough": false
        },
        {
            "tag": "//",
            "color": "#474747",
            "strikethrough": true
        },
        {
            "tag": "todo",
            "color": "#FF8C00",
            "strikethrough": false
        },
        {
            "tag": "*",
            "color": "#98C379",
            "strikethrough": false
        }
    ],
@aaron-bond
Copy link
Owner

Hmm, someone raised a similar issue before but I couldn't repro.

Can you tell me:
Is it a multi folder workspace?
What languages are you working with?

@BennyHarv3
Copy link

I'm also experiencing this issue with Groovy files, both with and without a workspace. Same configuration, and both with and without folders (e.g., just a top-level folder named test.groovy doesn't work).

@nickprivalov
Copy link

I think I had something similar happen to me just now. I'm working on Pebble SDK C files, with lots of Better Comments tags being used, and at some points it seemed like the editor was failing to properly discern what lines were supposed to be changed in color or not. It would seem to make certain sections of the code (by line) render in the incorrect color.

I had some other files open in the same window but reside in a folder in the workspace root. Moving them to the same folder, the workspace root, solved the issues.

@aaron-bond
Copy link
Owner

Hey thanks for the info. Were the files quite large?

To confirm: having files open in the editor from outside your workspace root and moving to ones inside seemed to cause issues?

@nickprivalov
Copy link

The one that was in the workspace root ('main.c') is fairly large sized, I think maybe ~150 lines, while the one that was in the folder ('main_old.c') is over 400 lines. I'm rewriting a Pebble watch app manually to make the code cleaner, less redundant, etc., and I have both files open at the same time in two panes, in the same VSC window.

The issue occurred when 'main.c' was in the workspace root folder, and 'main_old.c' was in a folder named 'old' in the workspace root. Moving the files in the 'old' folder to the workspace root solved the problem.

Very interesting behavior, but figured I'd share it because it seems to be a rare case.

@aaron-bond
Copy link
Owner

Thanks for the suggestions here @nickprivalov - mentioning the two open files at once was enough to get me onto the right track to chase down the bug. That one's been giving me the run around for a while now, so thanks :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants