LuaLS / LuaLS/lua-language-server

[Enhancement] Create cache in a user directory

Open
#2,676 2 comments 17 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Lua
Stars
4.4k
Forks
442
PR merge metrics
No merged PRs in 30d

Description

### How are you using the lua-language-server?

Neovim

### Which OS are you using?

Linux

### What is the issue affecting?

Other

### Expected Behaviour

`lua-language-server` should create the cache directory on the user's home directory. On Linux this should be in `~/.cache/lua-language-server/` ideally.

### Actual Behaviour

`lua-language-server` fails to start because it attempts to create the cache directory in a system directory which a regular user doesn't have permissions to write to.

### Reproduction steps

1. Download `lua-language-server-3.9.1-linux-x64.tar.gz` and extract it to `/opt/lua-language-server/`
2. Make sure the owner of `/opt/lua-language-server/` is `root:root`.
3. Execute `/opt/lua-language-server/bin/lua-language-server --help`
4. See error: `lua-language-server: create_directories: "/opt/lua-language-server/log/cache/40815": (generic:13)Permission denied`

### Additional Notes

_No response_

### Log File

_No response_

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Begin with the `/opt/lua-language-server/bin/lua-language-server --help` reproduction and trace where the `log/cache/40815` path is selected. Verify that the cache is created under `~/.cache/lua-language-server/` for a regular Linux user, then rerun the documented startup steps without permission errors.

Written by the indexing model from the issue text.

Assessment

Tech stack
linux, lua, neovim
Domain
operating-systems, tooling
Issue type
Feature
Difficulty
3/5
Estimated time
1-2 days
Activity status
Quiet
Clarity
Mostly clear
Newbie friendliness
48/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.