12 ms·
GNU nano is my editor of choice (2021)
- tristanbvk 4y agoI used to be a nano user but now whenever I want to use a terminal text editor I will almost always use micro as it has built in support for most languages. https://micro-editor.github.io/ https://micro-editor.github.io/
- VaxWithSex 4y agoCame here to write this, you beat me to it.
- fifilura 4y agoI got stuck with jed https://www.jedsoft.org/jed/ https://www.jedsoft.org/jed/ as my terminal editor after getting too used to the emacs shortcuts but when emacs -nw became too heavy. Does anyone else use this? (To be fair I am transitioning to vim now that my emacs muscle memory is waning, and the rate of jed bugfixes likewise).
- zimpenfish 4y agoI had a period where I was using jed because I was doing stuff with s-lang (mostly Lynx) and using slrn to read news. But then I drifted into the vi/vims because trying to get jed installed everywhere was a pain.
- nivertech 4y agonano is usually installed by default
- petre 4y agoVi is fortunately present on just about every unix-like system and in busybox. Typing "v" in the pager and getting thrown into nano always prompts me to installing vim and changing the default editor. When I got into Linux there was no nano, only vi and ed. Pico came later with the Pine e-mail client.
- sbuk 4y ago> "Pico came later with the Pine e-mail client" Nope. GNU Nano, like a lot of the early GNU utilities, emulates Pico. I was using Pico/Pine around 1994/95 on UNIX workstations, and Pico was the default editor.
- petre 4y agoPico came later than vi/ed. I know nano is a pico clone which first appeared in '99 or so.
- threatofrain 4y agoAlso checkout Helix for those who want Vim with nice defaults (like LSP). https://helix-editor.com https://helix-editor.com https://github.com/helix-editor/helix https://github.com/helix-editor/helix
- anonyme-honteux 4y agoUsing those kind of Unix tools is like having a time travel machine to understand what kind of mistakes you should never do when Iyou design a software. Not having system wide keyboard shortcuts is one of them: vim, emacs, nano etc all have a different shortcut to quit the app Worse still, every software invents his own configuration format. Thinking that being ultra configurable is a good excuse for not doing the right thing by default is another big one. Syntax highlighting should just work, not only sort of work when you learn a configuration syntax and install little known third party packages
- europeanguy 4y agoOn the other hand, having system wide keyboard shortcuts will almost certainly impose unwanted constraints on how an app can behave.
- deleted 4y ago[deleted]
- spdionis 4y agoPlease do impose those unwanted constraints thank you!
- moffkalast 4y agoExactly, that's the whole damn point. It's to constrain those app devs from making stupid UI choices.
- wiseowise 4y agoDon’t use them if you don’t like them.
- allarm 4y agoI use vim keys everywhere I can, so from my standpoint “stupid” UI choices are the ones that don’t support modality. I would really prefer having vim keys optional built ins everywhere. Your situation is simpler though - you can just avoid using vim or whatever, there’s plenty of other options available. Also calling personal preferences of lots of people “stupid” is far from reasonable. I’ve met a lot of smart folks who used vim and emacs, so from my personal experience it’s not correct.
- dijit 4y agoThere was a time (2006?) when I was getting into linux. I was a big microsofty, due to comfort mostly, and I was shamed into trying Linux. Like most people I went Ubuntu first, but wifi drivers at the time were lacking, and nvidia of yore was certainly not better than nvidia of now. Suffice it to say: I spent a lot of time in the terminal trying to fix things. Nano was my tool of choice because: honestly the initial learning curve of linux and a modal text editor was far too much. that said: when I was later shamed into using vi/vim instead of nano.. after my initial hesitation (and a few rounds on vimtutor) I was as confident as I was on nano... what's more, I was "unlocked" and started learning new and faster ways to move. Being able to replay my last action with "." was nice, and lead me to learn even more native movements. My watershed moment came when I had to delete a leading series of characters in a file of I think 500 lines.. Not enough to say it's impossible but a real chore. Nano would not help me in such a situation: but vim did it with no complaints; all I needed to know was the incantation. I feel like nano shipping as the default editor is a step-back. We have a less powerful tool because we want to attract newbies, but it's the same mistake microsoft makes; When I was into microsoft tooling I had no idea how handicapped I was, the learning curve always had a stop point: everything beyond it was impossible. I will always be thankful I learned linux in a time where the hand-rails were starting to come up, but that we still used powerful and expressive tools instead of being jailed to the opaque and inflexible systems that have come to dominate for the sake of convenience.
- nkozyra 4y ago> I feel like nano shipping as the default editor is a step-back. We have a less powerful tool because we want to attract newbies Perhaps, but your experience sounds like a good blueprint for what new terminal users might want. Start with nano move to more powerful tools when you need them.
- radicalbyte 4y agoWindows ships with Notepad, which is fine for 99.9% of users. Those who need more know how to install Notepad++, UltraEdit or Sublime.
- 4y ago
- mhd 4y agoI'm quite fond of stories about people using editors besides the Big Two or the Newfangled Brigade. Keep 'em coming, you usually learn something about regular use and what others deem necessary – or can live without. Nano is interesting in that context, because for many it's the "default" editor, which is a bit weird if you came in to Linux/Unix earlier. I bet a lot of people feel the same when it comes to anything besides ed, though ;)
- europeanguy 4y ago[flagged]
- onei 4y agoI would guess because nano is meant to be a replacement for pico. Much to my surprise, I recently found nano was symlinked to pico on macOS. It'd been niggling at me for a while, I'd just assumed I'd been given an older version of nano. Guess I was kind of right.
- sys42590 4y agoPico was the inspiration for Nano. Pico was the standalone editor of the Pine mail client. The problem with Pico and Pine was their restrictive license, therefore clones with a more sane license were created (Nano and Alpine).
- dang 4y agoIf you keep crossing into personal attack we are going to have to ban you. No more of this, please. If you'd please review https://news.ycombinator.com/newsguidelines.html https://news.ycombinator.com/newsguidelines.html and stick to the rules when posting here, we'd appreciate it. Note this one: "Please don't pick the most provocative thing in an article or post to complain about in the thread. Find something interesting to respond to instead."
- samwillis 4y agoI've never learnt Vim or Emacs, have always used Nano when editing via the terminal. However I increasingly find myself firing up a VSCode remote session if I need to edit more than a single line. Remote VSCode is kind of magic, I'm increasingly working in (local) VMs via it. I have one project that is probably never going to never going to support ARM, and I'm close to needing to upgrade my MacBook. I really want an M2, but this project would be hard to run locally on it. VSCode on a remove VM is probably going to be the answer.
- forgotpwd16 4y agoI don't understand something. In order to remote develop you've to install VSCode to the remote machine?
- samwillis 4y agoSort of... VSCode will temporarily download and install its remote server on the remote machine, under your user home, when you connect to it. You don't have to do it yourself. To connect it's just plain ssh, so as long as you can login you can use it remotely. As soon as you connect it gives you a file file browser to select the root for VSCodes built in file browser side bar. My understanding is VSCode has a client/server architecture and so this was considered in its architectural design from the beginning. Along with file io, it's runs the language servers, git, terminal, and many other plugins remotely. Not all your plugins will initially be installed on the remote, but it's just a case of going to the plugins panel and clicking one button to install and enable on the remote.
- yakshaving_jgt 4y agoFWIW, vim can edit files over ssh. You still use your local vim, so you don’t need to [even temporarily] download/install your configuration/plugins on the remote machine. An alternative approach might be to mount the remote directory as a file system with sshfs.
- Aperocky 4y agoI liked Atom before I jumped into vim. I installed about 10 plugins that made my vim look almost exactly like Atom, except much faster, I also had a script that could install the exact plugins in any unix system in a few seconds, very useful since I work with VMs. Best of both worlds, people often forgets/don't know that vim are actually more configurable than other editors - colors, layouts, you name it.
- sfx77 4y agoAll of the old editors are horrible. Nano, vi, emacs... sure they might be conveniently placed, but are a pain to learn. This one is a vast improvement https://micro-editor.github.io/ https://micro-editor.github.io/
- b112 4y agoWha?! Nothing matches the power of vi or emacs. Nothing. If you don't want the power, or don't need the tool, fine. I get that. But calling vi terrible, is like complaining that a sledgehammer is terrible, because you want to hang a picture, and that's all you have.
- sfx77 4y agoThat's the thing. I want to hang a picture.
- mickeyp 4y agoThat is why you use Emacs. It has `M-x picture-mode` and its successor, `M-x artist-mode'.
- sfx77 4y agoright. I have no idea what that is.
- R0flcopt3r 4y agoIt's a joke.
- shiomiru 4y agoOr stay inside vi, and just filter your picture through the standard unix tool for hanging pictures.
- palata 4y agoHave you tried Windows or macOS? They are really good at hanging pictures.
- pavlov 4y agoI’m forever stuck with 1980s Turbo Pascal as my heart’s secret place of text-mode editing comfort, and nano is probably the closest thing available by default in most Unixes.
- ajuc 4y agomcedit was closer (and I still use it even though they stopped bundling it with most distributions for some reason). I love mcedit feature that lets you pipe selected text through a custom bash script.
- npteljes 4y agoThis is really curious to me. I'm also very partial to mcedit, it's often the first thing I install on boxes. And also, my first programming language was Turbo Pascal. Is that maybe why I like mcedit so much?
- ripe 4y agoYes!! Thanks for reminding me. Turbo Pascal was the ultimate in text editing. In fact, it was a complete IDE in a TUI. And the most-used commands were single keystrokes. Edit-run cycles were so fast that I was writing programs to do regular automation tasks.
- reshie 4y agoit is good for basic edits like configuration files. vim does just as well and has a lot more functionality universally.
- DemocracyFTW2 4y agoHighly reminiscent of #378: * nano? Real Programmers use emacs. * Hey. Real Programmers use vim. * Well, Real Programmers use ed. * No, Real Programmers use cat. * Real Programmers use a magnetized needle and a steady hand. * Excuse me, but Real Programmers use butterflies. They open their hands and let the delicate wings flap once. The disturbances ripple outward, changing the flow of the eddy currents in the upper atmosphere. These cause momentary pockets of higher-pressure air to form, Which act as lenses that deflect incoming cosmic rays, focusing them to strike the drive platter and flip the desired bit.
- red_trumpet 4y agoYou forgot the last panel: * Nice. 'Course there's an emacs command to do that. * Oh yeah! Good ol' `C-x M-c M-butterfly`... * Dammit, emacs! https://xkcd.com/378/ https://xkcd.com/378/
- mickeyp 4y agoIn homage to this, there's now `M-x butterfly' in Emacs.
- bruce343434 4y agoI have always thought that panel was deserving of treatment from the r/comedyamputation subreddit.
- DemocracyFTW2 4y agoyeah deliberately left that out
- pfoof 4y agoHow can you even use cat to write? I understand dd or echo, but cat by itself? Cat /dev/whatever and a steady hand?
- forgotpwd16 4y ago$ cat <<EOF > test > this is a test text file > written with cat > EOF $ cat <<EOF >> test > this is an extra line at the end > EOF $ cat test this is a test text file written with cat this is an extra line at the end But not sure how you modify them. An option will be using other tools but that makes cat incapable of being a text editor.
- lynx23 4y agoNano is the first thing I apt remove upon installing a new Debian box. Yes, I could use update-alternatives to make it non-default, but better uninstall the damn thing so that nobody can hurt themselves...
- tobbob 4y agoOkay..
- forgotpwd16 4y agoHow do you even hurt yourself with something that has on-screen help?
- latency-guy2 4y agoWhen people don't know what ^X means - it's Linux, most tools are very specific of flags and the order in which you put them on the command line. So is nano saying - SHIFT-[6](^)-SHIFT-X - SHIFT-[6](^)-x - CTRL-[6](^)-SHIFT-X - CTRL-[6](^)-x All I see is '^X', on my keyboard '^' is on 6. Why the hell isn't this working? Little does little Sally know that this is a UNIXism, carat means 'CTRL', X is really just 'x' - but how would Sally know? Sally was just trying to do a simple git commit to get used to using Linux in the first place. Is it little Sally's fault for not knowing? No! Will little Sally have a bad taste in her mouth due to using an unfamiliar tool? Yes. And there you go, little Sally has went on back to Windows. -1 user.
- lynx23 4y agoIs there a particular reason why you seem to imply that little knowledge == female? Sometimes the meme of "we need to mention girls more" works in unexpected directions if people are not careful.
- allarm 4y agoSally is a quranic boy and girl name. Is there any particular reason why you seem to imply that the the comment above mentioned a female? There’s no indication of gender.
- tobbob 4y agoI've never seen the point in spending time and effort learning and memorising a bunch of vim commands. If I need to do more than simple edits to a file, I'll have a graphical desktop installed and use vscode. I tend to use nano if using a CLI as it's more intuitive.
- jamespwilliams 4y agoOne reason among many: less keyboard<->mouse hand movements -> less strain on your hands and wrists. Vscode has decent vim bindings btw.
- yakshaving_jgt 4y agoI've never seen the point in spending time and effort learning and memorising a bunch of contextual menus that I need to point and click through. If I need to do more than simple edits to a file, I'll do the same thing as I would when making simple edits to a file or composing an email, I'll crack open vim and get to work.
- wiseowise 4y ago> If I need to do more than simple edits to a file, I'll do the same thing as I would when making simple edits to a file Cracked me up good.
- tobbob 4y agoYou don't need to spend any time or effort memorising a bunch of menus.
- yakshaving_jgt 4y agoNothing is going to convince me that a more conventional GUI text editor provides better ergonomics than something like vim or emacs. If you don’t like that kind of editor, that’s fine. You do you.
- p-e-w 4y agoThere is a very simple, end-of-discussion type argument why shipping Vim as the default editor is a terrible idea: Because its user interface differs significantly from how every other program on the system works. You can have all kinds of fruitful or fruitless debates about whether there is some deeper sense in which Vim is a "superior" editor, but there is no sensible reason for it to be the default, ever. Conventions matter. Don't surprise me. That's literally UX design 101. If a single program sticks out like a sore thumb because every keyboard shortcut suddenly means something different than it does in all other programs installed by default, that program is the problem. Replacing Vi(m) with Nano in the standard install was one of the most important UX decisions made by the major distros in recent years, and I can only attribute to blatant arrogance from some of the decision makers that it took so long in the first place.
- kator 4y agoBy that logic we should just make "ed" the default editor. It's more like every other line oriented CLI interface element in the system than Nano is.
- p-e-w 4y agoEd is indeed a good choice for a line editor. We're not talking about line editors, though, but about text editors. Ed is not useful for writing, because it does not have the immediate visual feedback when entering text that even mechanical typewriters have. For that, you need a text editor, and between Vim and Nano, only one behaves like most Unix software developed in the past three decades.
- chongli 4y agoEd is not useful for writing, because it does not have the immediate visual feedback when entering text that even mechanical typewriters have. What do you mean? $ ed i Ed is indeed a good choice for a line editor. We're not talking about line editors, though, but about text editors. Ed is not useful for writing, because it does not have the immediate visual feedback when entering text that even mechanical typewriters have. For that, you need a text editor, and between Vim and Nano, only one behaves like most Unix software developed in the past three decades. . .s/not useful/useful/g p Ed is indeed a good choice for a line editor. We're not talking about line editors, though, but about text editors. Ed is useful for writing, because it does not have the immediate visual feedback when entering text that even mechanical typewriters have. For that, you need a text editor, and between Vim and Nano, only one behaves like most Unix software developed in the past three decades. .s/does not have/does have/g p Ed is indeed a good choice for a line editor. We're not talking about line editors, though, but about text editors. Ed is useful for writing, because it does have the immediate visual feedback when entering text that even mechanical typewriters have. For that, you need a text editor, and between Vim and Nano, only one behaves like most Unix software developed in the past three decades. w ed_is_useful.txt 389 q $ cat ed_is_useful.txt Ed is indeed a good choice for a line editor. We're not talking about line editors, though, but about text editors. Ed is useful for writing, because it does have the immediate visual feedback when entering text that even mechanical typewriters have. For that, you need a text editor, and between Vim and Nano, only one behaves like most Unix software developed in the past three decades. $
- kleiba 4y agoWhat exactly is meant by the notion of "vim-like functionality with modeless editing"?
- dddddaviddddd 4y agoIn this article, it seems to mean syntax highlighting and hiding the help bar.
- rob81777 4y ago[flagged]
- yakshaving_jgt 4y agoGreat minds discuss ideas; average minds discuss events; small minds discuss people.
- imiric 4y agoIt's neat to see that nano supports customization at this level, and I can see the appeal for quickly editing files (though there are superior tools for even that nowadays, as mentioned in this thread), or if you're just getting familiar with text-mode editing, but I couldn't take anyone seriously if they _prefer_ it for programming. For one, the modal interface is so much superior to traditional key chords. It allows you to efficiently manipulate text and move the cursor, without twisting your hand in awkward positions, and remembering an endless amount of arbitrary chords. Emacs is the worst offender at this, and while it's my editor of choice, I couldn't imagine using it without evil-mode. Vim's default bindings are semantically significant, and naturally invite exploration. `c` is for `change`, `d` is for `delete`, `s` is for `substitute`, `w` is for `word`, etc. There are a limited amount of these that can be quickly learned, but the power comes when you combine them. *D*elete un*t*il the period becomes `dt.` *D*elete *i*nside parens becomes `di)`. Etc. Doing this without a modal interface becomes a chore of repeating key presses, or pressing some obscure combination of keys. Also, nano lacks any sort of plugin system. This means there's no LSP integration, file system or project exploration, running actions on save, etc. I don't blame it; if it had all those things it probably wouldn't be called _nano_... I'm a firm believer of using the tool you enjoy using, but it needs to be the right tool for the job. Use nano for its intended purpose, but if you edit text for a living, take the time to learn more advanced tools that will ultimately make your job easier.
- saagarjha 4y agonano has a file browser, and you can have it run actions on save.
- numlock86 4y agonano is cool for people with a newer background. If you've grown up with vi the muscle memory just beats anything in productivity.
- Havoc 4y agoFor people picking up linux for the first time that initial impression is crucial. Dropping people like that into an editor that requires you to somehow know ":q!" is the answer is utterly insane. Same with beginner tutorials using vi. It's straight up bad for linux adoption even if technically superior. Anyone that is a vi fan likely has the skillset to install it themselves - the reverse is not always true.
- lionkor 4y agoto be fair, at least neovim says to press :q! when you try Ctrl+C
- rich_sasha 4y agoVim seems to suggest that when by muscle memory i try "C-x C-q" (emacs exit). But the whole modality thing is insane for a newbie; vim is a fine editor as a conscious choice of course.
- p-e-w 4y ago> It's straight up bad for linux adoption even if technically superior. I think the idea that Vim is "technically superior" should be challenged as well. I've watched, and participated in, dozens of discussions on text editors, and have never been shown a concrete piece of scientific evidence demonstrating Vim's claimed superiority according to any real-world metric. All we have are artificial comparisons where it takes Vim 37 keystrokes to transform a Christmas carol into the lyrics of a death metal song, while it takes Nano an unacceptable 51 keystrokes to do the same (of course, this only works if you take half an hour beforehand to mentally construct that 37-keystroke sequence).
- Aperocky 4y agoWell there's no convincing you then. The pros of modal editing is well documented, and I'm not even arguing about the superiority of vim over the likes of emacs. People who believe using cursor to select, move, copy stuff are better than modal editing, even after all the argument, is probably not going to be swayed ever. As an almost pure vim user, I know how my own speed are significantly improved ever since I adopted vim and its modals, and I don't need to mentally construct keystrokes just like most people don't need to look at a keyboard to type. The demonstration are mostly some edge cases that don't really happen, but the general speed over general editing, some `V}y` here, some `ci(` there, some `Vjj2>`, `c-vwwGx` etc is what makes vim really shine. And no we don't have to dig a dictionary to type those things, all I had to do was to open vim since that's how muscle memory works.
- vintermann 4y agoI learned to type seriously not in an editor which respected CUA/Windows conventions, nor emacs conventions, nor vi conventions. It was the AMOS Basic editor, which I think followed Rexx conventions or something weird. All I remember is that shift-backspace would delete the whole line, which was terribly easy to do by mistake and extremely frustrating for a kid who didn't touch type or know about undo. That's given me a lot less patience for people wishing to re-train me for some alternate way do do the very basic things in life. Standard interface design is a great idea. The standards we use, even QWERTY, are a lot better than many would give them credit for.
- btdmaster 4y agoTiny solution: include "/usr/share/nano/*.nanorc"
- yakshaving_jgt 4y agoPerhaps it's confirmation bias, but it seems like quite a few vim/emacs/nano discussions have appeared on HN recently (more so than usual), with much of the commentary being along the lines of "Yeah I had a look at vim, but I don't see the point." What drives people to make comments like this? Why not either put in the work to understand the point, or just move along?
- deafpolygon 4y agoI use vim because I prefer modal editors when editing config files - "normal" mode prevents me from fat-fingering a lot of my config, and undo is a simple "u" away. :setlist allows me to see if I have any stray invisible characters. However, as a default for new distributions, nano is a solid choice (with the command help on the bottom). Any experienced users can just type vi, or update the EDITOR env var. It's about as friction-less as running a different command. However, once you grok vi, there's no going back.
- sylware 4y agoAs a programer, I do some "block edition" stuff it seems I cannot do with nano. I say it seems, because I only skimmed nano documentation.
- severak_cz 4y agoBtw - is there any linux based editor similar to Qbasic IDE?
- zX41ZdbW 4y agomcedit
- agolio 4y agoAh, a good old fashioned editor wars thread, surely the comments will be reasonable.
- sigmonsays 4y ago_editor1_ sucks.. you can pry _editor2_ from my cold dead hands.
- nurettin 4y agoIn the olden times, we had IRCA channels for hackers who dedicated their time and energy to certain kinds of software. You would certainly expect to find this person on IRC in a semi-official nano channel. How is it these days? How do you find these awesome experts?
- Conan_Kudo 4y agoI wonder if this blog post got written because some discussion about Fedora switching the OS default for terminal text editors to GNU nano spilled over somewhere. Fedora Linux 33 Change: https://fedoraproject.org/wiki/Changes/UseNanoByDefault https://fedoraproject.org/wiki/Changes/UseNanoByDefault
- GleamingGazelle 4y ago[dead]
- cesarb 4y agoThere's a reason I've always removed nano on every system I administer, and have done so for decades: when I first learned of nano, I also learned that it can corrupt configuration files where line breaks are significant by hard-wrapping long lines, unless you're very careful to always use "nano -w" instead of just "nano". I believe that this default has changed in a recent version of nano, and even before that some Linux distributions shipped with it set to not hard-wrap by default on a global configuration file, but it's still an unnecessary risk (unless you're really sure that the nano version is recent enough to have the new default, and that you'll never ssh to a machine running an older version of nano).
- themodelplumber 4y agoI accidentally turned this on once, IIRC, and discovered the issue after some shell scripting went off the rails. It was pretty irritating. Still, it led me to a deeper read of the configuration and I ended up enjoying nano more after that. It's come a long way in recent years too.
- me551ah 4y agoMy editor of choice is vscode and Intellij, the only time I would use a command line editor is when I am sshing into a server temporarily and just want to make some small edits to a file. I know enough commands on vim to insert/edit text and exit, which works when nano isn't available on the machine and I don't have access to a package manager. But for everything else, I use a proper IDE. I setup sshfs with remote machines that I use frequently, and just load the folder into my IDE and edit files in my IDE. VIM was designed in a very different era when terminals were small. An IDE gives me an integrated debugger, code completion, code formatting, project management(very useful for hierarchical projects) and integration with tools like VCS, Testing frameworks etc. I still don't understand people who use vim(or nano) as their primary editor.
- 3836293648 4y agoAn ide provides very little that vim doesn't. If you think it does you're just ignorant about what vim can do. Nano is basically featureless though
- pwpw 4y agoDoes anyone have a good tutorial for vim/neovim that they recommended for learning how to use them effectively? I’ve been using vim for over a year for quick edits, but I don’t think I get the most out of it.
- jalgos_eminator 4y agovimtutor. It comes with the full vim install, at least in ubuntu. It will give you the basics, then afterward you can run :h <command> to see what the less used commands do.
- pwpw 4y agoExactly what I needed. I learned a lot from it. Thank you!
- jalgos_eminator 4y ago> modal editing doesn’t really fit my mental model of how an editor should work The whole point of vim is that you change your mental model to become faster at editing text. People don't come into programming with a blank slate about editors, they were introduced to wysiwyg editors from an early age because of Microsoft Word, web based text input, and now phones (with emojis too). A mental model had been impressed already, but that doesn't make it the "default" or the best. I used notpad++ in college, then switched to vim after I saw my boss edit some code while I was looking over his shoulder. He could do complex editing tasks with just a couple keystrokes and doing them so fast that I couldn't keep up just watching. It seemed like he was editing at the same speed as he was thinking which didn't seem possible to me at the time.
- trynewideas 4y ago> The whole point of vim is that you change your mental model to become faster at editing text. The whole point of vi and vim was to edit text visually, instead of as lines. Bill Joy reflecting on vi in 1984:[1] "REVIEW: What would you do differently? JOY: I wish we hadn't used all the keys on the keyboard. I think one of the interesting things is that vi is really a mode-based editor. I think as mode-based editors go, it (is) pretty good. One of the good things about EMACS, though, is its programmability and the modelessness. Those are two ideas which never occurred to me. ... The fundamental problem with vi is that it doesn't have a mouse and therefore you've got all these commands. In some sense, its backwards from the kind of thing you'd get from a mouse-oriented thing. I think multiple levels of undo would be wonderful, too. But fundamentally, vi is still ed inside. You can't really fool it. Its like one of those pinatas - things that have candy inside but has layer after layer of paper mache on top. It doesn't really have a unified concept. I think if I were going to go back - I wouldn't go back, but start over again. I think the wonderful thing about vi is that it has such a good market share because we gave it away. Everybody has it now. So it actually had a chance to become part of what is perceived as basic UNIX. EMACS is a nice editor too, but because it costs hundreds of dollars, there will always be people who won't buy it." ... "REVIEW: What is it that (WYSIWYG document processor) Interleaf offers you that EMACS doesn't? JOY: I can just look at my screen, and when I print it off, it's the same as it looks on the screen. It is formatted, and I'm tired of using vi. I get really bored. There have been many nights when I've fallen asleep at the keyboard trying to make a release. At least now I can fall asleep with a mouse in my hand. I use the Xerox optica mouse instead of the other one because it is color coordinated with my office. Did you notice? I prefer the white mouse to the black mouse. You've got to have some fun, right? This business of using the same editor for 10 years - it's like living in the same place for 10 years. None of us does it. Everyone moves once a year, right?" 1: https://web.archive.org/web/20120210184000/http://web.cecs.pdx.edu/~kirkenda/joy84.html https://web.archive.org/web/20120210184000/http://web.cecs.p...
- oktwtf 4y agoYou can install nano on Windows using scoop, I usually do this so I can have some kind of text editor in powershell when I ssh into a Win11 box. Once you do a bit of configuration, nano has all the pleasantries you’d want for a quick edit.
- dang 4y agoDiscussed at the time: GNU nano is my editor of choice - https://news.ycombinator.com/item?id=28174810 https://news.ycombinator.com/item?id=28174810 - Aug 2021 (230 comments)
- phist_mcgee 4y agoOne argument I rarely see being brought up in the whole IDE/terminal editor wars is why use a terminal editor at all? For me, the pain of switching between multiple terminals and then to a different gui program like a browser can be a real tiring chore, especially when debugging.
- kazinator 4y agoIt seems Ariadne hasn't yet come across a code maintenance situation that she couldn't overcome by expenditure of keystrokes into a typewriter-like program. There is an illusion that it is all you need because using such a thing you can certainly crank out volumes of brand new content. If you have a clear idea of what you're writing, maybe just backspacing over the odd typo is all you need to forge ahead. And you can easily make small fixes to existing content with Nano, Notepad and whatnot. The more you have to think to make those fixes and the smaller is the actual textual change, the less of an impediment is it to use a "nonprogrammer's editor". If it took you 180 minutes to figure out it, shortening the editing from 30 seconds to 5 seconds succumbs to Amdah'ls Law; the speedup is virtually nil. There can be a range of editing needs in between these use cases, in the context of development. From Ariadne's experience I don't have the sense that she's worked in a software organization in a team, working on big changes to a big, existing code base and such and under pressure. Moreover, even in such an environment, there are those who survive somehow with goofy non-programmers' editors. You know the types; they announce themselves with their tattle-tale trail of wrong formatting (e.g. tabs where there should be spaces, incorrect indentation, ^M carriage returns in Unix-formatted files ...) spurious blank lines, or else trailing newline at the end of the file, trailing whitespace in lines and such. The times when raw editing is really the bottleneck are rare; and in all the other times, Amdahl's is ever present. Someone who has somehow figured out what needs to be changed where (with no help from any code navigation features in their glorified typewriter) can just crank it out. If what should take 5 minutes takes 45, it's not a big deal in the big picture. The assiduous Turtle armed with Notepad will beat the Hare who aptly uses a programmer's editor, but is unable to settle down to work. I can see how a developer could convince themselves that all they need is a glorified typewriter program for coding, and easily brush aside any evidence to the contrary. What you Get Done with that typewriter is your direct, personal experience, whereas how other people work is just anecdotes, not hard data.
- tpoacher 4y agoI agree with the article. I think most people who think nano is a "weak" editor simply haven't really used it beyond opening a file, editing a line, and then closing it. I do all my coding in nano, and I'm more than happy. I gave vim a sporting chance, know how to use it reasonably well, and do use it comfortably when editing collaboratively with a vim user. But nano just works, and without having to go through silly mental hoops. And for all the "mental efficiency" talk, in practice 99% of vim users I have interacted with either end up ignoring all the complicated stuff such that vim actively ends up wasting more of their time to do otherwise simple stuff, or manage to shoot themselves on the foot for every other "clever" thing they try to do. The latest release (7 onwards) has also become even more powerful, now that it allows function calling in macros (previously you could only use pre-bound keybindings)