deno_std
lsp-mode
deno_std | lsp-mode | |
---|---|---|
17 | 118 | |
1,038 | 4,669 | |
- | 0.6% | |
0.0 | 9.3 | |
over 4 years ago | 3 days ago | |
TypeScript | Emacs Lisp | |
MIT License | GNU General Public License v3.0 only |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
deno_std
- Ask HN: Where do I find good code to read?
-
[Showcase] My first project in Deno and an early perspective
For reference (for the issues you mentioned): 1. This issue was opened almost immediately to solve the weird .only function not working https://github.com/denoland/deno_std/issues/2979 2. That looks weird to me, will get back to you on this one since it should work I think 3. Generally polluting the global namespace isn't great, but because we're only polluting the namespace of a module (and we choose what parts to import), I personally find it quite freeing. I entirely understand how that might feel awkward. 4. you CAN specifying only writing to certain directories! --allow-write=/path/to/dir would allow that!
-
Deno v1.27
At least for the ones related to trees, it's just a renaming. Below is a link to the PR. When I initially implemented these trees, I chose the names BSTree and RBTree to keep the names short. I'm guessing the person that proposed renaming them did so to make it more obvious what they are.
https://github.com/denoland/deno_std/pull/2400
The standard library is separate from the runtime. It wouldn't break backward compatibility if you were to update. For example, if you were importing RBTree and upgraded Deno to the latest release, it would keep working just fine. You would only really need to switch to using RedBlackTree instead if there was a change made to it that you wanted.
I think the only time you would need to update your standard module imports to be able to use newer versions of the Deno runtime if the standard module were depending on runtime APIs that have a breaking change.
-
No Safe Efficient Ways to Do Three-Way String Comparisons in Go
It is like Demo deprecating fs.exists().[1]
[1]https://github.com/denoland/deno_std/discussions/2102
-
Programming language comparison by reimplementing the same transit data app
This was fun to read through.
I would need to profile the code, but the startup time being bad for Deno seems like maybe a combination of the code in here being unoptimized:
https://github.com/denoland/deno_std/blob/0ce558fec1a1beeda3...
(Ex. Lots of temporaries)
And usage of the readFileSync+TextDecoder API instead of readTextFile (which is also a docs issue since it's suggests the first one). It seems the code loads the 100MB into memory, then converts to another 100MB of utf8, then parses with that inefficient csv decoder. The rust and go versions look to be doing stream/incremental processing instead.
-
How do I check if a file doesn’t exist?
But it there's some talk to reconsider it
- JSWorld Conference 2022 Summary - 1 June 2022 - Part I
-
Testing frameworks
Sorry to hear that. I want to provide expect API in deno_std in the future: https://github.com/denoland/deno_std/issues/1779
-
Just migrated my first module from Node to Deno: Froebel - a strictly typed TypeScript utility library.
I just migrated the module to Deno and rewrote the test cases using the Deno test runner. Also contributed a bug fix to the test runner that I encountered during the migration. An npm version is still available and automatically generated from the Deno code via a small bash script (rewriting imports, adding an index.ts, etc.).
-
Deno.js in Production. Key Takeaways.
Much of Node.js is written in C, yet it's still called Node.js.
Deno has some JavaScript/TypeScript in it. On GitHub https://github.com/denoland/deno is 22.8% JavaScript and 13.2% TypeScript, and https://github.com/denoland/deno_std is 68.2% JavaScript and 31.6% TypeScript.
So to me it's misleading about the name, but not about what Deno is written in.
lsp-mode
- lsp-mode: Emacs client/library for the Language Server Protocol
-
lsp-keymap-prefix not working
I also tried to the solutions suggested ![here](https://github.com/emacs-lsp/lsp-mode/issues/1532) and ![here](https://github.com/emacs-lsp/lsp-mode/issues/1672), but nothing worked. I moved the (setq lsp-keymap-...) line outside (and before) use-package. I also used :config (define-key lsp-load-map...) in my use-package block. But none of them worked.
-
Help getting the yaml language server working with eglot
Not sure how much this might help, but lsp-mode has lsp-yaml-select-buffer-schema and lsp-yaml-set-buffer-schema commands to pick schema from a list or set from a URI. Checking the source of them might give some hints about how the same could be implemented in eglot?
-
What LaTeX setup do you use?
Beyond that you might as well embrace the suck and install autex with a language server: https://emacs-lsp.github.io/lsp-mode/
-
Emacs bankruptcy
Smart completion these days is done primarily through LSP. eglot is fairly minimal but built-in as of 29, also available via GNU Elpa. lsp-mode is another option with more integrations and a bit more fleshed out.
-
The bottom emoji breaks rust-analyzer
lsp-mode: https://github.com/emacs-lsp/lsp-mode/issues/2080
-
Setting up a fundraiser for multi-threaded Emacs, any thoughts on this?
Are you running emacs-29? It has numerous speed-ups compared to emacs-28 and older versions, many of them coded by Mattias Engdegård, e.g. commit def6fa4246. I have a fresh build of emacs-29 running on Linux and a new mac with an M1 CPU, and it's stupid fast. I don't use the native-comp feature. I rarely notice any hesitation or slowness. I don't use Elpy. I do use lsp mode.
-
Newbie here! Need Help!
Since you are doing code development, the first things to go for would be setting up your emacs packaging (installing use-package and melpa (use-package's documentation covers this) so you have more packages to choose from (do be careful to not just pick things willy nilly but research them a bit first)) and then setting up lsp-mode. lsp-mode lets you use LSP servers for the specific programming languages you work with in a somewhat unified fashion. You then need to install and setup the LSP servers for the languages you use, and possibly install language specific Emacs packages as support (note, Emacs has builtin functionality for many).
-
Emacs 29: Install Tree-Sitter parser modules with a minor mode
And first of all, I'm trying to understand, how is it connected to https://github.com/emacs-lsp/lsp-mode? I'm sure, that existed lsp implementations already parse source code. Why TreeSitter?
What are some alternatives?
fp-ts - Functional programming in TypeScript
eglot - A client for Language Server Protocol servers
froebel - A strictly typed utility library.
tide - Tide - TypeScript Interactive Development Environment for Emacs
Refactoring-Summary - Summary of "Refactoring: Improving the Design of Existing Code" by Martin Fowler
ctags - A maintained ctags implementation
clara-rules - Forward-chaining rules in Clojure(Script)
ANTLR - ANTLR (ANother Tool for Language Recognition) is a powerful parser generator for reading, processing, executing, or translating structured text or binary files.
intellij-lsp-server - Exposes IntelliJ IDEA features through the Language Server Protocol.
dap-mode - Emacs :heart: Debug Adapter Protocol
LavaMoat - tools for sandboxing your dependency graph
company-lsp - Company completion backend for lsp-mode