• Objet : L'éditeur de textes nano.
• Niveau requis :

  débutant, avisé
• Commentaires : Un éditeur simple d'utilisation pour, entre autres choses, administrer son système.
• A savoir : Utiliser GNU/Linux en ligne de commande, tout commence là !.
• Suivi :
  • Création par smolski le 12/06/2009
  • Révision par milou et paskal le 11/10/2015
  • Tests réalisés par milou le 11/10/2015
• Commentaires sur le forum : Lien vers le forum concernant ce tuto¹⁾

Nano est un éditeur de texte, en console ou en terminal, très utile pour modifier les fichiers de configuration de votre système.

Qui dit éditeur de texte dit :

1. programme qui permet essentiellement de modifier des fichiers,
2. donc des textes bruts sans mise en forme (gras, italique, souligné…).

Comme son nom le laisse deviner (le terme “nano” représente une toute petite unité), il s'agit d'une application :

1. plutôt simple, mais néanmoins puissant.
2. possédant moins de fonctions comparé aux commandes d'édition vim ou emacs.

mais qui convient tout à fait lorsque l'on commence à utiliser un éditeur de texte ou que nos besoins ne sont pas trop grands.

Voici une liste de ses fonctions les plus intéressantes :

1. Annulation multiple.
2. Coloration syntaxique
3. Auto-Complétion
4. Macro

Pour une édition en tant qu'utilisateur du fichier monfichier

nano monfichier

Pour une édition en tant que root du fichier monfichier

nano monfichier

Ces raccourcis clavier s'appliquent pour un clavier Azerty Français

Pour sélectionner du texte, le copier et le coller :

1. Se déplacer avec les flèches ↑ ↓ ← → pour se placer à l'endroit voulu,
2. Faire Alt+A ou Maj+Ctrl+- pour marquer le début de la sélection,
3. Se déplacer avec les flèches ↑ ↓ ← → pour sélectionner la zone de texte à copier,
4. Copier cette sélection avec Maj+Alt+-,
5. Se déplacer à l'endroit voulu pour le collage,
6. Coller avec Ctrl+U.

Pour que nano affiche en permanence les coordonnées ligne/colonne, il est possible de le lancer avec l'option -c :

nano -c <fichier>

Pour utiliser la souris dans le terminal, lancer nano avec l'option -m

Par défaut gpm donne le support de l'utilisation de la souris dans le terminal (+ copier-coller en un clic), nous allons voir comment faire pour positionner le curseur à l'endroit du clic.

Pour que nano place le curseur où vous cliquez :

Installer gpm

Lancer nano avec l'option -m:

nano -m <fichier>

L'option permet de sauvegarder l'ancienne version du fichier. Il est donc possible de récupérer cette version en cas d'erreur. Le fichier sera renommé avec le suffixe ~, on retrouvera alors le fichier <fichier> et <fichier>~ sa sauvegarde.

Lancer nano avec l'option -B:

nano -B <fichier>

On peut aussi configurer nano ainsi :

En local en créant un :

 /home/user/.nanorc

Et en le configurant mot à mot…

Ou pour tout le monde, en modifiant les options dans :

 /etc/nanorc

Par exemple :

Dans un terminal root, éditer nanorc ainsi :

nano /etc/nanorc

Gagner de la place à l'écran en n'affichant pas les raccourcis, décommenter la ligne set nohelp :

/etc/nanorc

## Don't display the helpful shortcut lists at the bottom of the screen.
#set nohelp

Faire disparaître la barre de status, décommentez set quickblank :

/etc/nanorc

## Do quick statusbar blanking.  Statusbar messages will disappear after
## 1 keystroke instead of 26.  Note that "const" overrides this.
##
#set quickblank

A l'inverse on peut préférer avoir un affichage plus complet comme le défilement de numéros de lignes, colonnes, etc…
Et si vous consultiez :

man nanorc

Essayer, c'est l'adopter ! Merci tux12

/etc/nanorc

## Sample initialization file for GNU nano.
##
## Please note that you must have configured nano with --enable-nanorc
## for this file to be read!  Also note that this file should not be in
## DOS or Mac format, and that characters specially interpreted by the
## shell should not be escaped here.
##
## To make sure an option is disabled, use "unset <option>".
##
## For the options that take parameters, the default value is given.
## Other options are unset by default.
##
## Quotes inside string parameters don't have to be escaped with
## backslashes.  The last double quote in the string will be treated as
## its end.  For example, for the "brackets" option, ""')>]}" will match
## ", ', ), >, ], and }.
 
