News for hackers. Stuff that matters.

A comment on EmacsConf 2024 Notes. Parent comment

Re:EmacsConf 2024 Notes by throwup238 on Saturday December 28, 2024 @03:34PM (#42534402)
Depending on the language you use VScode might not be any more performant because it probably uses the same LSP on top of electron instead of elisp. I write Rust/C++ on a sizable project and since everyone depends on rust-analyzer* all IDEs are just unbearably slow and mostly useless in language integration beyond basic refactors and click to go to definition.

* except RustRover but that comes with its own set of issues

[ Parent | on HN ]
Re:EmacsConf 2024 Notes by arrsingh on Saturday December 28, 2024 @03:44PM (#42534523)
yes its rust. Looks like you're right. Well is back to good old emacs for me!
[ Parent | on HN ]
Re:EmacsConf 2024 Notes by throwup238 on Saturday December 28, 2024 @03:54PM (#42534632)
> I have way too much custom elisp to build and debug Rust/Go/C++

What kind of emacs scripts do you write to help debug Rust?

[ Parent | on HN ]
Re:EmacsConf 2024 Notes by arrsingh on Saturday December 28, 2024 @06:50PM (#42535989)
Nothing special or too sophisticated. On the one hand I use Just (a command runner) to standardize specific build and test commands that call cargo with various flags. Here is a simple example from one of my repos: https://github.com/deepmesa/deepmesa-rs/blob/mainline/justfi...

Then I have a bunch of elisp code that calls just and / or generates boilerplate code right in the buffer - M-x new-macro or M-x run-test (asks for a test to run) etc. I keep writing more elisp as I go along and add specific key bindings to specific things and now its too hard to move away from it all.

[ Parent | on HN ]