nano - Nano's ANOther editor, an enhanced free Pico clone


SUBMITTED BY: Guest

DATE: June 4, 2014, 6:19 a.m.

FORMAT: Text only

SIZE: 4.5 kB

HITS: 4839

  1. NAME
  2. nano - Nano's ANOther editor, an enhanced free Pico clone
  3. SYNOPSIS
  4. nano [+LINE] [options] [file]
  5. DESCRIPTION
  6. This manual page documents briefly the nano command.
  7. nano is a small, free and friendly editor which aims to replace Pico, the default editor included in the non-free Pine package. Rather than just copying Pico's look and feel, nano also implements some missing (or disabled by default) features in Pico, such as "search and replace" and "go to line number".
  8. OPTIONS
  9. +LINE
  10. Places cursor at LINE on startup.
  11. -B (--backup)
  12. When saving a file, back up the previous version of it to the current filename suffixed with a ~.
  13. -D (--dos)
  14. Write file in DOS format.
  15. -F (--multibuffer)
  16. Enable multiple file buffers, if available.
  17. -H (--historylog)
  18. Log search and replace strings to ~/.nano_history so they may be stored for later editing, if nanorc support is configured.
  19. -I (--ignorercfiles)
  20. Don't look at $SYSCONFDIR/nanorc or ~/.nanorc, if nanorc support is available.
  21. -K (--keypad)
  22. Do not use the ncurses keypad() call unless necessary. Try this flag if you find that the arrow keys on the numeric keypad do not work for you under nano.
  23. -M (--mac)
  24. Write file in Mac format.
  25. -N (--noconvert)
  26. Disable automatic conversion of files from DOS/Mac format.
  27. -Q str (--quotestr=str)
  28. Set the quoting string for justifying. The default is "^([ \t]*[|>:}#])+" if regular expression support is available, or "> " otherwise.
  29. -R (--regexp)
  30. Enable regular expression matching for search strings, as well as \n subexpression replacement for replace strings, if available.
  31. -S (--smooth)
  32. Enable smooth scrolling. Text will scroll line-by-line, instead of the usual chunk-by-chunk behavior.
  33. -T num (--tabsize=num)
  34. Set the size (width) of a tab.
  35. -V (--version)
  36. Show the current version number and author.
  37. -Y str (--syntax=str)
  38. Specify a specific syntax highlighting from the .nanorc to use, if available.
  39. -c (--const)
  40. Constantly show the cursor position.
  41. -h (--help)
  42. Display a summary of command line options.
  43. -i (--autoindent)
  44. Indent new lines to the previous line's indentation. Useful when editing source code.
  45. -k (--cut)
  46. Enable cut from cursor to end of line with ^K.
  47. -l (--nofollow)
  48. If the file being edited is a symbolic link, replace the link with a new file, do not follow it. Good for editing files in /tmp, perhaps?
  49. -m (--mouse)
  50. Enable mouse support (if available for your system).
  51. -o dir (--operatingdir=dir)
  52. Set operating directory. Makes nano set up something similar to a chroot.
  53. -p (--preserve)
  54. Preserve the XON and XOFF sequences (^Q and ^S) so they will be caught by the terminal.
  55. -r cols (--fill=cols)
  56. Wrap lines at column cols. By default, this is the width of the screen, less eight. If this value is negative, wrapping will occur at cols columns from the right of the screen, allowing the wrap point to vary along with the screen width if resized.
  57. -s prog (--speller=prog)
  58. Enable alternative spell checker command.
  59. -t (--tempfile)
  60. Always save changed buffer without prompting. Same as Pico -t option.
  61. -v (--view)
  62. View file (read only) mode.
  63. -w (--nowrap)
  64. Disable wrapping of long lines.
  65. -x (--nohelp)
  66. Disable help screen at bottom of editor.
  67. -z (--suspend)
  68. Enable suspend ability.
  69. -a, -b, -e, -f, -g, -j
  70. Ignored, for compatibility with Pico.
  71. INITIALIZATION FILE
  72. nano will read initialization files in the following order: $SYSCONFDIR/nanorc, then ~/.nanorc. Please see nanorc(5) and the example file nanorc.sample which should be provided with nano.
  73. NOTES
  74. nano will try to dump the buffer into an emergency file in some cases. Mainly, this will happen if nano receives a SIGHUP or SIGTERM or runs out of memory, when it will write the buffer into a file named nano.save if the buffer didn't have a name already, or will add a ".save" suffix to the current filename. If an emergency file with that name already exists in the current directory, ".save" and a number (e.g. ".save.1") will be suffixed to the current filename in order to make it unique. In multibuffer mode, nano will write all the open buffers to the respective emergency files.

comments powered by Disqus