Live data from Hacker News

Lem: Emacs-like editor written in Common Lisp

lem-project.github.io

21–30 of 62 posts

Re: Lem: Emacs-like editor written in Common Lisp

#21
post #3

Has anyone used this? I was just thinking the other day that it would be nice to have an emacs-like editor written in such a way that it made performance and parallelism easier, especially around multithreading. A real killer feature would be some kind of emacs-lisp compatibility layer so that you could load existing third-party emacs modules, but I imagine the complexity of that is so off the charts that it would be…

Emacs is pretty snappy these days, what kind of performance problems are you seeing with it?

Emacs is snappy in the terminal with the tui version while the gui versions are still really slow for me. Hopefully someone will make a fast frontend with GPUI or something because the lisp engine is certainly fast enough these days

Re: Lem: Emacs-like editor written in Common Lisp

#23

Has anyone used this? I was just thinking the other day that it would be nice to have an emacs-like editor written in such a way that it made performance and parallelism easier, especially around multithreading. A real killer feature would be some kind of emacs-lisp compatibility layer so that you could load existing third-party emacs modules, but I imagine the complexity of that is so off the charts that it would be…

>Has anyone used this? I have, it's awesome. There are some rough edges and some niceties/third party packages from emacs that I missed, so I ended up going back, but lem is very promising.

> niceties/third party packages from emacs that I missed

Was it magit?

Re: Lem: Emacs-like editor written in Common Lisp

#24

Earlier quoted context omitted.

>Has anyone used this? I have, it's awesome. There are some rough edges and some niceties/third party packages from emacs that I missed, so I ended up going back, but lem is very promising.

> niceties/third party packages from emacs that I missed Was it magit?

It’s always magit

Re: Lem: Emacs-like editor written in Common Lisp

#25

Earlier quoted context omitted.

>Has anyone used this? I have, it's awesome. There are some rough edges and some niceties/third party packages from emacs that I missed, so I ended up going back, but lem is very promising.

> niceties/third party packages from emacs that I missed Was it magit?

Lem has Legit. While missing some features, it works well enough for the daily add/stage/commit loop that makes up 90% of my git commands. It also uses less git commands so it's a fair bit snappier than Magit on large repos.

I can see the lack of org-mode being a dealbreaker for some, but I personally use markdown for my notes/docs so no issue there.

Re: Lem: Emacs-like editor written in Common Lisp

#26

Has anyone used this? I was just thinking the other day that it would be nice to have an emacs-like editor written in such a way that it made performance and parallelism easier, especially around multithreading. A real killer feature would be some kind of emacs-lisp compatibility layer so that you could load existing third-party emacs modules, but I imagine the complexity of that is so off the charts that it would be…

Yes I'm waiting for a nixos package. I have used it a bit through the Docker image and it's super cool. I can see it succeeding emacs. Seems like it's even more hackable than the latter, since it's all written in Common Lisp (there's no C core).

Re: Lem: Emacs-like editor written in Common Lisp

#27
post #20

Earlier quoted context omitted.

Okay, well either way, the UX is atrocious.

What is it that bothers you about the UX?

> would never describe it as snappy. The entire thing is single threaded so the UI locks up at the slightest provocation

This part seems to be about the User eXperience. (which I agree with, but elisp can start child processes and wait for the results asynchronously, so this is the fault of whoever wrote the code https://www.gnu.org/software/emacs/manual/html_node/elisp/Ou... )

Re: Lem: Emacs-like editor written in Common Lisp

#30
I'm watching it with attention but some stuff is concerning:

* Some binaries in the source tree like https://github.com/lem-project/lem/tree/main/extensions/term...

* Commit messages aren't really descriptive.

* PRs and issues lingering in the void.

* Working around the strange inferior process thing (cf https://github.com/lem-project/lem/issues/1076) that could be replaced by uiop:launch-program when a tty/pty isn't needed; still no LSP in c-mode, and forget C++, obviously.

Well, let's be honest, it's very interesting but still a one-man effort, as far as the core editor goes, so these are pretty normal.

Post reply on HN