Nano is no longer a GNU project

Re:Nano is no longer a GNU project by tretiy3 on Wednesday June 22, 2016 @08:40AM (#11953382)

I find it very convenient to open large log files bc Nano is very lightweight. Something like that:

$ cat /var/log/logfile | grep -n section_start which gives me required line numbers. and then:

$ nano +lineno /var/log/logfile

and for configs, of course.

[ Parent | on HN ]

Re:Nano is no longer a GNU project by Programmatic on Wednesday June 22, 2016 @10:36AM (#11954265)

I would go straight to vim and type: "/section_start<cr>", which navigates straight to that line. Then navigate to the line, "i" to enter insert mode, make edits, and "<esc>:wq<cr>".

It is absolutely a learning curve, but the power of vim is insane. "dd" deletes lines, "A" appends to the end, "I" inserts at the beginning, "<lineno>G" jumps to a line number, all little tweaks that I use nearly every day in editing files quickly. It's especially nice when editing known_hosts where it tells you the line of the offending key, just "<line#>Gdd:wq" and it's done.

[ Parent | on HN ]

Re:Nano is no longer a GNU project by ryanlol on Wednesday June 22, 2016 @11:07AM (#11954506)

>I find it very convenient to open large log files bc Nano is very lightweight.

Nano seems to be far slower than vim for opening large files.

Just quickly testing on a 200M 500k row text file on a SSD:

Vim opens practically instantly.

nano takes over 10 seconds to display text, but works well after that.

[ Parent | on HN ]