Konto erstellenAnmelden

Frühere Suchanfragen

Keine früheren Suchanfragen

Suchoptionen

Nur verfügbar, wenn angemeldet.
social.anoxinon.de ist einer von vielen unabhängigen Mastodon-Servern, mit dem du dich im Fediverse beteiligen kannst.
Die offizielle Mastodon Instanz des Vereins Anoxinon e.V.

Verwaltet von:

Serverstatistik:

1,1 Tsd.
aktive Profile

social.anoxinon.de: ÜberProfilverzeichnisDatenschutzerklärung

Mastodon: ÜberApp herunterladenTastenkombinationenQuellcode anzeigenv4.3.7

#lsp

1 Beitrag1 Beteiligte*r0 Beiträge heute
Öffentlich
Pavel Korytov :emacs:☮️

A lot of trouble with the new #Vue #LSP.

First, it disables all other typescript LSPs, even if there is no Vue in the project; fortunately, this can be fixed with:

(setq lsp-volar-take-over-mode nil)

Maybe a better way would be to advise `lsp-volar--activate-p' to detect Vue by parsing package.json.

Second, somehow the server sends empty "textDocument/publishDiagnostics" messages about a second after sending one with diagnostics! As a result, the diagnostics appear for a second and then disappear.

For now, I've worked around that by advising `lsp--on-diagnostics' to ignore empty messages if they come less than five seconds after a non-empty one. Not sure where to go next with this.

The code: sqrtminusone.xyz/configs/emacs

Finally, the server sometimes crashes randomly. It happened once or twice today.

sqrtminusone.xyzEmacs configFreedom is a state of mind
#Emacs
Fortgeführter Thread
Öffentlich
Aral Balkan

So it does look like the TypeScript language server has a limit of 4MB source size where it disables type checking (and actually shows an erroneous error stating that exports that exist in the file do not exist) for files that are imported but not open in the current workspace/session.

Still not sure if this is documented anywhere or not (haven’t been able to find it, if it is).

99.99999% of the time, unless you’re doing niche stuff like I am, you won’t run into this.

Workaround: should you have such a large file, e.g., with a large generated object, try and refactor to split it up into multiple files and rejoin it a separate file. The actual object size/memory usage isn’t the issue, it’s the file size.

github.com/typescript-language

GitHubServer fails on import when exported object constant has too many entries/is too large · Issue #951 · typescript-language-server/typescript-language-serverVon aral
#TypeScript#max#lines
Öffentlich *
Aral Balkan

Hit an interesting limit in the TypeScript language server¹:

Looks like there’s a limit on the number of entries an object (constant) can have before the language server balks. Seems to hit it around 1,343.

(I’m generating an object for an icon library.)

Doesn’t appear to be related to file/memory size (breaking up the same number of entries into several objects works).

Anyone know what limitation exactly I’m hitting (if it’s documented somewhere?) Been searching but couldn’t find any reference to it.

¹ It’s definitely a language server limit as I tried in VSCode as well to rule out it being a limit in Helix Editor.

#TypeScript#limit#constant
Öffentlich *
shom ✊🏽🐧📷🤿🏔️🪚

Hey language/IDE nerds, check out Bablr-lang by @stirlhoss, I resonate with the mission

The BABLR organization's mission is to build a new ecosystem of next-generation developer tools to radically raise computer code literacy around the world. It aims to do this by creating a common "math-y" system for representing code to that unlocks new coding workflows for all developers while changing the way that language and tooling authors collaborate to deliver rich IDE functionality.

A lot of the specifics are a beyond my pay-grade but #LSP and #treesitter have really moved the needle in this space and I think innovation is better than a mono-culture. Love that people are making cool things, #bablr!

bablr.orgBABLRThe Bablr language
Antwortete im Thread
Öffentlich
data0

@hyde I've been using it for an hour and couldn't find any problems. As I understand it, the #LSP changes only provide additional interfaces and don't breaking existing ones. They are not aimed at making nvim-lspconfig obsolete either. It's just some plumbing moved to core, so that nvim-lspconfig can really be just about config. Which makes a lot of sense, because while it's gotten easier to manually set up LSPs in v0.11, it still a good idea to pool configs in a plugin. #neovim

Antwortete im Thread
Öffentlich
Fred

@bobidle Also aktiv, meinst du, und nicht nur mit einem automatisiert verschickten Crashdump und einer Zeile Fehlerbeschreibung dazu?

Mmh, zuletzt wäre das dann vermutlich mein MR vor 8 Monaten für #KDE #Kate, um den #Typst #LSP hinzuzufügen. (Ist das echt schon so lange her? Uff, vielleicht sollte ich mal prüfen, ob der überhaupt noch funktioniert und sich nicht in der Zwischenzeit etwas grundlegendes geändert hat.)

Öffentlich
Lukas Rotermund

Is there a good way to debug why the intelephense v1.14.3 LS on node v22.14.0 can't activate/check my valid license key in neovim v0.10.4/v0.11 on a fresh Debian? Works on other machines.

My simplified kickstart lua config:
```lua
local servers = {
....intelephense = {
........init_options = {
............licenceKey = 'some valid key',
........},
....}
}
```

The image show's symfonys kernel.php file opened in neovim. Below is a telescope (neovim plugin) modal visible, showing an error of the intelephense language server: "Your intelephense licence key could not be activated at this time. Please c..." the rest of the error is not visible within the picture.
#php#intelephense#lsp
Öffentlich
Heals :heart_nb:

Hey my fellow Helix users.. I’m at a loss here so help me out!

Is there any keybind to cycle LSP code completions for a method with multiple parameter versions like in C++?

Example:

QWidget->setFocus()

Gives me an auto-complete with one result:

setFocus() -> void (1/2)

How do I cycle through these two?
The normal tab/shift tab do nothing, neither does ctrl-p/n nor up/down

Code completion preview in helix, currently showing “setFocus() -> void (1/2)”
#helix#helixEditor#lsp
Öffentlich *
FediVerseExplorer

#MasterMe von @trummerschlunk@chaos.social @falktx@mastodon.falktx.com benutze ich seit es das gibt für meine Projekte fast immer. Vielen Dank für dieses #OpenSource Tool!
Manchmal ist aber hinten dran das #LSP #Clipper noch nötig. Besonders wenn es um Onlineaufnahmen mit suboptimalem Audiokonferenzequipment geht.
So auch bei der Vorbereitung dieser Tagung zur #Inklusion:
https://bildung.social/@komin/113803547189314869

#Audio #FX #DeBeSSZukunft #DeBeSSTagung

Screenshot der DAW Ardour mit geöffnetem Plugin Clipper
EntdeckenLive-Feeds
Über