jlelong / latex-workshop-wiki Goto Github PK

Hello,

The option latex-workshop.intellisense.label.keyval seems not to be present in the extension settings. Labels defined using label={...} are not detected. Has this option been deprecated?

Regards,
Lukasz

This is a duplicate of of issue James-Yu/LaTeX-Workshop#2139 (closed as not located on the right repo).

I am not really sure where to put this information so I wanted to draw your attention on this before doing anything.

Do you think the wiki deserves a build tools section (if not already existing) and in particular, an arara section ?

Currently, all latex projects without magic comments, are built using the default recipe (the first recipe). I find this behavior not so satisfactory since different project uses different compilers. In my case, many available English-version paper templates use pdflatex as its compiler, and I have to use xelatex to write Chinese.

Thus, I'm wondering if any of the following two options are possible, or already implemented but not documented:

• when called Build Latex Project, change the default recipe to the last called recipe Build with recipe.
• provide a project-only configuration file to override the global building settings.

Thanks

For longer .tex files, the structure is no longer visible. Also, the structure is not supporting the \include command: the chapters, sections, subsections, etc. in it.

the SyncTex can be used with the following settings:

In sumatraPDF: (THIS IS IMPORTANT)

InverseSearchCmdLine = "C:\Users\<Username>\AppData\Local\Programs\Microsoft VS Code\Code.exe"  -g "%f":"%l"// the part of cli.js is deleted
EnableTeXEnhancements = true

In vscode: (other settings are the same as normal)

"latex-workshop.view.pdf.external.synctex.args": [
        "-forward-search",
        "%TEX%",
        "%LINE%",
        "-reuse-instance",
        "-inverse-search",
        "code \"C:\\Users\\<Username>\\AppData\\Local\\Programs\\Microsoft VS Code\\resources\\app\\out\\cli.js\" -r -g \"%f:%l\"", 
        //In this place, whether the cli.js is deleted seems like make no sense
        "%PDF%",
    ],

P.S. it seems like that the cli.js is not necessary, but i do not know the reason why the deletion will make sense since i have no idea about the file or anything about the principle of SyncTex, but it truly works for me. By the way, this way seems like also solve the problem that the SyncTex fails when use inverse search and open the cli.js in vscode instead.

Some configuration variables from package.json are not documented in the wiki

• latex-workshop.chktex.delay
• latex-workshop.chktex.run
• latex-workshop.docker.image.latex
• latex-workshop.hover.ref.number.enabled
• latex-workshop.intellisense.update.aggressive.enabled
• latex-workshop.intellisense.update.delay
• latex-workshop.latex.external.build.args
• latex-workshop.latex.rootFile.useSubFile
• latex-workshop.message.convertFilenameEncoding
• latex-workshop.progress.barLength
• latex-workshop.progress.barStyle
• latex-workshop.progress.runIconType
• latex-workshop.texdoc.args
• latex-workshop.view.pdf.external.synctex.args
• latex-workshop.view.pdf.external.synctex.command
• latex-workshop.viewer.pdf.internal.port

On the contrary, some variables documented in the wiki do not exist anymore

• latex-workshop.chktex.interval
• latex-workshop.hover.ref.numberAtLastCompilation.enabled
• latex-workshop.latex.texdoc.args
• latex-workshop.latex.texdoc.path
• latex-workshop.view.pdf.external.command
• latex-workshop.view.pdf.external.synctex

• In the Explorer Panel, the Outline view only describes the structure of the current file.
• In the TeX badge, the structure view describes the structure of the complete LaTeX project.

I'd like to propose the addition of a snippet for the Omega symbol ("\Omega") in a manner similar to the existing functionality. For instance, just like "@f" outputs "\phi" and "@f" outputs "\Phi", I propose the addition of the snippet "@o" to generate "\Omega".

Currently, while using the LaTeX Workshop, there isn't a predefined snippet for entering the Omega symbol. Introducing this snippet would be beneficial for users, providing a more streamlined and efficient way to input this specific symbol.

Would it be possible to include this snippet in the library of predefined shortcuts for enhanced user convenience?

Thank you for considering this enhancement suggestion!

Translation provided by ChatGPT

