3 ms·

nano, or the new feature? I use nano all the time.

by throwaway613834 9y ago

millstone 9y ago
Why do you use nano?
- throwaway613834 9y ago
  It's simple, it's on every platform I ever SSH into, and it gets the job done quickly?
  - phillc73 9y ago
    Exactly this reason. You just know it will always be installed. And I still type "pico".
    - throwaway613834 9y ago
      pico is harder & slower for me to type for some reason! not sure why.
    - Fnoord 9y ago
      (Assuming you're using Bash as shell) If you want to get rid of this habit put this in /usr/local/bin/pico.sh or ~/bin/pico.sh #!/bin/bash echo "Type nano instead of pico..." sleep 5 nano $* Put in ~/.bashrc alias pico=~/bin/pico.sh (or /usr/local/bin/pico.sh) Make sure to chmod +x the shell script. You can also simply call it pico instead of pico.sh; then you won't have to use the ~/.bashrc addition.
- im_down_w_otp 9y ago
  I use it in a pinch fairly constantly. Despite being a heavily customized Emacs user all the rest of the time. Mostly when I'm already scouring around the shell poking at files or need to make a simple new one (like a .gitignore) and I don't want/need to perturb whatever else I'm doing in Emacs.
  - subway 9y ago
    This post makes me so glad to have been forced into vi all those years ago. Its everywhere, its quick, and unless you've done some pretty nutty stuff in your configs, basic usage is the same between a heavily customized vi and the vi you find bundled with every is bundled windows and gentoo. (Not to disparage any preference for emacs; it just seems a bit much to have to fall back to an entirely different editor seems a bit much)
    - im_down_w_otp 9y ago
      I don't _have_ to "fallback". I just choose not to interrupt the extremely rich development environment I have setup in Emacs and my projectile projects by bringing in random other files/buffers. It's akin to the same justification for why I wouldn't bother opening a random tiny file in Xcode or IntelliJ IDEA. I don't use Emacs as just a simple text editor. I can probably count the times I've typed `emacs some/file/path.whatever` into the shell on one hand.
  - confounded 9y ago
    If you start Emacs server as a daemon, you can use it pretty much like you'd use nano/vi/vim in the terminal, without disturbing anything. With an Emacs server running, for me, it loads faster than vim. I have a bash function along the lines of et() { emacsclient -tty --alternate-editor '' "$@" } .. for using Emacs in the terminal a-la vim/nano. When you close the file you opened, you'll be right back where you left-off in the shell. I still tend to use a long-running GUI instance as you describe, but for jumping into config files from a terminal to edit a line or two, it's great.
- int_19h 9y ago
  It's a simple text editor that's available out of the box in most Unix-like distros these days. So kinda like vi, except I know how to use it (and if I ever forget, it lists all shortcuts on the bottom of the screen anyway).
  - greenhouse_gas 9y ago
    Actually, the Debian install cd doesn't have vi but does have nano, and vim (and neovim) is larger than nano.
    - yjftsjthsd-h 9y ago
      That actually seems a bit odd; it's not like vi is big.
    - jwilk 9y ago
      The size argument alone cannot explain nano > vi preferences in d-i. vim-tiny and nano sizes are nearly the same; nvi is smaller; I'm pretty sure the "vi" applet in busybox would be much smaller.
7kmph 9y ago
Nano. Just curious :)
stuaxo 9y ago
I use nano all the time. It's on most platforms and it's quick to bring up for some basic editing. Over the last 20 years of using Linux I haven't learned vi and emacs above basic editing and saving files.

nano, or the new feature? I use nano all the time.

millstone 9y ago

Why do you use nano?

throwaway613834 9y ago
It's simple, it's on every platform I ever SSH into, and it gets the job done quickly?
- phillc73 9y ago
  Exactly this reason. You just know it will always be installed. And I still type "pico".
  - throwaway613834 9y ago
    pico is harder & slower for me to type for some reason! not sure why.
  - Fnoord 9y ago
    (Assuming you're using Bash as shell) If you want to get rid of this habit put this in /usr/local/bin/pico.sh or ~/bin/pico.sh #!/bin/bash echo "Type nano instead of pico..." sleep 5 nano $* Put in ~/.bashrc alias pico=~/bin/pico.sh (or /usr/local/bin/pico.sh) Make sure to chmod +x the shell script. You can also simply call it pico instead of pico.sh; then you won't have to use the ~/.bashrc addition.
im_down_w_otp 9y ago
I use it in a pinch fairly constantly. Despite being a heavily customized Emacs user all the rest of the time. Mostly when I'm already scouring around the shell poking at files or need to make a simple new one (like a .gitignore) and I don't want/need to perturb whatever else I'm doing in Emacs.
- subway 9y ago
  This post makes me so glad to have been forced into vi all those years ago. Its everywhere, its quick, and unless you've done some pretty nutty stuff in your configs, basic usage is the same between a heavily customized vi and the vi you find bundled with every is bundled windows and gentoo. (Not to disparage any preference for emacs; it just seems a bit much to have to fall back to an entirely different editor seems a bit much)
  - im_down_w_otp 9y ago
    I don't _have_ to "fallback". I just choose not to interrupt the extremely rich development environment I have setup in Emacs and my projectile projects by bringing in random other files/buffers. It's akin to the same justification for why I wouldn't bother opening a random tiny file in Xcode or IntelliJ IDEA. I don't use Emacs as just a simple text editor. I can probably count the times I've typed `emacs some/file/path.whatever` into the shell on one hand.
- confounded 9y ago
  If you start Emacs server as a daemon, you can use it pretty much like you'd use nano/vi/vim in the terminal, without disturbing anything. With an Emacs server running, for me, it loads faster than vim. I have a bash function along the lines of et() { emacsclient -tty --alternate-editor '' "$@" } .. for using Emacs in the terminal a-la vim/nano. When you close the file you opened, you'll be right back where you left-off in the shell. I still tend to use a long-running GUI instance as you describe, but for jumping into config files from a terminal to edit a line or two, it's great.
int_19h 9y ago
It's a simple text editor that's available out of the box in most Unix-like distros these days. So kinda like vi, except I know how to use it (and if I ever forget, it lists all shortcuts on the bottom of the screen anyway).
- greenhouse_gas 9y ago
  Actually, the Debian install cd doesn't have vi but does have nano, and vim (and neovim) is larger than nano.
  - yjftsjthsd-h 9y ago
    That actually seems a bit odd; it's not like vi is big.
  - jwilk 9y ago
    The size argument alone cannot explain nano > vi preferences in d-i. vim-tiny and nano sizes are nearly the same; nvi is smaller; I'm pretty sure the "vi" applet in busybox would be much smaller.

7kmph 9y ago

Nano. Just curious :)

stuaxo 9y ago

I use nano all the time. It's on most platforms and it's quick to bring up for some basic editing. Over the last 20 years of using Linux I haven't learned vi and emacs above basic editing and saving files.