search

StarlaneStudios / vscode-comment-anchors

⚓A Visual Studio Code extension that adds support for comment anchors 🔭
https://marketplace.visualstudio.com/items?itemName=ExodiusStudios.comment-anchors
MIT License
205 stars 32 forks source link

No comment anchors detected #219

Open Alexey-B opened 7 months ago

Alexey-B commented 7 months ago

Describe the bug After some kind of update in 2024, all the anchors disappeared (there were enough of them according to the project). The new ones don't applied either.

To Reproduce No idea

Expected behavior The anchors is appeared.

NoAnchors

Zodsmar commented 7 months ago

Describe the bug After some kind of update in 2024, all the anchors disappeared (there were enough of them according to the project). The new ones don't applied either.

To Reproduce No idea

Expected behavior The anchors is appeared.

NoAnchors

Have you changed your config file in any way? Have you tried comment anchors on other projects as well?

Try uninstalling and reinstalling the plugin as well

Alexey-B commented 7 months ago

I didn't change config file and I tried deleting and reinstalling this extension. No success. I even created a new workspace and disabled all extensions except Comment Anchors. The comments are still not picked up. Again - in 2023 everything worked with the same settings.

Alexey-B commented 6 months ago

I checked on Windows 8.1, everything works there. Looks like a problem in Windows 11.

Alexey-B commented 6 months ago

It’s also interesting that autofill suggests, but again doesn’t see anything. 123 456

Zodsmar commented 6 months ago

I checked on Windows 8.1, everything works there. Looks like a problem in Windows 11.

I've run some tests on my end and I can't seem to reproduce the issue at all. I've tried different environments and different languages everything seems to work.

image

I am running Windows 11 as well. Is there any other information you can provide? Can you show your settings.json and also if you made any modifications delete them and try just the default settings. (Deleting the plugin doesn't remove any settings.json that you added so if something is incorrect there it will exist on deletion and reinstalls)

Alexey-B commented 6 months ago

Hi @Zodsmar ! I have attached my simplest project, there is essentially nothing in it, no settings. I checked again (Windows 11): version v.1.10.4 is still not working. But when I rolled back to version 1.10.3, everything miraculously appeared (screen). Test1.zip v 1 10 3

Zodsmar commented 6 months ago

Hi @Zodsmar ! I have attached my simplest project, there is essentially nothing in it, no settings. I checked again (Windows 11): version v.1.10.4 is still not working. But when I rolled back to version 1.10.3, everything miraculously appeared (screen). Test1.zip v 1 10 3

image

Yeah I have no idea. It works perfectly for me. If anyone else has any ideas I'm all ears but if I can't reproduce it, I'm not sure how to even go about "fixing" it

redpwilliams commented 5 months ago

I can attest to what @Alexey-B is saying. I'm sure I'm just now noticing this issue although the update to 1.10.4 happened 2 months ago. Can confirm that downgrading to 1.10.3 solves the issue. I hope in the near future I'll be able to fork this and work on the issue.

Zodsmar commented 5 months ago

be able to

If you do fork it and get the issue in a dev environment please let me know cause I have tried so many things and just can't reproduce it at all

redpwilliams commented 5 months ago

@Zodsmar Now I'm as lost as you. I ran the extension locally at the latest version 1.14.0 and in a clean environment, this feature of the extension worked fine. Contrasted to before where I had to downgrade to 1.13.0 to have a working feature. I tried to do a git bisect to find where the bug was introduced, but in each commit from the release of 1.13.0 to 1.14.0, I saw no issues with the feature. To make things more confusing (for me, at least), I'm running 1.14.0 in my normal environment and the extension works fine now. I don't know what changed between today and a few days ago, as my other extensions, settings, and vscode version have stayed the same. My windows machine's version has not changed since mid February. I'd love to know if the problem has been resolved for you, @Alexey-B.

macjuul commented 5 months ago

Really strange issue as I personally have not run into any problems either, so I'm unsure how it could be fixed. If anyone does find a cause or a possible fix I'll gladly incorporate it and release a new version of the extension

Alexey-B commented 5 months ago

Everything is still the same for me and I still don’t understand the reason. In version 1.10.4 (something happened to the version numbering?) there are no anchors, in version 1.10.3 there are.

aderchox commented 2 weeks ago

I have an issue and I'm not sure if it's related here. My Comment Anchors in the activity bar is showing "Workspace disabled" and nothing else, ie, no "File Anchors" the way I'd expected. I've disabled workspace scans myself manually (using the related CA config), because the workspace has so many files in it and scanning all of them leads to a long list, which is difficult to find the current file in. (Maybe I'm doing things wrong? or missing some jumping-to-current-file functionality? IDK.) So I disabled workspace scans to get File Anchors the way it's shown in the pictures in the README and posted by others in issues. So how do I get the File Anchors to work for me? Also, if it's not possible in workspaces to have file anchors, then 1. Please mention this limitation in the README. 2. How do I jump to the current file in the scan result tree? Thanks in advance.