Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Customize Nano Text Editor (2022)

shafi.ddns.net

Post reply on HN
Print view View original

41–50 of 69 posts

Re: Customize Nano Text Editor (2022)

#41

Post by smartmic »

digisign wrote: post #19
its_notjack wrote: post #4

I must have used nano for years at this point, and I'm shocked to find out how customisable nano actually is! I tend to use micro[0] on most of my systems now just because it comes with really lovely defaults and keybindings that are a bit more familiar, but this might make me take a second look at nano in future. [0] https://micro-editor.github.io/

Before I used micro & ne I used nano, and configured the keybindings to work in the CUA style. I still have the dot files, didn't delete them, but they rarely get used anymore. I think they recently added Ctrl+S to save by default, even if unconfigured, woohoo.

For CUA aficionados, I recommend dte[0]. It has replaced my nano usage quite a lot.

[0]: https://craigbarnes.gitlab.io/dte/index.html

Re: Customize Nano Text Editor (2022)

#42

Post by genpfault »

digisign wrote: post #19
its_notjack wrote: post #4

I must have used nano for years at this point, and I'm shocked to find out how customisable nano actually is! I tend to use micro[0] on most of my systems now just because it comes with really lovely defaults and keybindings that are a bit more familiar, but this might make me take a second look at nano in future. [0] https://micro-editor.github.io/

Before I used micro & ne I used nano, and configured the keybindings to work in the CUA style. I still have the dot files, didn't delete them, but they rarely get used anymore. I think they recently added Ctrl+S to save by default, even if unconfigured, woohoo.

> Ctrl+S to save

XOFF ignored, mumble mumble

Re: Customize Nano Text Editor (2022)

#43

Post by dv35z »

What would it take to have "vim-wiki" for nano (see also: FOAM, Obsidian)? I have always admired nano for how simple and easy to use it is, and would love to use it for wiki/obsidian-style note taking & linking...

Re: Customize Nano Text Editor (2022)

#45

Post by suprjami »

bigstrat2003 wrote: post #34
SilentM68 wrote: post #29

Earlier quoted context omitted.

I would say that every tool has its good and bad. A tool is only as good as its ease of use and clarity of its documentation, imho.

Wouldn't that make vi(m) just about the worst tool to exist? There's a reason that the "how do I exit vim" jokes exist, it's because the UI is awful unless you already know how to use it.

God forbid having to learn how to use something useful. Don't ever take up programming.

Re: Customize Nano Text Editor (2022)

#46

Post by noisem4ker »

smartmic wrote: post #41
digisign wrote: post #19

Earlier quoted context omitted.

Before I used micro & ne I used nano, and configured the keybindings to work in the CUA style. I still have the dot files, didn't delete them, but they rarely get used anymore. I think they recently added Ctrl+S to save by default, even if unconfigured, woohoo.

For CUA aficionados, I recommend dte[0]. It has replaced my nano usage quite a lot. [0]: https://craigbarnes.gitlab.io/dte/index.html

I personally like msedit.

https://github.com/microsoft/edit

Re: Customize Nano Text Editor (2022)

#47

Post by gh02t »

dv35z wrote: post #43

What would it take to have "vim-wiki" for nano (see also: FOAM, Obsidian)? I have always admired nano for how simple and easy to use it is, and would love to use it for wiki/obsidian-style note taking & linking...

Nano doesn't really support any sort of scripting or plugins beyond macro sequences AFAIK. So, not really in the same sense as something like vim-wiki etc. You might be able to cobble together something with shell scripts and text files, but it won't be well integrated.

Re: Customize Nano Text Editor (2022)

#48

Post by tom_ »

notepad0x90 wrote: post #31

My struggle is that I work on lots of systems, sometimes ephemeral/temporary systems. There is no easy way to "sync" customizations, so I adapt to defaults. Even basic things like how shell history is managed is very annoying to configure every single time. if only it was as simple as cloning your private github repo to ~/.config.

Cloning a github repo to ~/.emacs.d is how you can cart around your Emacs config. I've been doing this for years, and it works nicely. For things configured by files that live in the home folder directly (e.g., shell - and looks like Nano would be similar?), I've got another repo with a couple of install scripts that create symlinks to the version-controlled files. I don't love the extra steps, but I've found this works pretty well too.

Most of the time, I can manage without, but every now and again I've needed to do some thing or other, and I've been grateful to have my own preferred setup rather than somebody else's.

Post reply on HN