I can't repro that, you mean that you updated lsp-mode or some package?

yeah, I guess so but I don't know which one 😢

I can try to update lsp-mode and check

updated lsp-mode and it's still working for me

weird

If you copied and pasted the settings that I pasted you the other day, you may have (setq flycheck-check-syntax-automatically '(save mode-enabled))? I think this makes flymake only actually run the linter when the file is saved?

that was terribly worded ... that's what I get for trying to type on slack during a meeting ... https://clojurians.slack.com/archives/C099W16KZ/p1700920735589559?thread_ts=1700910274.477479&cid=C099W16KZ ... that snippet sets flycheck to only check syntax on save, and I think that's how lsp-mode works? Does that make more sense?

@U0P0TMEFJ Ah so that was what was going on! I already wondered in #CPABC1H61 what got me into this new behavior! thanks!

undid this now

@U0P0TMEFJ Do you know what linter is used in this lsp server and how to configure it? I assumed it was eslint, but no matter how I configure things it doesn't work

in the js/ts lsp server?

I think I'm running eslint

yeah

what do you get when you run flycheck-verifiy-setup?

Syntax checkers for buffer index.ts<auth-service/src> in typescript-mode:

First checker to run:

  lsp (explicitly selected)
    - may enable: yes
    - may run:    t

Checkers that could run if selected:

  javascript-eslint  select
    - may enable:  yes
    - executable:  Found at /var/home/ed/bin/npx-eslint
    - config file: found

  typescript-tslint  select
    - may enable:         yes
    - executable:         Found at /var/home/ed/bin/npx-tslint
    - configuration file: Not found

Syntax checkers for buffer core.js in js2-mode:

First checker to run:

  lsp (explicitly selected)
    - may enable: yes
    - may run:    t

Checkers that are compatible with this mode, but will not run until properly configured:

  javascript-eslint (automatically disabled) reset
    - may enable:  no
    - executable:  Not found
    - config file: missing or incorrect

  javascript-jshint (automatically disabled) reset
    - may enable:         no
    - executable:         Not found
    - configuration file: Not found

  javascript-standard (automatically disabled) reset
    - may enable: no
    - executable: Not found

Flycheck Mode is enabled.  Use C-u C-c ! x to enable disabled checkers.

--------------------

Flycheck version: 33snapshot (package: 20230813.620)
Emacs version:    29.1
System:           aarch64-apple-darwin21.6.0
Window system:    mac

I am trying to suppress this one:

but no luck so far

perhaps this is some typescript thing

I didn't know about this flycheck feature, interesting

I have no idea where this warning is coming from

you can run flycheck-compile and it will ask for a linter to run

o ffff me:

// deno-lint-ignore require-yield
      

what is deno-lint

lol

dunno ... but I've heard of deno ... https://deno.com/ ... so something to do with that????

I not using deno...

I just installed whatever lsp server it asked me to, perhaps it's just that

how can I check this @UKFSJSM38 😆

maybe lsp-describe-session

yeah it's deno-ls

what do you get @U0P0TMEFJ?

there is lsp-uninstall-server and lsp-install-server

(in case you installed via emacs lsp-mode)

eslint + ts-ls ... they're written in my modeline

hmm I don't remember installing this server and it doesn't appear with lsp-uninstall-server

try list-process and check if you can find the path to that

ah it just runs deno ls maybe as a fallback?

I had deno installed. Anyway I can live with this

so it turns out that I have some things in my custom.el

'(flycheck-javascript-eslint-executable "~/bin/npx-eslint")

'(flycheck-typescript-tslint-executable "~/bin/npx-tslint")

npm i -g typescript-language-server typescript

cool ... and maybe I've done that in the past too? ... apologies for leading you astray

no worries!

but I tend to try and avoid installing things globally - I'm a contractor and have to work on lots of different people's code bases - so I spin up containers with podman for each client which lets me have many different dev envs on the same laptop (I use fedora silverblue which makes the whole thing a bit more straight forward 😉 )

yeah I totally get that

I don't know how to enable eslint via lsp

here on this page it says: https://emacs-lsp.github.io/lsp-mode/page/lsp-eslint/ lsp-eslint-enable but I don't get this command...

maybe a separate package to install?

https://github.com/emacs-lsp/lsp-mode/blob/a23433ae68c457f108de4e592df859ac005e1ecc/clients/lsp-eslint.el#L407 here is the function that checks that

I don't have any eslint packages installed

AFAICS there is a server to be installed via lsp-install-server eslint

got it:

👍

I don't use those server installations via lsp-mode as well (especially because I'm a nix user), but a nice idea would be to follow the nix approach and have a way to declare in your config the servers you want installed and lsp-mode just install/uninstall it automatically or so, then you will have a way to control what you want installed and what not in a declarative way (like nix)

yeah ... I've been looking at this https://www.jetpack.io/devbox/ ... it looks like it does what silverblue's toolbox does, but with nix? ... not got around to trying it yet though 😉

interesting, looks like a wrapper for nix in a more intuitive way perhaps

I spin up an container for each contract I'm working on ... but that includes emacs every time - so if I'm working on 2 different things I have 2 emacs servers running (and need to specify a socket for them to communicate on) ... but they share my emacs config dir - so sometimes I've run 2 different emacs versions with the same ~/.emacs.d/ and come across compilation problems where packages work in one but not the other ... it happens rarely but it's a pain when it does happen

I use this to isolate things atm https://docs.fedoraproject.org/en-US/fedora-silverblue/toolbox/ ... the nix approach that the devbox thing uses seems like it could be nicer

somehow I still don't get linting from eslint...

and on the command line it only complains about something which is valid:

const x = 10;

ah now it works after some init ceremony

woo!