Re: Remote LSP unable to find texlab server

[Riccardo Romoli]

Good morning Michael,

Did you really start with emacs -Q, and have sent
  the *whole* log?

I'm not an expert emacs user so it has been quite difficult to be able to run the command you suggested without errors. Due to the spacemacs layers config, to loar lsp-mode I wrote a specific init.el file and ran emacs -Q -l my-specific-init-el. First of all I try to open a local latex file to check if lsp works using this configuration file. Then I open the remote latex file and manually load lsp (M-x lsp-mode). The lsp does not start because it is not able to find the server. Reading the log file it seems that the path I set was not loaded. I attach both the custom init.el and the log from tramp.

Best Regards, Riccardo

On Thu, Feb 8, 2024 at 4:32 PM Michael Albinus <michael.albinus@gmx.de> wrote:

Riccardo Romoli <ric.romoli@gmail.com> writes:

> Hi Michael,

Hi Riccardo,

> I tried your suggestion but nothing changed. I started a new emacs,
> cleared the tramp cache but again the same issue. I attached the log
> as you requested, hoping this could help. Let me know.

The log looks strange.

- It is incomplete. Did you really start with emacs -Q, and have sent
  the *whole* log?

- It contains helm backtraces. This makes it harder to analyze, so pls
  don't use helm for the test.

- It contains file notification activities. Pls don't activate them while
  testing.

- It doesn't show any remote process invocation. Did you start the
  remote lsp server?

- You didn't send me the steps how to produce the log. I've asked for
  this, in order to reproduce locally.

> Best regards, Riccardo

Best regards, Michael.

debug_tramp_ssh_erre_remote_lsp_texlab.log
Description: Text Data

my-specific-init.el
Description: Text Data