Tag Archives: editor

VSCode Unable to find custom header file directory: fatal error: no such file or directory

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",
  }

[Solved] Latex&VScode Error: I found no bibdata command//command//citation—while reading file*.aux

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", 

}

VScode debug error: configured debug type ‘Python’ is not supported

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.

Vs code execute command error [How to Solve]

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:

    1. download the cmder plug-in in vs Code

    1. modify the default terminal

 

    1. steps: File —— preferences —— settings —— search shell —— Click to enter the file

"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

[Solved] Toad Set Error: The following files specified on the Executables tab could not be found:TNS Ping

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.

How to Solve Vscode save Vue file eslint error

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.

Visual Studio 2010 compilation error fatal error lnk1123: failed during conversion to coff: solution to invalid or corrupt file

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

Vscode automatically formats the code when an error is reported

Use default

Prettier vscode save code auto format plug-in used by vscode
select formatonsave in vscode settings or modify it in setting.json

"editor.formatOnSave": true,

Use eslint for automatic formatting

Sometimes your front-end project uses eslint, which has automatic formatting configuration. We want to use the project’s own eslint configuration. We can use the format of eslint when saving automatically.

Let’s install the eslint plug-in first

Then set it in vscode

"editor.codeActionsOnSave": {
        "source.fixAll.eslint": true
 }

Add this configuration. In this way, the eslint configuration of the project itself will be used when saving.

After modifying the Tomcat configuration file in development, the modified configuration file will be automatically restored after ecplise starts Tomcat

The causes of the problem are as follows:


The reason is that when Tomcat is added in eclipse, eclipse will automatically store the Tomcat configuration file. When the Tomcat server starts in eclipse, it will replace the original Tomcat configuration file with its stored Tomcat configuration file.


resolvent:


1. Set ecplise to cancel the automatic publishing function

    in ecplise, select window preferences server launching to cancel automatically publishing Wen starting servers and click OK to finish operation

    2. In ecplise project, there is a server project, a Tomcat VX. X server at localhost config, in which there are configuration files to modify the files directly. When Tomcat is republished, it will use the configuration files here to cover the files in conf under Tomcat

SLAMBook2 in ch3 code run fatal error: Eigen/Core: No such file or directory

1. First determine whether you have installed eigen3

If not, use the following command to install:

sudo apt-get install libeigen3-dev

2. The installation directory is inconsistent with the directory specified in cmakelists.txt

The default installation directory in cmakelists.txt is as follows:

modify it to the correct path

the final running success is as follows: