How to make Intellisense metadata persistent in Visual Studio Code
up vote
0
down vote
favorite
I'm using Visual Studio Code for C/C++ development (and I'm very happy with it).
However, I'm working on huge C/C++ projects, which makes Intellisense work for a long time before getting all the files, symbols, etc.
The problem is that the result of this long process seems to be non-persistent when I quit and come back to my project folder, Intellisense starts everything again, and this is not convenient to wait for 15 minutes before being able to go to a symbol definition.
Is it possible to force Intellisense parsed results to be persistent? Like allowing it to store metadata in .vscode directory of my project?
I think Intellisense stores everything in my home directory in a folder which must get cleaned periodically or when growing to a certain size (directory ~/.config/Code is 3 GB big so I guess it's there).
Alternatively can I increase the size limit of this folder?
metadata visual-studio-code intellisense
asked Nov 22 at 9:43
Benjamin Barrois
1112
add a comment |
up vote
0
down vote
favorite
I'm using Visual Studio Code for C/C++ development (and I'm very happy with it).
However, I'm working on huge C/C++ projects, which makes Intellisense work for a long time before getting all the files, symbols, etc.
The problem is that the result of this long process seems to be non-persistent when I quit and come back to my project folder, Intellisense starts everything again, and this is not convenient to wait for 15 minutes before being able to go to a symbol definition.
Is it possible to force Intellisense parsed results to be persistent? Like allowing it to store metadata in .vscode directory of my project?
I think Intellisense stores everything in my home directory in a folder which must get cleaned periodically or when growing to a certain size (directory ~/.config/Code is 3 GB big so I guess it's there).
Alternatively can I increase the size limit of this folder?
metadata visual-studio-code intellisense
asked Nov 22 at 9:43
Benjamin Barrois
1112
Many times this is caused by an installed extension.
– harrymc
Nov 22 at 10:57
add a comment |
up vote
0
down vote
favorite
up vote
0
down vote
favorite
I'm using Visual Studio Code for C/C++ development (and I'm very happy with it).
However, I'm working on huge C/C++ projects, which makes Intellisense work for a long time before getting all the files, symbols, etc.
The problem is that the result of this long process seems to be non-persistent when I quit and come back to my project folder, Intellisense starts everything again, and this is not convenient to wait for 15 minutes before being able to go to a symbol definition.
Is it possible to force Intellisense parsed results to be persistent? Like allowing it to store metadata in .vscode directory of my project?
I think Intellisense stores everything in my home directory in a folder which must get cleaned periodically or when growing to a certain size (directory ~/.config/Code is 3 GB big so I guess it's there).
Alternatively can I increase the size limit of this folder?
metadata visual-studio-code intellisense
asked Nov 22 at 9:43
Benjamin Barrois
1112
I'm using Visual Studio Code for C/C++ development (and I'm very happy with it).
However, I'm working on huge C/C++ projects, which makes Intellisense work for a long time before getting all the files, symbols, etc.
The problem is that the result of this long process seems to be non-persistent when I quit and come back to my project folder, Intellisense starts everything again, and this is not convenient to wait for 15 minutes before being able to go to a symbol definition.
Is it possible to force Intellisense parsed results to be persistent? Like allowing it to store metadata in .vscode directory of my project?
I think Intellisense stores everything in my home directory in a folder which must get cleaned periodically or when growing to a certain size (directory ~/.config/Code is 3 GB big so I guess it's there).
Alternatively can I increase the size limit of this folder?
metadata visual-studio-code intellisense
metadata visual-studio-code intellisense
asked Nov 22 at 9:43
Benjamin Barrois
1112
asked Nov 22 at 9:43
Benjamin Barrois
1112
asked Nov 22 at 9:43
Benjamin Barrois
1112
asked Nov 22 at 9:43
Benjamin Barrois
1112
asked Nov 22 at 9:43
Benjamin Barrois
1112
1112
Many times this is caused by an installed extension.
– harrymc
Nov 22 at 10:57
add a comment |
Many times this is caused by an installed extension.
– harrymc
Nov 22 at 10:57
Many times this is caused by an installed extension.
– harrymc
Nov 22 at 10:57
Many times this is caused by an installed extension.
– harrymc
Nov 22 at 10:57
add a comment |
active
oldest
votes
active
oldest
votes
active
oldest
votes
active
oldest
votes
active
oldest
votes
Thanks for contributing an answer to Super User!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Some of your past answers have not been well-received, and you're in danger of being blocked from answering.
Please pay close attention to the following guidance:
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f1377523%2fhow-to-make-intellisense-metadata-persistent-in-visual-studio-code%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Many times this is caused by an installed extension.
– harrymc
Nov 22 at 10:57