Debacle#Emacs users typically do not run Emacs on a remote host. It's not necessary. We can edit remote files on our local Emacs instance, thanks to #TRAMP. Which allows things like #ediff two configuration files on two remote servers. We can locally #bookmark remote files, if we need to access them more than once. We can use #dired (file management) and #magit (version control) on remote machines, in a fully transparent way.
Dave Marquardt
bignose@PvN
> #Emacs config for working with #Python
* #EditorConfig for seamless project-specific configuration of basic text editing rules, that every modern text editor can obey.
* The default 'python-mode' is fine.
* #Eglot for #LSP enhances that. Follow Eglot documentation to set up for Python.
* #Magit for excellent Git porcelain.
* 'pyvenv-mode' to detect and activate Python virtualenv in a project.
I wouldn't want to directly use the Git plumbing (its awkward command line interface), when there are excellent porcelains like #Magit.
That depends on #Emacs, but doesn't depend on a GUI. You might have something similar that works with #Vim, @ahasty.
Agreed that a terminal window can work fine as an IDE.
Ashish Panigrahi
slackline :emacs: :orgmode:@alcarney Not an `eshell` solution but if you are looking to use `jj`from Emacs you might be interested in Majutsu, particularly if you used and liked Magit as it claims to be "Magit for Jujutsu"
Marcus Kammer
@bashbunni #Magit is so good, I have recommended developers learn #Emacs solely on the strength of how much they will enjoy https://magit.vc/
Thank you @tarsius!
Jonathan Lamothe