emacs
emacs-async
emacs | emacs-async | |
---|---|---|
11 | 24 | |
67 | 823 | |
- | - | |
0.0 | 6.2 | |
3 months ago | about 2 months ago | |
Emacs Lisp | Emacs Lisp | |
GNU General Public License v3.0 only | 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.
emacs
-
The Good, The Bad, and The Ugly
The ugly: Handling JSONRPC synchronously. Now that eldoc is in core emacs, LSP is officially supported by core emacs but from this branch https://github.com/emacs-lsp/emacs/tree/json-rpc-29 it looks like core emacs still handles JSONRPC synchronously and blocking.
- emacs: Mirror of GNU Emacs
-
is it just me, or LSP mode is very slow in emacs?
Without perf profile, it is hard to say. For starters, you may remove lsp-ui. After this: https://emacs-lsp.github.io/lsp-mode/page/performance/ it should be good enough for most use usecases. If you want blazingly fast lsp-mode, you need the LSP Emacs fork https://github.com/emacs-lsp/emacs which is another beast(see https://www.reddit.com/r/emacs/comments/ymrkyn/async_nonblocking_jsonrpc_or_lsp_performance/ as well).
-
How do I improve Emacs as a Typescript IDE
https://emacs-lsp.github.io/lsp-mode/page/performance/ . If this doesn't do, then https://github.com/emacs-lsp/emacs
-
Emacs 29 is at least several weeks away
The other major performance boost is if you're using lsp-mode and this fork. And an lsp-server that sends waaay too much info, I guess.
-
Is lsp volar extremely slow or is it just me?
lsp-mode is async, but sending the messages. If the server is busy and not reading the input messages then lsp-mode will block. The only way ATM to avoid the issue is to use https://github.com/emacs-lsp/emacs .
-
My IDE is too heavy so I moved to Emacs
I disagree. When I am running a compilation (with output being dumped into a visible buffer) + query magit for large commit. Over tramp. Things noticeably freeze. Technically it all is async. Practically, it is implemented as polling things on main thread with some witing happening in non-async fashion.
> For example, querying your compiler for a list of methods that apply to the current object, or a list of functions that start with “Foo” are mostly moving to external processes using LSP as the communication protocol.
That's why we have lsp-bridge and lsp-mode emacs fork :) Both of which build some infrastructure to avoid doing communication work with lsp-mode work in main emacs thread. So, heavy emacs users are building some async machinery which wraps another already async and relatively lightweight protocol, because core emacs facilities can't keep up with it. Architecturally it is kind of insane.
I think, lsp-mode fork is doing the right thing (from practical POV; it goes against "emacs is just an elisp interpreter" ideology though) and hope it gets into core at some point. A better solution would have being having first class async and background threads support at the elisp level. Which would never happen due to elisp messiness.
https://github.com/emacs-lsp/emacs
-
Emacs 29 is nigh What can we expect?
Locks: https://www.gnu.org/software/emacs/manual/html_node/elisp/Mu...
Semaphores are not there, my mistake; I was thinking about: https://www.gnu.org/software/emacs/manual/html_node/elisp/Co...
That's basically what every other threading library provides in most languages... and it's also what was shown time and again to be very hard to work with directly. Higher-order abstractions are necessary to make parallelism safe and concurrency convenient.
> and atomicity is guaranteed apart from when you use these calls. So you'd never be in a problem state of `setq` failing halfway, for example.
That's true - it looks like Emacs uses a global lock to ensure the atomicity, similarly to what Python does. Also like in Python, you can release that lock from native code (module or core). You cannot touch any interpreter state from other threads, so you need a bit of plumbing to get the results back, but it's possible. I found this: https://github.com/emacs-lsp/emacs/blob/json-rpc/src/json.c very interesting: it's a fork that moves JSONRPC from Lisp to C and out of the main thread. See for example line 1109 and related.
> but threads are pretty useful already if hard to code with.
That's the point: the capabilities are there (mostly), but abstractions are not. Coding with threads, even in the presence of the global lock, is hard, and ensuring correctness is nontrivial. At the very least we should get channels for communication (share by communicating, don't communicate by sharing) between threads and thread pools for executing tasks (like futures in Java or Python, or Task in Elixir). Threads and locks are way too low-level for normal coding. I suspect that's the reason why they're not used more widely, even though they're there for the third(?) release now.
Aside: Racket is actually a nice example of concurrency and parallelism being treated as completely separate concerns. IIRC threads in Racket are call/cc-based green threads, while places are separate instances of the VM that execute in OS-level thread or separate process. Threads provide concurrency and places provide parallelism. It's actually a good thing, I think. Mixing the two is often a major source of errors. Racket also has futures, which are parallel-if-possible primitives that can benefit from parallelism if they don't touch external state - a sort of a middle ground.
In any case: yes, Elisp threads are a good addition to the language, but they alone are not enough to bring concurrency to the masses, so to speak. As a concurrency primitives, and compared to callbacks, they have few advantages and some serious downsides. Emacs still needs a lot of work on the concurrency front. And don't even mention parallelism, that's another can of worms that we don't really need to open :)
-
Async non-blocking JSONRPC (or lsp performance faster/comparable with other clients)
In order for that to work, you have to use the json-rpc branch from here: https://github.com/emacs-lsp/emacs .
emacs-async
- emacs-async: Simple library for asynchronous processing in Emacs
-
Is there any way to run an emacs function as a separate process?
That is probably the simplest option possible; but if you need non-blocking evaluation, async package is definitely a better option.
-
Is it possible for Emacs Lisp to get something like multiprocessing from Python?
You already can. Using https://github.com/jwiegley/emacs-async or https://github.com/chuntaro/emacs-promise.
-
How to turn sequential computation into parallel computation in Elisp?
IMO the best option currently is async by Wiegley. It will manage Emacs instances for you and do all the low-level synchronization and messaging for you, so you can work in higher level abstractions as if you are working with threads.
-
Asynchronous alternative to xref?
Have you checked the async package?
-
Lsp-Bridge, Not Even Wrong
That is quite normal thing to do. Have you not seen Emacs Async? Take, a look, it is a useful thing. Or Emacs Request. Since Emacs does not have proper thread scheduler, that is the best next thing you can do.
-
[ANN] Blamer 0.6.0 released. Added pretty avatar preview
There are ways to avoid this, have you tried e.g. https://github.com/jwiegley/emacs-async ?
-
Video Series: Denote as a Zettelkasten
As a note about the third video, and searching for backlinks; the volume, when you get there, might be a slow-down when you work with many small files, like searching for backlinks. Each note means a separate file access, search process, etc. It is much more efficient for computers to read one big file, then many small files, and then just use Emacs to search in that file. If you are a developer of Denote, you might wish to look at asynchronous processes or perhaps use Wigleys Async package to search for backlinks asynchronously.
-
Setting up a fundraiser for multi-threaded Emacs, any thoughts on this?
Async process can do that. Have you checked async library by Wiegley? You can use another emacs process as a sort of clean interpreter thread similar to javascript workers.
-
My IDE is too heavy so I moved to Emacs
That "99% of standard usage" is the kicker, isn't it? Those greybeards who always opposed multithreading since long ago tend to say that the remaining 1% of use cases is best done in an external process, ideally not even written in Emacs Lisp, so that the rest of the open source community can benefit, like the GNU Global you mention. I suppose if you still want that program to be written with Emacs Lisp, you could use async.el (https://github.com/jwiegley/emacs-async/) and there's finally an use-case for the threads: it'll be relatively safe to run those 16 threads only in the external Emacs-process.
What are some alternatives?
lsp-bridge - A blazingly fast LSP client for Emacs
ranger.el - Bringing the goodness of ranger to dired!
homebrew-emacs-plus - Emacs Plus formulae for the Homebrew package manager
Taskflow - A General-purpose Parallel and Heterogeneous Task Programming System
toggleterm.nvim - A neovim lua plugin to help easily manage multiple terminal windows
esxml - An elisp library for working with xml, esxml and sxml.
codelite - A multi purpose IDE specialized in C/C++/Rust/Python/PHP and Node.js. Written in C++
Thrust - [ARCHIVED] The C++ parallel algorithms library. See https://github.com/NVIDIA/cccl
telega.el - GNU Emacs telegram client (unofficial)
org-yaap
lsp-mode - Emacs client/library for the Language Server Protocol
oneTBB - oneAPI Threading Building Blocks (oneTBB)