Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Add Nu LSP support #6369

Closed
1 task done
Tom-Boscher opened this issue Nov 15, 2023 · 1 comment
Closed
1 task done

Add Nu LSP support #6369

Tom-Boscher opened this issue Nov 15, 2023 · 1 comment
Labels
enhancement [core label] language An umbrella label for all programming languages syntax behaviors potential extension Functionality that could be implemented as an extension (consider moving to community extensions) unsupported language

Comments

@Tom-Boscher
Copy link
Contributor

Check for existing issues

  • Completed

Language

Nu

Tree Sitter parser link

No response

Language server link

https://www.nushell.sh/blog/2023-11-14-nushell_0_87_0.html

Misc notes

Nushell now provide a LSP using nu —lsp.
It’s still in early stage but they write an example for a configuration for Neovim:

configs.nulsp = {
    default_config = {
        cmd = { "nu", "--lsp" },
        filetypes = { "nu" },
        root_dir = function(fname)
            ...
        end
    },
}
@Tom-Boscher Tom-Boscher added admin read Pending admin review enhancement [core label] language An umbrella label for all programming languages syntax behaviors potential extension Functionality that could be implemented as an extension (consider moving to community extensions) triage Maintainer needs to classify the issue unsupported language labels Nov 15, 2023
@JosephTLyons JosephTLyons removed triage Maintainer needs to classify the issue admin read Pending admin review labels Nov 17, 2023
@JosephTLyons
Copy link
Collaborator

Hey @Tom-Boscher, this will be going out with today's preview release (v0.115.0-pre).

@JosephTLyons JosephTLyons transferred this issue from zed-industries/community Jan 24, 2024
mikayla-maki pushed a commit that referenced this issue Mar 6, 2024
@JunkuiZhang
Update mio (#8935)
59faef5 
### Description
This is a part of #8809 

Update mio from 0.8.8 to 0.8.11.

When using named pipes on Windows, mio will under some circumstances
return invalid tokens that correspond to named pipes that have already
been deregistered from the mio registry. The impact of this
vulnerability depends on how mio is used. For some applications, invalid
tokens may be ignored or cause a warning or a crash. On the other hand,
for applications that store pointers in the tokens, this vulnerability
may result in a use-after-free.

### Connections

[named-pipes: fix receiving IOCP events after deregister
#1760](tokio-rs/mio#1760)

[Windows Named pipes invalid memory access
#6369](tokio-rs/tokio#6369)


Release Notes:

- N/A
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
enhancement [core label] language An umbrella label for all programming languages syntax behaviors potential extension Functionality that could be implemented as an extension (consider moving to community extensions) unsupported language
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@JosephTLyons @Tom-Boscher