#lsp

5 posts · Last used Aug 03

I'm happy to announce Badness: a formatter, linter, and language server for LaTeX! It is meant to be a all-in-one replacement for whatever texlab + latexindent/tex-fmt + chkex + bibtex-tidy setup you have going. The goal is to be a Ruff for LaTeX. The architecture is heavily inspired by rust-analyzer. Features include reflow and sentence wrapping, a curated set of chktex lint rules, and support for tex, sty, ins, and bib files. https://github.com/jolars/badness #texlatex #formatter #lsp #linter
1
0
1
0

We have our own blog now! We are breaking it in by re-sharing our New Year's post from another platform. Check it out if you had not read it and browse our site while you are there to learn more about us and what we can do for you.

New Year, New Endeavors: RSI Hosting, Recording, and Tech Support 🐙📖 https://www.traducoop.com/blog/new-year-new-endeavors-rsi-hosting-recording-and-tech-support

#WorkerOwned #LSP #RSI #VRI #Interpretation #LanguageAccess #LanguageJustice #PuertoRico #MastodonPR #CooperativasPR

3
0
4
0
Imagine a protocol like #LSP, but for adding real-time collaboration to existing text editors. It would allow #Neovim to edit a #Hedgedoc, or peer-to-peer pair programming between #VSCode and #Emacs! We've come up with our own little protocol like that (for Teamtype), but we'd like to open up the discussion: That's why we're inviting everyone interested to an initial online gathering on Feb 26, 19:00 UTC, to gauge interest for working on a protocol like this together! https://md.ha.si/collaborative-editing-protocol
183
14
158
2
You've seen all posts