<br><br><div class="gmail_quote">2008/11/10 W W <span dir="ltr"><<a href="mailto:srilyk@gmail.com">srilyk@gmail.com</a>></span><br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div class="gmail_quote">On Mon, Nov 10, 2008 at 9:40 AM, Alan Gauld <span dir="ltr"><<a href="mailto:alan.gauld@btinternet.com" target="_blank">alan.gauld@btinternet.com</a>></span> wrote:</div><div class="gmail_quote">
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<snip> </blockquote><div class="Ih2E3d"><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">What does nano do that vi (or emacs) doesn't? Given that vi is the "standard" editor on *nix ity would seem the obvious choice. But everyone seems to be using nano? Why?</blockquote>
<div><br></div></div><div>AFAIK, it's a little smaller/faster than emacs... but since I'm a vi(m) fan, I'm probably the wrong person for the question ;)</div><br></div><br></blockquote></div><br>My guess is that, if you want to provide instructions to someone with no linux/unix experience. e.g. to edit a config file, you can safely tell them to: nano myfile.conf and expect them to be able to save the file and return to the command line. If you want to give the same instructions using vim or emacs, you would also need to specify how to save and exit. I imagine this to be the reason it is popular in tutorials, and if all the tutorials you use, use nano, you will probably use it too.<br clear="all">
<br>-- <br>Michael Connors<br><br>