sevvie Rose 🈲Sep 6, 2018
@puffinux Hm. Looks fun.

Programs I use with my #linux (#archlinux) machines:

#GNOME3 (display mgr)
#Brave & #FirefoxNightly (browser, image viewer)
#LibreOffice (office)
#Riot (chat)
#nvim (editor)
#terminator (term emulator)
#tmux (term multiplexer)
#mutt (email)
#GIMP (image editor)
Puffinux (@[email protected])

402 Toots, 185 Following, 116 Followers · #Solarpunk, technology repairer, free software enthusiast. Maker of robots. Bicycles for transport. #Alternative. 🤖🌿🎨🖥🏰🌅🏊🚴🎮🎲💿📚

Show threadTheOuterLinux ✅Sep 6, 2018

@sevvie @[email protected] GNOME3....?! On an Arch machine?! WHAT MADNESS IS THIS! Have ye no i3 fealty?!

#MXLinux (Linux distro)
#XFCE (desktop environment)
#Palemoon (browser)
#xviewer (image viewer)
#LibreOffice (office)
#irssi or a #tox client (chat)
#nano (because I'm a sane person)
#xfce4-terminal (term emulator)
#tmux (term multiplexer)
#alpine or #Thunderbird (email)
#GIMP, #Krita, #MyPaint, or #GrafX2 for image editing/painting

Show threadcodesectionsSep 6, 2018

@TheOuterLinux @sevvie @puffinux

Just curious, what is the appeal of #nano? I've always thought of it as the simple, lightweight, but low-featured editor for quick edits over #ssh or something, but I've seen a few people on here that use it at a primary editor. I get that #vim/#emacs are acquired tastes, but what makes #nano stand out from more "modern" editors like #sublime or #vscode? Is it just being on the command line? (Which, don't get me wrong, I value too!)

Show threadDanilo SpinellaSep 6, 2018

@codesections @TheOuterLinux @sevvie @puffinux

Note also that lot of people use #vim for quick edits over #ssh, because ever systems have vi/vim installed. The same people then use a more complex system to develop on, or #emacs too.

Show threadcodesectionsSep 6, 2018

@danyspin97 @TheOuterLinux @sevvie @puffinux

Yeah, I'm in that camp myself, actually. I just meant that I'd thought of nano as filling that role for people who didn't like vim keybindings (it's the $EDITOR on a number of distros these days). But clearly there's more to it than that.

Show threadDanilo Spinella

@codesections @TheOuterLinux @sevvie @puffinux

It's because nano is the simplest terminal editor(considering the learning curve), and it usually comes preinstalled with the system. So if you don't want to learn vim, and have only #ssh access, then nano is your editor of choice.

The same if you want a mininal terminal editor.

There is also a modern replacement, called micro.

https://micro-editor.github.io/

Micro - Home

Sep 6, 2018 at 12:52pmWeb
Show threadcodesectionsSep 6, 2018

@danyspin97 @TheOuterLinux @sevvie @puffinux

Yeah, I get all that. That's exactly what I thought nano was for/how I've seen it used.

But @TheOuterLinux said they use it as their primary editor, and I've seen a couple other people say the same thing. (Or maybe I've seen @TheOuterLinux say the same thing a couple times before…). So I'm curious why they use it even when *not* constrained by SSH or anything else—there must be some feature set I'm missing.