luals / luals.github.io Goto Github PK

They move so fast I can't really take in what they are showing.

Ideally there would be some way to pause these. (I've looked around for a Firefox extension to do this but couldn't find one).

But yeah - Animated GIFs aren't really ideal for this kind of thing.

Right now it is pretty impossible to tell the difference between a group and a diagnostic when not referring to the outline:

How are you using the lua-language-server?

Other

Which OS are you using?

Windows

What is the issue affecting?

Other

Expected Behaviour

workspace.checkThirdParty docs says "Whether addons can be automatically detected and applied" which sounds like it would automatically configure third party libraries for me.

Actual Behaviour

But the check3rdByWords looks like it never automatically changes configuration. It always prompts the user if it finds a relevant add-on:

https://github.com/LuaLS/lua-language-server/blob/63211177f8f3ad2a50dca3ab2ccaae737486813c/script/library.lua#L520-L593

I want "automatic configuration" behaviour, but I don't want "prompt me every time I open my project" behaviour.

Reproduction steps

1. Use vim with vim-lsp-settings and :LspInstallServer sumneko-lua-language-server to setup vim with LuaLS
2. Open a lua file
3. Get prompted with "Do you need to configure your work environment as LÖVE?" (#679)
4. try configuring luals to use 'runtime': { 'version': 'Lua 5.4'}, which is not love (love uses luajit)
5. restart vim and Open a lua file
6. Get prompted with "Do you need to configure your work environment as LÖVE?"

Additional Notes

I think the documentation is incorrect and instead should read:

Whether LuaLS should detect and request to enable addons automatically. Addons can set up the environment to be as close as possible to your target runtime environment. To manually configure addons, set their path with workspace.userThirdParty and select them with workspace.library.

I'm not sure that last sentence is correct.

Log File

No response

translations.mdx

| [zh-cn] | Chinese - People's Republic of China |
| [zh-tw] |           Chinese - Taiwan           |

为什么要用”People's Republic of China“代表简化汉字，而”Taiwan“代表**传统汉字？我们明明有更加准确和政治中立的名词区分这两个概念：Chinese Simplified，Chinese Traditional。

Why use "People's Republic of China" for simplified Chinese characters and "Taiwan" for traditional Chinese characters?
We clearly have more accurate and politically neutral terms to distinguish between these two concepts: Chinese Simplified, Chinese Traditional.

Attach Debugger

I think there are a few things that could benefit from greater clarity in order to avoid unnecessary confusion & frustration when trying to get the debugger to work. I spent a bit of time going round in circles, due to the following misunderstandings. A lot of these may seem obvious, but when it isn't working, one can end-up trying to fix things in the wrong place/s.

1. Install actboy168.lua-debug: Your doc links to actboy168.lua-debug, which in-turn has detailed instructions for building & installing, which allows for some confusion. I think it should be made clear to install the extension via VSCode only - with no need for any other installation steps.

2. Debug Host: is referred to as the language server within: ... /.vscode/extensions, it should really indicate that it should be the server folder within the language server: i.e. ... /.vscode/extensions/<sumneko.lua-*******>/server

3. Copy .vscode/launch.json into Debug Host: Similarly it should be made clear that launch.json should be placed in a .vscode folder inside the server folder

4. Open the Run and Debug sidepanel ... : This instruction follows one relating to the Debug Target, and as such implies that it also relates to the Target, whereas it relates to the Debug Host. So that should be made clear.

5. Finally - I found that I needed to Restart the Debug Target after the the Debug Host was up and running / debugging - not before.

workspace.supportScheme was removed in v3.6.8 as pointed out by @checkraisefold.

Need a guide to help users with contributing to the project

A link somewhere on the wiki article pages to the source MDX would be nice so that users can more easily make edits.

The method currently used for describing how to use annotations can be easy to understand at times:
---@type <type>

And also impossible for mere mortals to understand:
---@cast <value_name> [+|-]<type|?>[, [+|-]<type|?>...]
---@overload fun([param: type[, param: type...]]): [return_value[,return_value]]

There must be a better way to represent these more complex syntaxes while also not using symbols regularly in use (<, >, (, ), [, ], {, }, @, #, -, +, =, :, ", ,, ., ?). Although now that I have listed some in-use symbols, I realize we really are quite limited. It is hard to explain a syntax that uses many symbols… using symbols.

I'm open to any suggestions on how this can be improved 🙂

Plugins.md

Right now, the list of contributors to the wiki are grabbed client-side. Really, there shouldn't be any contributions to the website that don't trigger a new build and deploy, so we can get and render the list at build time.