## Make the 'nextword' function (Ctrl+Right) stop at word ends
## instead of at beginnings.
# set afterends
set afterends
 
## When soft line wrapping is enabled, make it wrap lines at blanks
## (tabs and spaces) instead of always at the edge of the screen.
# set atblanks
 
## Automatically indent a newly created line to the same number of
## tabs and/or spaces as the preceding line -- or as the next line
## if the preceding line is the beginning of a paragraph.
# set autoindent
set autoindent
 
## Back up files to the current filename plus a tilde.
# set backup
 
## The directory to put unique backup files in.
# set backupdir ""
 
## Use bold text instead of reverse video text.
# set boldtext
 
## The characters treated as closing brackets when justifying paragraphs.
## This may not include any blank characters.  Only closing punctuation,
## optionally followed by these closing brackets, can end sentences.
# set brackets ""')>]}"
 
## Do case-sensitive searches by default.
# set casesensitive
 
## Constantly display the cursor position in the status bar.  Note that
## this overrides "quickblank".
# set constantshow
 
## Use cut-from-cursor-to-end-of-line by default.
# set cutfromcursor
set cutfromcursor
## (The old form, 'cut', is deprecated.)
 
## Set the line length for wrapping text and justifying paragraphs.
## If the value is 0 or less, the wrapping point will be the screen
## width less this number.
# set fill -8
 
## Remember the used search/replace strings for the next session.
set historylog
 
## Display line numbers to the left of the text.
# set linenumbers
set linenumbers
 
## Enable vim-style lock-files.  This is just to let a vim user know you
## are editing a file [s]he is trying to edit and vice versa.  There are
## no plans to implement vim-style undo state in these files.
set locking
 
## The opening and closing brackets that can be found by bracket
## searches.  They cannot contain blank characters.  The former set must
## come before the latter set, and both must be in the same order.
# set matchbrackets "(<[{)>]}"
 
## Use the blank line below the title bar as extra editing space.
# set morespace
 
## Enable mouse support, if available for your system.  When enabled,
## mouse clicks can be used to place the cursor, set the mark (with a
## double click), and execute shortcuts.  The mouse will work in the X
## Window System, and on the console when gpm is running.
# set mouse
set mouse
 
## Switch on multiple file buffers (inserting a file will put it into
## a separate buffer).
# set multibuffer
set multibuffer
 
## Don't convert files from DOS/Mac format.
# set noconvert
 
## Don't display the helpful shortcut lists at the bottom of the screen.
# set nohelp
 
## Don't automatically add a newline when a file does not end with one.
# set nonewlines
set nonewlines
 
## Don't pause between warnings at startup.  Which means that only the
## last one will be readable (when there are multiple ones).
# set nopauses
 
## Don't wrap text at all.
set nowrap
 
## Set operating directory.  nano will not read or write files outside
## this directory and its subdirectories.  Also, the current directory
## is changed to here, so any files are inserted from this dir.  A blank
## string means the operating-directory feature is turned off.
# set operatingdir ""
 
## Remember the cursor position in each file for the next editing session.
# set positionlog
set positionlog
 
## Preserve the XON and XOFF keys (^Q and ^S).
# set preserve
 
## The characters treated as closing punctuation when justifying
## paragraphs.  They cannot contain blank characters.  Only closing
## punctuation, optionally followed by closing brackets, can end
## sentences.
# set punct "!.?"
 
## Do quick status-bar blanking.  Status-bar messages will disappear after
## 1 keystroke instead of 26.  Note that "constantshow" overrides this.
# set quickblank
 
## The email-quote string, used to justify email-quoted paragraphs.
## This is an extended regular expression.  The default is:
# set quotestr "^([ 	]*([#:>|}]|//))+"
 
## Fix Backspace/Delete confusion problem.
# set rebinddelete
 
## Fix numeric keypad key confusion problem.
# set rebindkeypad
 
## Do extended regular expression searches by default.
# set regexp
 
## Put the cursor on the highlighted item in the file browser;
## useful for people who use a braille display.
# set showcursor
 
