News for hackers. Stuff that matters.
Re:Thanks for the memory: How cheap RAM changes computing by nine_k on Monday October 17, 2016 @08:05AM (#12724280)
If you need an editor, use notepad.exe, nano, or an equivalent.

You run emacs / vim / sublime / atom exactly because it's much more than a simple text editor, it's a development environment of sorts.

Re:Thanks for the memory: How cheap RAM changes computing by melling on Monday October 17, 2016 @08:58AM (#12724580)
Why wouldn't use simply use the editor you leave open on your desktop for the "small editor" tasks?

What kind of person says "this is a job for nano, while this is a job for emacs?"

Re:Thanks for the memory: How cheap RAM changes computing by noir_lord on Monday October 17, 2016 @09:05AM (#12724626)
> What kind of person says "this is a job for nano, while this is a job for emacs?"

Me, I use nano for quick edits over SSH and a different editor/IDE for everything else (which is done locally and pushed, I (incredibly) rarely edit anything on the server.

Re:Thanks for the memory: How cheap RAM changes computing by npsimons on Monday October 17, 2016 @02:18PM (#12727679)
> What kind of person says "this is a job for nano, while this is a job for emacs?"

Depends on what you're used to. Even I as a seasoned die-hard Emacs user who is aware of both TRAMP and emacsclient will still fire up VIM (or vi) for various reasons: because it's what I grew up on, because I can't remember how to use TRAMP to edit that file remotely or as root, or the system is really not up to the task of running emacs.

Re:Thanks for the memory: How cheap RAM changes computing by yumaikas on Monday October 17, 2016 @11:30AM (#12725894)
I have a very specific example of jobs for nano vs vim. When I need to copy paste some code into a server and I don't have clipboard access over ssh, nano is better for that than vim, because vim tends to keep tabs indented, so I'll use nano to paste the file into, and then go into vim to edit it. I'm sure there are other examples.
Re:Thanks for the memory: How cheap RAM changes computing by OMGWTF on Monday October 17, 2016 @12:21PM (#12726483)
Use ":set paste" before you paste. (Disable with ":set nopaste".)

See also: http://vim.wikia.com/wiki/Toggle_auto-indenting_for_code_pas...

Or, if your terminal emulator supports "bracketed paste", use something like this: https://github.com/ConradIrwin/vim-bracketed-paste

Re:Thanks for the memory: How cheap RAM changes computing by nine_k on Monday October 17, 2016 @11:29AM (#12725879)
Indeed, if you use emacs, you just keep it open forever and use it for everything. Such is the culture.

(Some people even try to use emacs as their entire desktop environment.)

Re:Thanks for the memory: How cheap RAM changes computing by Roboprog on Monday October 17, 2016 @12:20PM (#12726475)
Maybe we disagree about scale :-)

Vim is my "little" editor; JetBrains (and the like) are my "big" editor (albeit with vi[m] plugin to avoid the mental context switch).

Somewhere an emacs user is laughing at me, but I'll get over it.