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

systemverilog.maxLineCountIndexing issue #228

Open
hubertdetartas opened this issue Jun 12, 2024 · 1 comment
Open

systemverilog.maxLineCountIndexing issue #228

hubertdetartas opened this issue Jun 12, 2024 · 1 comment

Comments

@hubertdetartas
Copy link

Hi,
I am getting this recurrent warning when I index my verilog/systemverilog files:

The character count of is larger than 5000. Falling back to fast parse. To fully parse this file, please set 'systemverilog.maxLineCountIndexing > 18416 in the systemverilog extension settings.

Yet, when I go to my settings, this variable has been changed to : 100000 both in User and Workspace.
After doing the changes, I closed everything and restarted visual studio code, but I have still the same warning.
( I tried 50000 but it was the same result)

Also, I see on the bottom of the screen the indexing count increasing when I click on a file. I thought the indexing was done
when I load a folder in visual studio code. I understand this takes time, but I can wait for the indexing to be finished.

Thanks and regards
Simon

@joecrop
Copy link
Collaborator

joecrop commented Aug 30, 2024

@hubertdetartas This setting does not track indexed tokens, it tracks individual file size (in the form of line numbers). In this case, it is telling you that a file has 18416 lines, which is bigger than the systemverilog.maxLineCountIndexing setting.

To trigger re-indexing, you can click on the
image
button at the bottom bar of VSCode.

I just tested this, and the setting is working for me in a VS-Code sandbox that has only this extension installed. Fair warning, though, a file that large will almost certainly have a performance impact on VS-Code, so you would want a powerful machine to manage it if you do allow it to be fully indexed.

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

2 participants