71–80 of 154 posts
Earlier quoted context omitted.
I often reach for emacs -nw -Q It boots up quickly and the basic editing defaults are all there. Has the advantage of being everywhere Emacs already is as well
I like mg as an emacs-like editor that is simple and quick. Made by the great OpenBSD folks and is of great quality with good documentation.
Earlier quoted context omitted.
Nano also has mouse support, it's just disabled by default. /etc/nanorc is worth a look, at least on Debian it's well commented
I'm confused. The only reason one uses nano is because you ssh'ed into some random machine and you are stuck with whatever is on it. If you got enough bother to install micro or fiddling with the settings of nano you might as well setup something more proper.
>An overlong line is no longer automatically hard-wrapped. Finally. It was one of the most insane defaults in the history of text editors. Things like this are the reason why it's so hard to recommend nano to beginners.
I like the idea of hard wrap, line of code shouldn't be longer than 80 characters... sure it's confusing for beginners + sometimes data shouldn't be hard-wrapped, but in general (imho) it's better than worse
>A newline character is no longer automatically added at end of buffer. yesssssssssss
Such an insane default. Currently programming a bittorrent client and was edited files to test some functionality. Was confused for a long time until I realized nano was turning my "echo 'this is a test' > test" into "echo 'this is a test\n' > test"
echo 'this is a test' > test\n
Earlier quoted context omitted.
For a stable piece of software the build script(s) somehow turn into a change hotspot. You might have not touched the core of the software in five years, but guess what, every couple months some change to the build script is necessary.
Depends on how much nonstandard stuff you’re using, and whether you have flags such as -Werror that can cause “new” build failures.
Earlier quoted context omitted.
Nano also has mouse support, it's just disabled by default. /etc/nanorc is worth a look, at least on Debian it's well commented
I'm confused. The only reason one uses nano is because you ssh'ed into some random machine and you are stuck with whatever is on it. If you got enough bother to install micro or fiddling with the settings of nano you might as well setup something more proper.
Earlier quoted context omitted.
Genuinely curious, why do you see this as a good change?
Because if I type "hello" in a document, I expect the editor to save "hello", not "hello\n".
(I was actually very surprised when vscode _didn't_ do this!)
Earlier quoted context omitted.
The old behaviour is the sane default, at least for editing text files. POSIX defines a text file as a file consisting of a number of lines, each terminated by an LF character.
sane is what the user expects, not what POSIX demands.
>A newline character is no longer automatically added at end of buffer. yesssssssssss
Such an insane default. Currently programming a bittorrent client and was edited files to test some functionality. Was confused for a long time until I realized nano was turning my "echo 'this is a test' > test" into "echo 'this is a test\n' > test"