I have worked so far with a half-baked, unsatisfying #Python configuration for #emacs. I'm thinking of redoing it from scratch. I want the standard things, I guess: access to doc strings for the core's and project's entities, completion, and easy switching between venvs, …
Do you have a starting point you'd recommend?
=> More informations about this toot | More toots from eslr@mastodon.social
meanwhile… I stripped down my Emacs Python configuration to the very basic, using python-ts-mode, eglot with pylsp, and pyvenv. But I expect this basic setup to evolve
See my repo here https://github.com/larsen/emacs-configuration/blob/master/lisp/larsen-python.el (and https://github.com/larsen/emacs-configuration/blob/master/lisp/larsen-lsp.el)
=> More informations about this toot | More toots from eslr@mastodon.social
Related: https://olddeuteronomy.github.io/post/python-programming-in-emacs/ (via https://irreal.org/blog/?p=12676)
=> More informations about this toot | More toots from eslr@mastodon.social
@eslr I've had to tweak Doom Emacs very little out of the box, but it's a love it or hate it thing
=> More informations about this toot | More toots from bamboombibbitybop@mastodon.social
@eslr I have been planning the same for a while and my previous attempts bore no fruits. I hope this thread blows up with all sorts of solutions (that aren't yet another emacs flavor) :p
=> More informations about this toot | More toots from weepingclown@fosstodon.org
@eslr
I would be interested in this as well
=> More informations about this toot | More toots from deedend@fosstodon.org This content has been proxied by September (ba2dc).Proxy Information
text/gemini