## Make the Home key smarter.  When Home is pressed anywhere but at the
## very beginning of non-whitespace characters on a line, the cursor
## will jump to that beginning (either forwards or backwards).  If the
## cursor is already at that position, it will jump to the true
## beginning of the line.
# set smarthome
set smarthome
 
## Use smooth scrolling as the default.
# set smooth
 
## Enable soft line wrapping (AKA full-line display).
# set softwrap
 
## Use this spelling checker instead of the internal one.  This option
## does not have a default value.
# set speller "aspell -x -c"
 
## Allow nano to be suspended.
set suspend
 
## Use this tab size instead of the default; it must be greater than 0.
# set tabsize 8
set tabsize 4
 
## Convert typed tabs to spaces.
# set tabstospaces
 
## Save automatically on exit; don't prompt.
# set tempfile
 
## Snip whitespace at the end of lines when justifying or hard-wrapping.
# set trimblanks
## (The old form, 'justifytrim', is deprecated.)
 
## Disallow file modification.  Why would you want this in an rcfile? ;)
# set view
 
## The two single-column characters used to display the first characters
## of tabs and spaces.  187 in ISO 8859-1 (0000BB in Unicode) and 183 in
## ISO-8859-1 (0000B7 in Unicode) seem to be good values for these.
## The default when in a UTF-8 locale:
# set whitespace "»·"
## The default otherwise:
# set whitespace ">."
 
## Detect word boundaries differently by treating punctuation
## characters as parts of words.
# set wordbounds
 
## The characters (besides alphanumeric ones) that should be considered
## as parts of words.  This option does not have a default value.  When
## set, it overrides option 'set wordbounds'.
# set wordchars "<_>."
 
 
## Paint the interface elements of nano.  These are examples;
## by default there are no colors, except for errorcolor.
# set titlecolor brightwhite,blue
# set statuscolor brightwhite,green
# set errorcolor brightwhite,red
# set selectedcolor brightwhite,magenta
# set numbercolor cyan
# set keycolor cyan
# set functioncolor green
## In root's .nanorc you might want to use:
# set titlecolor brightwhite,magenta
# set statuscolor brightwhite,magenta
# set errorcolor brightwhite,red
# set selectedcolor brightwhite,cyan
# set numbercolor magenta
# set keycolor brightmagenta
# set functioncolor magenta
 
 
## Setup of syntax coloring.
##
## Format:
##
## syntax "short description" ["filename regex" ...]
##
## The "none" syntax is reserved; specifying it on the command line is
## the same as not having a syntax at all.  The "default" syntax is
## special: it takes no filename regexes, and applies to files that
## don't match any other syntax's filename regexes.
##
## color foreground,background "regex" ["regex"...]
## or
## icolor foreground,background "regex" ["regex"...]
##
## "color" will do case-sensitive matches, while "icolor" will do
## case-insensitive matches.
##
## Valid colors: white, black, red, blue, green, yellow, magenta, cyan.
## For foreground colors, you may use the prefix "bright" to get a
## stronger highlight.
##
## To use multi-line regexes, use the start="regex" end="regex"
## [start="regex" end="regex"...] format.
##
## If your system supports transparency, not specifying a background
## color will use a transparent color.  If you don't want this, be sure
## to set the background color to black or white.
##
## All regexes should be extended regular expressions.
##
## If you wish, you may put your syntax definitions in separate files.
## You can make use of such files as follows:
##
## include "/path/to/syntax_file.nanorc"
##
## Unless otherwise noted, the name of the syntax file (without the
## ".nanorc" extension) should be the same as the "short description"
## name inside that file.  These names are kept fairly short to make
## them easier to remember and faster to type using nano's -Y option.
##
## To include all existing syntax definitions, you can do:
include "/usr/share/nano/*.nanorc"
 
 
## Key bindings.
## See nanorc(5) (section REBINDING KEYS) for more details on this.
##
## The following two functions are not bound to any key by default.
## You may wish to choose other keys than the ones suggested here.
# bind M-B cutwordleft main
# bind M-N cutwordright main
 
## Set this if your Backspace key sends Del most of the time.
# bind Del backspace all

• TP : nano par l'exemple

• Le site officiel de GNU nano (us)
• Le lien en français pour tout comprendre des options nanorc
• Nano, sur ubuntu-fr
• Nano, l'éditeur de texte du débutant, sur OpenClassrooms
• Introduction à l'édition de texte avancée, sur OpenClassrooms