VSCode: settings.json file is not recognizing a terminal.integrated setting - visual-studio-code

Why is this entry not recognized by VSCode? I have a very slow terminal output that I am hoping this will help fix:
"terminal.integrated.rendererType": "experimentalWebgl"
The above command is known to exist, here: https://github.com/Microsoft/vscode-docs/blob/master/docs/editor/integrated-terminal.md
Here is my settings.json file:
{
"atomKeymap.promptV3Features": true,
"editor.formatOnPaste": true,
"editor.multiCursorModifier": "ctrlCmd",
"python.pythonPath": "C:\\Users\\Andrew\\Anaconda3",
"workbench.colorTheme": "Visual Studio Dark",
"terminal.integrated.rendererType": "experimentalWebgl", # grey'd out assuming its not a real command
"workbench.iconTheme": "Monokai Pro Icons",
"workbench.editorAssociations": {
"*.ipynb": "jupyter-notebook"
},
"python.defaultInterpreterPath": "C:\\Users\\Andrew\\Anaconda3",
"terminal.integrated.defaultProfile.windows": "Command Prompt",
"notebook.cellToolbarLocation": {
"default": "right",
"jupyter-notebook": "left"
},
"debug.javascript.pickAndAttachOptions": {
},
"workbench.colorCustomizations": {
}
}

