Comments (10)
@martinra Do you have a ~/.latexmkrc
file? If so, then #1062 should fix the issue.
from texlab.
I do. I also pulled #1062 and the project root is now detected correctly. Thanks a lot the quick solution!
from texlab.
Is this truly fixed @pfoerster? I still have the exact same issue under both v5.14.1 (from nixpkgs-unstable) and v5.15.0 (from Homebrew). I used the minimal example mentioned by @martinra to test it. As long as my ~/.latexmkrc
is present, the project root is not recognized.
More exactly:
- with
~/.latexmkrc
:- if I have
~/tmp/.latexmkrc
, the project root is correctly identified as~/tmp/
- if I have
~/tmp/latexmkrc
(without the dot), the project root is incorrectly identified as~/
- similarly, I get the incorrect project root with any of the following files:
~/tmp/texlabroot
,~/tmp/.texlabroot
, and~/tmp/.git
- if I have
- without
~/.latexmkrc
:- the project root is correctly identified if there is either
~/tmp/.git
or~/tmp/.latexmkrc
- in all other cases (no special files,
~/tmp/texlabroot
,~/tmp/.texlabroot
,~/tmp/latexmkrc
) the project root is seemingly not set at all (the log oftexlab
reports it asnull
)
- the project root is correctly identified if there is either
from texlab.
@pitkling How are you checking the project root? Compiling the project, looking at the dependency graph or something else? How does the wrong project root show itself?
from texlab.
@pfoerster I used :LspInfo
of neovim/nvim-lspconfig and also double checked via the log file created bis texlab --log-file <file>
. Is this reproducible on your end or is it specific to my setup? Let me know if I can provide any further info to debug this.
from texlab.
Is this reproducible on your end or is it specific to my setup?
With VSCode, I am not able to reproduce it. Is the working directory of the editor (and thus the server) set to ~
or ~/tmp
. If it is ~
, then #1098 should have fixed this issue.
from texlab.
The working directory of Neovim seems not to matter. I tested it by starting Neovim from ~/
, from ~/tmp/
, and from a different subdirectory of ~/
. Neovim's :LspInfo
still reports ~/
as the root directory if ~/tmp/.latexmkrc
is not present. Again, other indicator files (~/tmp/{texlabroot,.texlabroot,.git}
) do not help either.
I also made sure to disable any other unrelated Neovim configuration/plugins and only load texlab
via Neovim/nvim-lspconfig
.
from texlab.
@pfoerster In case it helps, here is texlab
's log file (maximum verbosity) when opening ~/tmp/main.tex
in a minimal Neovim configuration. I had the following project root indicator files present: ~/tmp/{texlabroot,.texlabroot,.git,latexmkrc}
. As the log file indicates, texlab
sets ~/
as the project root.
from texlab.
This is an nvim-lspconfig issue (root directory detection is part of the client configuration shipped by this plugin); please open the issue there.
from texlab.
Ok, thanks for the pointer, I thought nvim-lspconfig
takes the root directly from texlab
.
P.S.: Feel free to close the issue again, and sorry for the noise. Also, in case someone finds this: The problem has been fixed a few months back in nvim-lspconfig
.
from texlab.
Related Issues (20)
- Thmtool's \declaretheorem should also accept list of environment names HOT 1
- ConcealLevel Support? HOT 2
- Custom LaTeX Commands Misinterpreted as Citations Causing Errors
- Support more macros for defining commands
- Support "Go To References" for commands
- Generic inverse search using show document request
- Disabling individual warnings HOT 1
- Allow extending label commands (not just ref)
- Lsp panics after deleting last line of a file HOT 4
- Forward search broken with empty latexmkrc
- project detection: .latexmkrc in higher level parent directory HOT 2
- texlab reports dublicate and unused label in macro definition
- Feature request: support apastyle prenotes
- BibLaTeX globbing patterns (`\addbibresource[glob]{}`) do not seem to read the `.bib` files under `nvim` HOT 1
- Diagnostics not displayed with `$aux_dir`
- Texlab lsp server exits on unicode letter 1F582 HOT 4
- ignore single warnings/errors HOT 1
- Compile on save doesn't work in neovim HOT 2
- Add user-defined prefixes to custom label reference and definition commands HOT 1
- Bib reference error for subimports HOT 8
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from texlab.