Linux Mint installs linuxbrew and resolves the boot error
Errors are reported as follows
Solution:
Checking the **.profile file** in the user directory, I found that eval was linked to the previous line, presumably because of a bug in the installation of the jetbrains toolbox
change Eval to the next line and save it (with administrator permission)
Premise: node and typescript are installed
Error: execute TSC xxx.ts in vscode, an error will be reported.
Solution: the execution mechanism of vscode is limited. Just change the execution mechanism
Exit vscode and run as administrator.
step 1:
execute get-ExecutionPolicy and return Restricted, which means it is restricted.
step 2:
execute set-ExecutionPolicy RemoteSigned
step 3:
execute get-ExecutionPolicy and return RemoteSigned
Perform the above steps and execute TSC xxx.ts again is OK
Sublime is the editor I am used to. I want to download it after reinstalling the system recently, but according to the download method on the official website, the following error will appear:
@ubuntu:~$ wget -qO - https://download.sublimetext.com/sublimehq-pub.gpg | sudo apt-key add -
OK
@ubuntu:~$ echo "deb https://download.sublimetext.com/ apt/stable/" | sudo tee /etc/apt/sources.list.d/sublime-text.list
deb https://download.sublimetext.com/ apt/stable/
@ubuntu:~$ sudo apt update && sudo apt install sublime-text
Hit:1 http://us.archive.ubuntu.com/ubuntu focal InRelease
Hit:2 http://security.ubuntu.com/ubuntu focal-security InRelease
Hit:3 http://us.archive.ubuntu.com/ubuntu focal-updates InRelease
Ign:4 https://download.sublimetext.com apt/stable/ InRelease
Hit:5 http://us.archive.ubuntu.com/ubuntu focal-backports InRelease
Err:6 https://download.sublimetext.com apt/stable/ Release
Certificate verification failed: The certificate is NOT trusted. The certificate chain uses expired certificate. Could not handshake: Error in the certificate verification. [IP: 104.236.0.104 443]
Reading package lists... Done
E: The repository 'https://download.sublimetext.com apt/stable/ Release' does not have a Release file.
N: Updating from such a repository can't be done securely, and is therefore disabled by default.
N: See apt-secure(8) manpage for repository creation and user configuration details.
The reason is that a software package called “ca-certificates” is not installed. After installation, you can execute the installation instruction of sublime from the beginning.
@ubuntu:~$ sudo apt install ca-certificatesUnable to open some built-in pages, including the home page
error: Unable to resolve resource walkThrough://vscode_getting_started_page
solution: File – preferences – settings
search “editorassociations”
delete all the contents.
The solution is as follows:
First, add the path of the folder where your header file is located in "includepath":[] of C_cpp_properties.json.
Of course, this step is only to tell the vscode header file where it is for debugging, but it is not known when GCC compiles. We know that if you use G + + main.CPP - I library_path - O main can be compiled successfully directly, so we just need to tell vscode to use our own defined commands
There are generally two methods. The first is to add “- I header_file_path” to the args key in tasks.json, as follows:
"args": [
"-g",
"${workspaceFolder}\\src\\*.cpp",
"-o",
"${fileDirname}\\src\\${fileBasenameNoExtension}.exe",
"-I",
"header_file_path"
],
But it doesn’t seem to work well in some cases.
The second method is to directly set in setting.json:
"code-runner.executorMap": {
"cpp": "cd $dir && g++ $fileName -o $fileNameWithoutExt -I 'header_file_path' && $dir$fileNameWithoutExt",
}
Latex& Vscode error I found no bibdata command// command// citation – while reading file * aux
Problem description
The template I use requires the compile order: Compile with: xelatex -> biber -> xelatex -> xelatex
Using various tutorials in the VScode plugin configuration json file are xelatex -> bibtex -> xelatex -> xelatex
In fact bibtex and biber are not a thing, refer to tex link
Resulting in the problem as shown
Solution:
Add the configuration for biber compilation to the setting.json configuration file in VScode’s Latex
"latex-workshop.latex.tools": [
{
"name": "biber",
"command": "biber",
"args": [
"%DOC%"
]
}
],
"latex-workshop.latex.recipes": [
{
"name": "xelatex -> biber -> xelatex*2",
"tools": [
"xelatex",
"biber",
"xelatex",
"xelatex"
]
}
],
Restart VScode and use xelatex -> biber -> xelatex*2 to compile successfully
Full Codes:
{
"latex-workshop.latex.tools": [
{
"name": "latexmk",
"command": "latexmk",
"args": [
"-synctex=1",
"-interaction=nonstopmode",
"-file-line-error",
"-pdf",
"%DOC%"
]
},
{
"name": "xelatex",
"command": "xelatex",
"args": [
"-synctex=1",
"-interaction=nonstopmode",
"-file-line-error",
"%DOC%"
]
},
{
"name": "pdflatex",
"command": "pdflatex",
"args": [
"-synctex=1",
"-interaction=nonstopmode",
"-file-line-error",
"%DOC%"
]
},
{
"name": "bibtex",
"command": "bibtex",
// "command": "biber",
"args": [
// "%DOC%"
"%DOCFILE%"
]
},
{
"name": "biber",
"command": "biber",
// "command": "biber",
"args": [
"%DOC%"
]
}
],
"latex-workshop.latex.recipes": [
{
"name": "xelatex",
"tools": ["xelatex"]
},
{
"name": "latexmk",
"tools": ["latexmk"]
},
{
"name": "pdflatex -> bibtex",
"tools": ["pdflatex","bibtex"]
},
// {
// "name": "pdflatex -> bibtex -> pdflatex*2",
// "tools": [
// "pdflatex",
// "bibtex",
// "pdflatex",
// "pdflatex"
// ]
// },
{
"name": "xelatex -> bibtex -> xelatex*2",
"tools": [
"xelatex",
"bibtex",
"xelatex",
"xelatex"
]
},
{
"name": "xelatex -> biber -> xelatex*2",
"tools": [
"xelatex",
"biber",
"xelatex",
"xelatex"
]
}
],
"latex-workshop.latex.clean.fileTypes": [
"*.aux",
"*.bbl",
"*.blg",
"*.idx",
"*.ind",
"*.lof",
"*.lot",
"*.out",
"*.toc",
"*.acn",
"*.acr",
"*.alg",
"*.glg",
"*.glo",
"*.gls",
"*.ist",
"*.fls",
"*.log",
"*.fdb_latexmk"
],
"latex-workshop.message.error.show": false,
"latex-workshop.message.warning.show": false,
"latex-workshop.showContextMenu": true,
"latex-workshop.intellisense.package.enabled": true,
"latex-workshop.latex.autoBuild.run": "onSave",
}
When using vscode to debug, an error is reported in the pop-up window:
Configured debug type 'python' is not supported
Refer to the reference website: https://github.com/microsoft/vscode/issues/136712
The measured solution is metaphysical, as follows:
Delete Jupiter and python in vscope extensions, and then reinstall them; Close all vscodes; (this step is very important.) Open vscode again and you can debug normally.
Inexplicable mistake about vs Code
Error Description:
Drive not found. If you enter any execution command in the vs Code terminal, you will report “drive not found”. The name is’ ‘ The drive for ‘C’ does not exist.
Solution:
"terminal.integrated.shell.windows": "C:\\WINDOWS\\System32\\cmd.exe"
Note out and replace with:
"terminal.integrated.shell.windows": "cmd.exe",
"terminal.integrated.env.windows": {"CMDER_ROOT": "[cmder_root]"},
"terminal.integrated.shellArgs.windows": ["/k", "[cmder_root]\\vendor\\init.bat"],
As shown in the figure:
4 Save exit, restart vs Code
Today, when the toad adjustment setting of the software is completed, click OK to always report
error: the following files specified on the executables tab could not be found: TNS Ping, as shown in the following figure
in fact, it is mainly caused by the setting problems in other places in the option, here we just need to modify the setting,
Select View toad options editor executables TNS Ping. Then check whether the path of your own command in the figure below is correct, or you can directly click the “auto search” button to automatically obtain the correct path 
After that, click OK in other options in toad, and no error will be reported.
Just change the code UTF-8 to GB18030
at first, just modify the code in the lower right corner
Problem background
When using vscode to automatically save, it is found that there is a problem with each save format. 
Solution:
There are only a few storage formats
The saving format of vscode itself uses the saving format configured by eslint
so after analysis, the problem is clear at a glance.
After investigation,
it was originally set in vscode settings.json
"editor.formatOnSave": true,
Also set
"editor.codeActionsOnSave": {
"source.fixAll.eslint": true
},
In this way, the first save takes effect, but the second save uses other configurations, resulting in inconsistency between the two
handle
"editor.formatOnSave": true,
Just delete this configuration. When saving, you can only format it according to the eslint configuration.
VS2010 environment compilation encountered a fatal error lnk1123: failure during conversion to coff: invalid or corrupt file, fatal error lnk1123: failure during conversion to coff.
Here are some solutions:
Option 1:
Click “project” – & gt; “Properties” – & gt; “Inventory tool”,
Then select “input and output” – & gt; “embedded list”, and change the following “yes” to “no”
Option 2:
Search the vs installation directory for cvtres.exe
Two cvtres.exe files were found, including
Some netizens chose to overwrite all the old cvtres.exe with the latest file, and some netizens deleted the old cvtres.exe file
Change the name for the recovery environment. Note that the two files have the same version number, but the generation time is only 1 hour. Select the latest one. There are also many cvtres.exe searches
I don’t know. Try how to delete these files. My two file directories are as follows:
D:\ProgramFiles (x86)\Microsoft Visual Studio 10.0\VC\bin\amd64
D:\Program Files (x86)\Microsoft VisualStudio 10.0\VC\bin
Option 3:
Even if the new VS2010 Sp1 is installed, this method can also solve some of this problem.
What’s more troublesome is that this Sp1 is still relatively large, and all the messy things have to be patched.
= division line of sigh ===========
Related resources: lnk1123: failure during conversion to coff: solution to invalid or corrupt file _lnk1123
Lnk1123: failure during conversion to coff: solution to invalid or corrupt file
original link: https://blog.csdn.net/weixin_39951018/article/details/111739349