When editing a Tex file, the role of placeholder • is erratic. When several of these are put sequentially in a snippet, the TAB only moves the pointer to the first • and behaves erratically afterwards. It is not possible to get out of an environment using • when this placeholder is outside the environment. Would it be possible to program the • so that TAB moves seamlessly from • to • ?

The reference link on the following page as “see here” is broken.

https://github.com/James-Yu/LaTeX-Workshop/wiki/View#sumatrapdf

This is because the discussion forum has moved.

Wrong link

https://forum.sumatrapdfreader.org/t/inverse-search-not-performed-for-vs-code-exe/4486/20

https://forum.sumatrapdfreader.org/t/inverse-search-not-performed-for-vs-code-exe/4486/20

Go to “Not Found” page...

Correct link

https://forum.sumatrapdfreader.org/t/inverse-search-not-performed-for-vs-code-exe/4486

https://forum.sumatrapdfreader.org/t/inverse-search-not-performed-for-vs-code-exe/4486

However, it is difficult to see which part of the link page is being referred to. You can also make the reference point clearer by adding highlights to specific characters. See https://developer.chrome.com/blog/new-in-chrome-80/#more

https://forum.sumatrapdfreader.org/t/inverse-search-not-performed-for-vs-code-exe/4486/#:~:text=DigNative

https://forum.sumatrapdfreader.org/t/inverse-search-not-performed-for-vs-code-exe/4486/#:~:text=DigNative

The Sumatra Reader Discussion Forum moved to GitHub Discussion of SumatraPDF.

This past discussion logs will be archived. See sumatrapdfreader/sumatrapdf#2293

Variables in package.json but not in the wiki:

• latex-workshop.codespaces.portforwarding.openDelay
• latex-workshop.latex.build.rootfileInStatus
• latex-workshop.latex.rootFile.indicator
• latex-workshop.synctex.indicator.enabled

Variables in the wiki but not in package.json:

• latex-workshop.intellisense.fastparse.enabled
• latex-workshop.intellisense.label.keyval

I tried to compile multiple file project but it is not compiling it is always showing errors. Could you please help me with it?
It is always showing "Recipe terminated with error". I am attaching the screenshot below.

please help!!

@James-Yu We had better update Linters.md

Configuration variables

• latex-workshop.intellisense.preview.enabled
• latex-workshop.progress.location
• latex-workshop.view.pdf.tab.backgroundColor

Commands

• latex-workshop.actions
• latex-workshop.addtexroot
• latex-workshop.citation
• latex-workshop.clean
• latex-workshop.kill
• latex-workshop.log
• latex-workshop.refresh-viewer
• latex-workshop.saveWithoutBuilding
• latex-workshop.showCompilationPanel
• latex-workshop.showSnippetPanel
• latex-workshop.synctex
• latex-workshop.tab
• latex-workshop.texdoc
• latex-workshop.texdocUsepackages
• latex-workshop.view

Just as with Path Autocomplete, the Path Intellisense extension breaks the autocompletion for bibliograpy citations.

I have added this incompatibility in a PR: #78

The following variables are not documented

• latex-workshop.bibtex-format.trailingComma
• latex-workshop.intellisense.includegraphics.preview.pdf.enabled
• latex-workshop.mathpreviewpanel.editorGroup

It turns out that Synctex doesnot work with zathura for the latest vscode on the linux system.
The discussion suggests that --no-sandbox flag can fix this.

When working with multi-file projects that have multiple alternate root files that include the same sub-files, the current root file detection can be hard to switch. For example:

• A1 and A2 are root files that both input B, and only define some toggles: these build two different versions of a document (e.g. for short/full versions of some document).
• B contains \begin{document} and possibly includes multiple subfiles C1...CN

Using the current root file setup, it is cumbersome to switch between A1 and A2, especially when editing Cx, as the root file to compile needs to be either hardcoded in all these files B,C1..CN, or one needs to switch back to A1/A2 to trigger the build.

Requested feature:

A generic solution that would probably work for many other use cases, is to introduce a workspace setting that, if present, overrides the root file detection (https://github.com/James-Yu/LaTeX-Workshop/wiki/Compile#the-root-file). This could be called something like, e.g., latex-workshop.latex.rootfile or latex-workshop.latex.forceRootfile.

(Note that I tried to simulate this behavior with include/exclude lists for the root file search, but this didn't yield the override I wanted in all cases.)