home.social

#languageserver — Public Fediverse posts

Live and recent posts from across the Fediverse tagged #languageserver, aggregated by home.social.

  1. I have just released version 1.0.0 of ESR: an R tree sitter mode for #emacs

    It is the first version independent of #ESS although tree sitter can be paired with ESS.

    ESR's interaction mode can use comint or #vterm The second one plays well with #radian Coding tools for now are supported by R's package #languageserver and can be connected with #eglot

    A big step for the #rstats users of Emacs

    codeberg.org/teoten/esr

  2. "[Helix] Spellchecking in Git commits with Harper"

    blog.skyplabs.net/posts/helix-

    "Unlike Vim, Helix doesn't include a spell checker natively. However, Helix has built-in support for LSP, which makes it easy to pair it with an LSP-based spell checker such as Harper. All you need is tweaking a bit your languages.toml Helix configuration file as explained in the official documentation."

  3. "[Helix] Spellchecking in Git commits with Harper"

    blog.skyplabs.net/posts/helix-

    "Unlike Vim, Helix doesn't include a spell checker natively. However, Helix has built-in support for LSP, which makes it easy to pair it with an LSP-based spell checker such as Harper. All you need is tweaking a bit your languages.toml Helix configuration file as explained in the official documentation."

    #Helix #Vim #LSP #LanguageServer #Harper #SpellChecking #Linux #Git #GitCommit #VCS #Dotfiles

  4. "[Helix] Spellchecking in Git commits with Harper"

    blog.skyplabs.net/posts/helix-

    "Unlike Vim, Helix doesn't include a spell checker natively. However, Helix has built-in support for LSP, which makes it easy to pair it with an LSP-based spell checker such as Harper. All you need is tweaking a bit your languages.toml Helix configuration file as explained in the official documentation."

    #Helix #Vim #LSP #LanguageServer #Harper #SpellChecking #Linux #Git #GitCommit #VCS #Dotfiles

  5. "[Helix] Spellchecking in Git commits with Harper"

    blog.skyplabs.net/posts/helix-

    "Unlike Vim, Helix doesn't include a spell checker natively. However, Helix has built-in support for LSP, which makes it easy to pair it with an LSP-based spell checker such as Harper. All you need is tweaking a bit your languages.toml Helix configuration file as explained in the official documentation."

    #Helix #Vim #LSP #LanguageServer #Harper #SpellChecking #Linux #Git #GitCommit #VCS #Dotfiles

  6. Eclipse Fun:

    1. Language server jdtls code formatting: needs XML file exported from eclipse.
    2. Command line JavaCodeFormatter (help.eclipse.org/latest/index.) wants a properties file for -config

    I used

    xq <eclipse-formatter.xml | jq -Mr '.profiles.profile.setting[] | ."@id" + "=" + ."@value"' >config.props

    and all worked but the indent with spaces. It used tabs. Reason:

    - XML export uses value="SPACE"
    - the property file needs ...=space

    🤦‍♀️

    #java #eclipsejdtls #codeFormatter #languageServer

  7. Maybe this #ProofOfConcept is useful for your, if you do #Jenkins pipeline scripts, but your editor doesn't have a proper plugin to validate these scripts.

    github.com/hasselmm/JenkinsLan

    #LanguageServer #QtCreator

  8. What's not to like about eclipse-jdtls. It works just great with Emacs Eglot, except when it does not:

    "Workspace restored, but some problems occurred.\nnull"

    Result: the server does not provide any errors.

    What can be more infuriating than no error message at all? An error message like this: "na na nana na, I know there is a problem but I won't tell you!"

    #emacs #eglot #eclipsejdtls #languageserver

  9. Ah, finally, the Elixir community has an "official" language server—because nothing screams #innovation like adopting a protocol from 2016. 🔮 Meanwhile, GitHub's marketing team is busy slapping "AI" on everything, hoping you'll forget they just recycled last month's #buzzwords. 🤖✨
    github.com/elixir-lang/expert #ElixirCommunity #LanguageServer #GitHubAI #HackerNews #ngated

  10. 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

    #TypeScript #max #lines #memory #constant #object #import #bug #issue #LSP #languageServer #HelixEditor #VSCode #JavaScript #microsoft #workaround

  11. 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 #object #languageServer #LSP

  12. 🤔 Looks like I have to write a free, open source PHP language server myself - without php and Javascript of course. PHP really is still an awkward language for professional, modern development... Pity.

    #php #intelephense #languageServer #lsp #neovim

  13. Out of , full. What could be the reason? Did I go overboard with Firefox tabs? Too many QtCreators? A multitude of open consoles and documents?

    Nope. It's stray processes eating 15GiB. Or maybe it's 's fault?