Adam

This is complicated, as there could be a chain of these, and I'd have to rearchitect how it fetches things. Realistically, we don't know whether we need to fetch the...

Probably a lot easier, yeah. I'd be OK with that, I suppose.

``` adam@adam-ThinkPad-T15p-Gen-1:/tmp$ lpm --userdir . install lsp_typescript 2.3 MB [ 3.0 MB/s][100%]: Fetching https://github.com/lite-xl/lite-xl-plugin-manager.git:latest... 336.2 kB [ 3.1 MB/s][100%]: Fetching https://github.com/lite-xl/lite-xl-plugins.git:master... 44.3 kB [ 1.0 MB/s][100%]: Fetching https://github.com/lite-xl/lite-xl-colors.git:master... 24.9 kB...

Seems to work fine on my end, weirdly enough.

Seems like it's to do with auto-detecting your lxl install. If you don't have one, this fails. I'll have flagged core plugins as still core, even if they're not part...

Should be fixed by 0d153a3148382242ae2a71511664bb1a106b6fc5.

Should be fixed by https://github.com/lite-xl/lite-xl-plugin-manager/commit/259331a015432cfd47eb5c6161c6ddf05288a01c.

:+1:

For now, you can modify this kinda thing with the LITE_SCALE environmental variable, if it's out of whack for your system. Try `LITE_SCALE=1`. I think. EDIT: Or maybe `LITE_SCALE=2`? Try...

So, `init.lua` in the same directory isn't a way you can modify lite's behavior. Did you try just setting `LITE_SCALE` as an environment variable from the command line?