Is there a way to disable the "To enable project-wide JavaScript/TypeScript language features, exclude large folders with source files that you do not work on." warning as it is displayed on each opening of files? I have configured jsconfig.json excluding folders such as node_moduels, but my source files are in the range of thousands.
I couldnt find such option in the preferences so I guess it is a typescript option? Im using vscode 1.14.1 and ts 2.4.1
As answered in Github use this glob pattern
**/some_dir_like_node_modules/*
or it wont be detected and vscode will look into it.
Related
I'm working with Laravel 5.5 and I use Visual Studio Code for code editor. After last update, VS Code freaked out. The main problem is that I can't search files inside vendor folder with ctrl+p. I can search and find any files except inside vendor folder. Does vendor folder disallow searching? I can't find anything related to this. Does anyone have a similar problem? Thanks!
Fix 1.
I am not sure how many projects you have but I think you can enable this by changing the excludefile settings.
Go to VSCode > Preferences > Settings or press ⌘,.
Search for files.exclude and make **/.git to false.
Fix 2
OR try to search for search.useIgnoreFiles in your settings and make it false.
You can find more details here.
Open User Settings
Search for: "Search: Use Ignore Files"
Uncheck: "Controls whether to use .gitignore and .ignore files when searching for files."
Can't find an simple, basic solution anywhere for this problem so I figured it was worth posting it here.
When I go to run my code as a task, I get the following message: "Tasks are only available on a workspace folder" - I can't find a solution anywhere and I'm a beginner at Visual Studio Code so I might need the answer / solution explaining in more simpler terms.
VSC Version = 1.17.0
Visual Studio Code treats the folder containing your program file as a workspace folder.
Your tasks created will be contained in a file tasks.json within a hidden folder .vscode inside your project or workspace folder.
So instead of opening the file directly to create a task, you need to open the folder as a project.
The "Workspace launch configuration" section of VSCode mentions:
With multi-root workspaces, VS Code searches across all folders for launch.json debug configuration files and displays them with the folder name as a suffix.
Additionally VS Code will also display launch configurations defined in the workspace configuration file.
Example of settings: vscode-tslint/vscode-tslint.code-workspace
As an alternative, you can have User level tasks to share them across projects since VSCode 1.42 (Jan. 2020).
But regarding workspace tasks, since VSCode 1.57 (May 2021), said tasks will have to be "trusted" by anyone opening the same workspace, assuming you have versioned and pushed the .vscode folder.
Safe code browsing
It's great that there is so much source code available on public repositories and file shares. No matter the coding task or problem, there is probably already a good solution available somewhere.
However, using open-source code and tools does have risks and you can leave yourself open to malicious code execution and exploits.
Workspace Trust provides an extra layer of security when working with unfamiliar code by preventing automatic code execution when a workspace is open in Restricted Mode.
I often like to use VSCode to quick view some projects to pull snippets from them. However, this leads to a ton of additional .vscode folders being placed on my drive in any folder I use the right-click -> Open with VSCode option.
Is there a way to disable this folder from being created every time vscode loads somewhere new?
This issue was due to the 'C/C++ for Visual Studio Code' extension being outdated.
Upgrading to the latest version of this extension has fixed the problem.
That is not the standard behaviour of VSCode, normally the .vscode only gets generated once there is something like a launch.json put into it. Mind checking what's actually in there?
I have Sublime-Text 3 with Omnisharp running fine. I created a project to use with this, and now have the following two files:
MySolution.sublime-project
MySolution.sublime-workspace
Should these files be added to source control?
If not, what can I do to ignore the files in source control, but don't get clobbered on the equivalent of git clean?
From the Sublime Text docs on projects:
As a general rule, the sublime-project file would be checked into version control, while the sublime-workspace file would not.
I'm having an issue with netbeans scanning a large directory of PHP files
The scan takes about 2 hours and totally blocks the IDE's autocompletion and slows it down a lot
I tried a few things:
disabling auto-scanning of sources as mentionned here
adding the pattern of the files in the "Files ignored by the IDE" box
adding the directory to the ignored folder list in my project properties
None of the above worked.
An idea anyone?
You also might be able to ignore just some files from the automatic source scan.
See netbeans wiki
You need to close the "Tasks" tab to stop it.