The referenced markdown documentation file is not up to date (note that it's on branch master, while current development happens on the main branch). The WebGL renderer has been made the default in v1.55 (March 2021):
As part of this work we also added some fallback logic. When "terminal.integrated.rendererType": "auto", the following happens:
The WebGL renderer will try to start up.
If it fails, for example due to lack of OS/browser support:
The canvas renderer will be enabled and the time it takes to render a frame will start to be measured.
If the first 20 frames are rendering slowly, for example if there are hardware issues or GPU rendering is disabled:
The DOM renderer will be enabled.
In the next release, we plan on removing the rendererType setting all together in favor of a much more understandable "terminal.integrated.gpuAcceleration": "auto" | "on" | "off".
See the current documentation on this for further reference.

Related

Why is importing an icon named ImportExport breaking other dependencies?

I added a Material-UI icon to one of my react components like so:
import { ImportExport } from '#material-ui/icons';
Thereafter, on my production site (but not my localhost dev server), I started getting an error on pageload whereby my socket-io client library was unable to correctly import something in one of its internal files. It had this:
const encodePacket = require("./encodePacket");
Which was used like so:
encodePacket(packet, false, encodedPacket => {
This is where the error arises: TypeError: encodePacket is not a function. Inspecting it, I can see that encodePacket is indeed not a function. When printed in the console, it shows as {default: {…}, __esModule: true}.
On my localhost dev server, this isn't the case. It's a function as expected. Moreover, the import right next to it, for decodePacket, is still a function in both contexts, locally and in production.
More bizarrely, when I examine the encodePacket module in the console, it looks like this:
Mui is Material-UI, a UI lib I use in other parts of the application and from which the icon is sourced - obviously it has no connection to a network library's internal packet encoding logic.
By commenting out the ImportExport icon and its import, I found that the error goes away.
What on earth though? How could this happen?
I even tried renaming the icon, but that didn't work either~
import { ImportExport as ReverseSortIcon } from '#material-ui/icons';
Any suggestions? I'm using Parcel and this is my tsconfig that has worked for 2+ years uneventfully~
{
"compilerOptions": {
"outDir": "./dist/",
"sourceMap": true,
"strict": true,
"noImplicitReturns": true,
"noImplicitAny": true,
"module": "es6",
"moduleResolution": "node",
"target": "es5",
"allowJs": true,
"jsx": "react",
"esModuleInterop": true
},
"include": [
"./src/**/*"
]
}

Prettier in vscode

I have a Problem with Visual Studio Code and Prettier. I got the following ".prettierrc"
{ "semi": false, "singleQuote": true, "arrowParens": "avoid", "bracketSpacing": false, "printWidth": 60 }
when i do know "npx prettier -w *.js" it works fine, for example it removes the Semicolon at the end of each line. But when I try to use it without the npx it doesn't work. I got the Option "format on save" activated for Prettier. But he only moves the semicolon to the end of the line and doesn't delete it.
I activated "Prettier:Require Config", Set Prettier -Code Format as default and also added "Prettier:Config Path: prettierrc" <-- Is my path maybe wrong ??

Code Runner extension in vs-code does not give clean output, despite checking off "Show Execution Message" option

I recently started using Code Runner Extension for Vs-Code and despite checking off the "code-runner.showExecutionMessage": false it keeps printing the file path, and some unwanted code after which it does print output but it's not clean, looks messy and hard to read the output. Here's what it does.
PS [path] \VsCode\ProblemSolving> cd "[path] \VsCode\ProblemSolving"
PS [path] \VsCode\ProblemSolving> cd "[path] \VsCode\ProblemSolving\" ; if ($?)
{ g++ CodingCompetitionTools.cpp -o CodingCompetitionTools } ; if ($?) { .\CodingCompetitionTools }
This precedes the actual program output and I don't want to see this, just the clean program output.
Settiings.json for code-runner
"code-runner.defaultLanguage": "c++",
"code-runner.saveAllFilesBeforeRun": true,
"code-runner.saveFileBeforeRun": true,
"code-runner.fileDirectoryAsCwd": true,
"code-runner.showExecutionMessage": false,
"code-runner.clearPreviousOutput": true,
"code-runner.runInTerminal": false,
Refer this link for Vs-Code Marketplace extension
Could you please share your settings.json file?
I guess your setting looks like this?
{
"code-runner.showExecutionMessage": false
}
Maybe you have code-runner.runInTerminal set to true? If so, change it to false.
Just to debug this a little further, create a .vscode folder in the root of your current project (with a preceding dot) and inside of that folder a settings.json file with just:
{
"code-runner.defaultLanguage": "c++",
"code-runner.saveAllFilesBeforeRun": true,
"code-runner.saveFileBeforeRun": true,
"code-runner.fileDirectoryAsCwd": true,
"code-runner.showExecutionMessage": false,
"code-runner.clearPreviousOutput": true,
"code-runner.runInTerminal": false
}
See if this changes anything.
Apologies if these steps are already obvious to you, but better safe than sorry.

LaTeX Workshop does'nt work well (Recipe terminated with error.)

Problem
I fail to build the LaTeX document on the VScode with LaTeX Workshop.
More preciously, ctrl + S can save the document but can't build the pdf. VScode warns "Recipe terminated with error".
The thing is that I was able to build the LaTeX documents earlier, but yesterday it abruptly didn't work well. Although I didn't change any option about LaTeX, I changed some settings about Python. For example, I uninstalled Anaconda and tried to create virtual environment of python with pipenv. However, I don't think those change are related to this problem...
settings.json
settings.json is as following.
{
"editor.suggest.snippetsPreventQuickSuggestions": false,
// ---------- LaTeX Workshop ----------
"latex-workshop.intellisense.package.enabled": true,
"latex-workshop.message.log.show": true,
"latex-workshop.message.badbox.show": true,
"latex-workshop.latex.autoClean.run": "onBuilt",
"latex-workshop.view.pdf.viewer": "tab",
"latex-workshop.latex.recipes": [{
"name": "ptex2pdf",
"tools": [
"ptex2pdf"
]
}],
"latex-workshop.latex.tools": [{
"name": "ptex2pdf",
"command": "ptex2pdf",
"args": [
"-l",
"-ot",
"-kanji=utf8 -synctex=1 -interaction=nonstopmode",
"%DOC%"
]
}],
"latex-workshop.message.latexlog.exclude":["(Font shape `(JY1|JT1|JY2|JT2)(/.*)(sl|it|sc)'.*|Some font shapes were not available.*)"]
}
Additional information
Since I hadn't used Workspace of VScode yet, but yesterday I started to use that. Since I thought it
may be the reason of the problem, now I stop using the worspace, but the situation doesn't change.
Furthermore, if I run on the cmd on VScode,
platex hoge.tex
dvipdfmx hoge.dvi
the pdf was outputted successfully.
environment
Windows10 Home
VScode 1.49.0
LaTeX Workshop 8.13.2

visual-studio-code Powershell command auto-complete in the editor panel not working

I've just started using Visual Studio Code for working with Powershell. I've loaded the powershell extension, and when I connect to Exchange auto-completion of cmdlets works in the integrated powershell window, but it doesn't work in the to peditor panel. How can I get cmdlet auto-complete or intellisense to work in the editor panel? Thank you!
You don't say if you configured you VSCode environment to make PowerShell the default language. If you look in the right hand corner of the editor, it will tell you what language is currently set to. Show your user settings. In your user settings, you should have lines like this in place (just an example from mine, tweak as needed for your use case - see the docs for details on the VSCode user settings.)…
"extensions.autoUpdate": true,
"files.defaultLanguage": "powershell",
"powershell.scriptAnalysis.enable": true,
"powershell.startAutomatically": true,
"powershell.integratedConsole.focusConsoleOnExecute": false,
"powershell.enableProfileLoading": true,
"powershell.developer.editorServicesLogLevel": "Verbose",
"editor.formatOnSave": true,
"editor.minimap.enabled": false,
"editor.mouseWheelZoom": true,
"editor.tabCompletion": "on",
"editor.suggestSelection": "first",
"terminal.integrated.shell.windows": "C:\\WINDOWS\\Sysnative\\WindowsPowerShell\\v1.0\\powershell.exe",
"terminal.integrated.rightClickBehavior": "default",
"window.title": "${activeEditorLong}",
"powershell.powerShellExePath": "C:\\WINDOWS\\System32\\WindowsPowerShell\\v1.0\\powershell.exe",
"powershell.scriptAnalysis.settingsPath": "ScriptAnalyzerSettings.psd1",
"workbench.startupEditor": "newUntitledFile",
"editor.cursorStyle": "line-thin",
"shellLauncher.shells.windows": [
{
"shell": "C:\\Windows\\system32\\WindowsPowerShell\\v1.0\\powershell.exe",
"label": "PowerShell 5.1"
},
{
"shell": "C:\\Program Files\\PowerShell\\6\\pwsh.exe",
"label": "PowerShell 6.0"
},
{
"shell": "C:\\Windows\\System32\\cmd.exe",
"label": "cmd"
},
{
"shell": "C:\\Program Files\\Git\\bin\\bash.exe",
"label": "Git bash"
},
{
"shell": "C:\\Windows\\System32\\bash.exe",
"label": "WSL Bash"
},
VSCode is notorious for intellisense stopping for no apparent reason (it's my #1 grip with it), but in most cases, all you have to do is backspace to the beginning of your command and try again, or use the CRTL+Spacebar to have intellisense kick it, or type reload.
Again, this happens to me all the time, and the above brings things back. It's annoying, but it is what it is.