←back to thread

432 points tosh | 4 comments | | HN request time: 0.76s | source
Show context
tyoma ◴[] No.39995915[source]
I’ve used aider to understand new codebases using technologies I don’t know and it did a fantastic job; much faster than grep/find + google.
replies(1): >>39995997 #
fyrn_ ◴[] No.39995997[source]
To be fair in a world of good LSP impls, grep/find are really primative tools to be using. Not saying this isn't better then a more sophisicated editor setup, just that grep and find are a _really_ low bar
replies(4): >>39996106 #>>39996629 #>>39997312 #>>40027408 #
1. shadowgovt ◴[] No.39996106[source]
When we reach that world, let me know. I'm still tripping over a "python-lsp-server was simply not implemented async so sometimes when you combine it with emacs lsp-mode it eats 100% CPU and locks your console" issue.
replies(2): >>39996914 #>>39999527 #
2. skeledrew ◴[] No.39996914[source]
Wait, so this is why Emacs has been locking up on me in most of my Python projects??
replies(1): >>39997909 #
3. shadowgovt ◴[] No.39997909[source]
Possibly. Definitely why it has been locking up on me when I added lsp-mode.

Lsp-mode will schedule one request per keypress but then cancel that request at the next keypress. But since the python LSP server doesn't do async, it handles cancel requests by ignoring them

4. fyrn_ ◴[] No.39999527[source]
If emacs hard blocks on LSP requests, that may be on emacs as well. I recomemd you try ruff-lsp, although it does not iver everything and is more for linting, it's higb quality