Spent my day configuring emacs....

@7root I sent with emacs because the vim modes thingy confuse me a lot and I keep typing commences into my actual buffer

I just use nano because I only use it to configure stuff

@c3ypt1c I used to do the same, but right now I'm working on a project which relies on a raspberry pi, and I got tired of git-ing every little code change just to be able to run them on the pi.

Now I use emacs (preconfigured using emacs-live) over ssh, nano just doesn't cut it for medium sized python/js programming.

Omg me too, finally get autocomplete running ... Feels so good!

@CptFox usually, for bigger projects, I work on my main machine (it's easier and faster than an RPi), use git for version control and then use SFTP to push changes all from main machine. Idk if this is bad practice but I've always done it this way.

TEAM NANO!!!

Me go with nano. Me like nano. Me not have to use nano much.

Nano. If I'm doing anything more than editing a config I'll use Notepad++ or VSCode.

I really use any of them these days. Long live configuration management systems.

Used Emacs as editor/IDE back in the day. Learning it really helps getting to know bash key bindings by the way. Still prefer it above all editors (not IDE) for big work (not quick change of a few lines to test song)
Now I mostly use vim (not vi unless it's not present) it starts fast, has syntax colouring and undo. (Protip use ZZ to save and exit and ZQ to about)

Spacemacs
/thread

@nhll T(h)ank. you.

This just saved me so much trouble when programming my pi remotely