doc: move section "Key bindings" at top level, add section title "Configuration" (user's guide)

1 files changed, 557 insertions, 543 deletions

diff --git a/doc/it/weechat_user.it.adoc b/doc/it/weechat_user.it.adoc
index 679ece67e..98eaadbf9 100644
--- a/doc/it/weechat_user.it.adoc
+++ b/doc/it/weechat_user.it.adoc
@@ -697,6 +697,58 @@ Some environment variables are used by WeeChat if they are defined:
 |===
 
 // TRANSLATION MISSING
+[[colors_support]]
+=== Colors support
+
+WeeChat può usare fino a 32767 coppie di colore per visualizzare il testo nelle barre e
+nell'area di chat(il terminale deve supportare 256 colori per essere utilizzati in WeeChat).
+
+In base al valore della variabile di ambiente _TERM_, potrebbero verificarsi i
+seguenti limiti per i colori in WeeChat:
+
+[width="75%",cols="8,>3,>3",options="header"]
+|===
+| $TERM                                  | Colori | Coppie
+| "rxvt-unicode", "xterm", ...           |     88 |  32767
+| "rxvt-256color", "xterm-256color", ... |    256 |  32767
+| "screen"                               |      8 |     64
+| "screen-256color"                      |    256 |  32767
+| "tmux"                                 |      8 |     64
+| "tmux-256color"                        |    256 |  32767
+|===
+
+È possibile eseguire `weechat --colors` o utilizzare il comando `/color` in
+WeeChat per visualizzare i limiti del proprio ambiente.
+
+Alcuni valori raccomandati per _TERM_ se si desiderano 256 colori:
+
+* con screen: _screen-256color_
+// TRANSLATION MISSING
+* under tmux: _screen-256color_ or _tmux-256color_
+// TRANSLATION MISSING
+* outside screen/tmux: _xterm-256color_, _rxvt-256color_, _putty-256color_, ...
+
+[NOTE]
+Potrebbe essere necessario installare il pacchetto "ncurses-term" per usare
+questi valori nella variabile _TERM_.
+
+Se si sta utilizzando screen, è possibile aggiungere questa riga al
+proprio _~/.screenrc_:
+
+----
+term screen-256color
+----
+
+// TRANSLATION MISSING
+If your _TERM_ variable has wrong value and that WeeChat is already running,
+you can change it with these two commands:
+
+----
+/set env TERM screen-256color
+/upgrade
+----
+
+// TRANSLATION MISSING
 [[files_and_directories]]
 === Files and directories
 
@@ -1047,157 +1099,6 @@ kbd:[!]
 Nel plugin irc, si possono riorganizzare i colori usando l'opzione
 <<option_irc.color.mirc_remap,irc.color.mirc_remap>>.
 
-[[colors]]
-=== Colori
-
-WeeChat può usare fino a 32767 coppie di colore per visualizzare il testo nelle barre e
-nell'area di chat(il terminale deve supportare 256 colori per essere utilizzati in WeeChat).
-
-In base al valore della variabile di ambiente _TERM_, potrebbero verificarsi i
-seguenti limiti per i colori in WeeChat:
-
-[width="75%",cols="8,>3,>3",options="header"]
-|===
-| $TERM                                  | Colori | Coppie
-| "rxvt-unicode", "xterm", ...           |     88 |  32767
-| "rxvt-256color", "xterm-256color", ... |    256 |  32767
-| "screen"                               |      8 |     64
-| "screen-256color"                      |    256 |  32767
-| "tmux"                                 |      8 |     64
-| "tmux-256color"                        |    256 |  32767
-|===
-
-È possibile eseguire `weechat --colors` o utilizzare il comando `/color` in
-WeeChat per visualizzare i limiti del proprio ambiente.
-
-Alcuni valori raccomandati per _TERM_ se si desiderano 256 colori:
-
-* con screen: _screen-256color_
-// TRANSLATION MISSING
-* under tmux: _screen-256color_ or _tmux-256color_
-// TRANSLATION MISSING
-* outside screen/tmux: _xterm-256color_, _rxvt-256color_, _putty-256color_, ...
-
-[NOTE]
-Potrebbe essere necessario installare il pacchetto "ncurses-term" per usare
-questi valori nella variabile _TERM_.
-
-Se si sta utilizzando screen, è possibile aggiungere questa riga al
-proprio _~/.screenrc_:
-
-----
-term screen-256color
-----
-
-// TRANSLATION MISSING
-If your _TERM_ variable has wrong value and that WeeChat is already running,
-you can change it with these two commands:
-
-----
-/set env TERM screen-256color
-/upgrade
-----
-
-[[colors_basic]]
-==== Colori base
-
-I colori base in WeeChat sono:
-
-[width="75%",cols="1m,4",options="header"]
-|===
-| Nome         | Colore
-| default      | Colore predefinito del terminale (trasparente per lo sfondo)
-| black        | Nero
-| darkgray     | Grigio scuro
-| red          | Rosso scuro
-| lightred     | Rosso chiaro
-| green        | Verde scuro
-| lightgreen   | Verde chiaro
-| brown        | Marrone
-| yellow       | Giallo
-| blue         | Blu scuro
-| lightblue    | Blu chiaro
-| magenta      | Rosa scuro
-| lightmagenta | Rosa chiaro
-| cyan         | Azzurro scuro
-| lightcyan    | Azzurro chiaro
-| gray         | Grigio
-| white        | Bianco
-|===
-
-[[colors_extended]]
-==== Colori estesi
-
-WeeChat alloca dinamicamente le coppie colore quando vengono usati i colori
-sullo schermo (per mostrare buffer e barre).
-
-In aggiunta ai colori di base, si può usare un numero per il colore compreso
-tra 1 e il limite del proprio terminale.
-
-Il comando `/color` mostra i colori attivi ed i limiti. Com kbd:[Alt+c] si può
-passare temporaneamente ai colori del terminale per sceglierne uno.
-
-Se ad esempio si desidera visualizzare l'ora in arancione nel buffer:
-
-----
-/set weechat.color.chat_time 214
-----
-
-O se si desidera uno sfondo verde scuro per la barra di stato:
-
-----
-/set weechat.bar.status.color_bg 22
-----
-
-[[colors_aliases]]
-==== Alias
-
-Si possono aggiungere degli alias ai colori con il comando `/color alias` e
-usarli in ogni opzione relativa al colore.
-
-Ad esempio:
-
-----
-/color alias 214 orange
-/set weechat.color.chat_delimiters orange
-----
-
-[[colors_attributes]]
-==== Attributi
-
-Esistono alcuni attributi per i colori. Uno o più attributi vanno aggiunti prima
-del nome o del numero del colore:
-
-* `+*+` : testo in grassetto
-* `+!+` : video inverso
-* `+/+` : testo in corsivo
-* `+_+` : testo sottolineato
-* `+|+` : mantiene attributi: non ripristina grassetto/inverso/sottolineato
-  al cambio di colore
-
-Ad esempio se si vuole il proprio nick bianco e sottolineato:
-
-----
-/set weechat.color.chat_nick_self _white
-----
-
-O se si desidera l'ora nella barra di stato arancione sottolineata
-e in grassetto:
-
-----
-/set weechat.color.status_time *_214
-----
-
-Per usare un attributo con il colore predefinito del terminale (-1), bisogna
-usare un numero maggiore dell'ultimo colore del terminale, ad esempio il
-numero massimo in WeeChat: 99999.
-
-Esempio di grassetto con il colore di primo piano del terminale:
-
-----
-/set weechat.color.status_time *99999
-----
-
 [[buffers_and_windows]]
 === Buffer e finestre
 
@@ -1537,240 +1438,6 @@ By default WeeChat and its default plugins interpret these variables:
 External plugins and scripts can define and use other local variables.
 
 // TRANSLATION MISSING
-[[bars]]
-=== Bars
-
-A _bar_ is an area beside the chat that can contain any type of text.
-
-The bar options can be set with options `weechat.bar.name.option` where `name`
-is the name of the bar and `option` the option for this bar.
-
-List of bar options:
-
-[width="100%",cols="2m,2,10",options="header"]
-|===
-| Option | Values | Description
-
-| type | `root`, `window` |
-// TRANSLATION MISSING
-  A bar with type `root` is displayed exactly one time on screen, outside all
-  windows. The default bar _buflist_ has type `root`. +
-  A bar with type `window` is displayed in each window, for example if you
-  split one time the screen (with `/window splith` or `/window splitv`), you
-  will have one bar in each window. The default bars _title_, _status_,
-  _input_ and _nicklist_ have type `window`.
-
-| position | `top`, `bottom`, `left`, `right` |
-  Position of the bar: above/below chat, on the left/right.
-
-| priority | integer ≥ 0 |
-  Priority for display of bar: this is used for ordering the bars on screen when
-  many bars have same type and position. +
-  The bars are displayed from the edge of the screen to the center. A higher
-  priority will display bar at the beginning, so closer to the edge. +
-  Example: _input_ bar has priority 1000, so it is displayed before the _status_
-  bar, which has priority 500.
-
-| size | integer ≥ 0 |
-  The size of the bar: number of columns for position left/right, number
-  of lines for position top/bottom. A size of `0` means automatic, so the size
-  will be computed according to content displayed in bar.
-
-| size_max | integer ≥ 0 |
-  The maximum size for a bar, `0` = no limit (this option is used only if
-  `size` = `0`).
-
-| color_bg | color |
-  The default background color for the bar.
-
-| color_fg | color |
-  The default text color for the bar.
-
-| color_delim | color |
-  The color for delimiters in bar.
-
-| hidden | `on`, `off` |
-  When option is `on`, the bar is hidden. +
-  Note: instead of changing this option, the command `/bar` is preferred, for
-  example: `/bar toggle nicklist` (see command <<command_weechat_bar,/bar>>).
-
-| separator | `on`, `off` |
-  When option is `on`, a separator (line) is displayed between this bar and
-  other bars (or chat).
-
-| items | string |
-  A list of _items_ (see <<bar_items,items>> for more info).
-
-| filling_left_right | `+horizontal+`, `+vertical+`, `+columns_horizontal+`, `+columns_vertical+` |
-  Type of filling for a bar which has position `left` or `right` (see
-  <<bar_filling,filling>> for more info).
-
-| filling_top_bottom | `+horizontal+`, `+vertical+`, `+columns_horizontal+`, `+columns_vertical+` |
-  Type of filling for a bar which has position `top` or `bottom` (see
-  <<bar_filling,filling>> for more info).
-
-| conditions | string |
-  The conditions to display the bar (see <<bar_conditions,conditions>> for more
-  info).
-|===
-
-[[bar_items]]
-==== Items
-
-The option _items_ is a string with a list of bar items, separated by a comma
-(space between items on screen) or `+++` (glued items).
-
-The list of bar items is displayed with command `/bar listitems`.
-
-// TRANSLATION MISSING
-Before or after item name, you can use chars (that are not alphanumeric, `+-+`
-or `+_+`). They will be displayed before/after item with the delimiters color
-defined in bar (option _color_delim_).
-
-Example of bar with items "[time],buffer_number+:+buffer_plugin+.+buffer_name":
-
-....
-┌───────────────────────────────────────────────────────────────────────────┐
-│[12:55] 3:irc/libera.#weechat                                              │
-└───────────────────────────────────────────────────────────────────────────┘
-....
-
-// TRANSLATION MISSING
-A special syntax can be used to force the buffer used when displaying the bar
-item: "@buffer:item" (where "buffer" is the full name of buffer and "item" is
-the name of a bar item).
-
-// TRANSLATION MISSING
-This is useful in root bars, to display item for a specific buffer which is
-not displayed in the current window (or even not displayed at all).
-
-// TRANSLATION MISSING
-Example: nicklist of bitlbee in a root bar (if the bar is called
-_bitlist_ and if bitlbee server is called _bitlbee_):
-
-----
-/set weechat.bar.bitlist.items "@irc.bitlbee.&bitlbee:buffer_nicklist"
-----
-
-[[bar_filling]]
-==== Filling
-
-There are four types of filling:
-
-* `+horizontal+`: the items are displayed horizontally, from left to right. If
-  there are new lines in items, a space is used to separate lines.
-* `+vertical+`: the items are displayed from top to bottom. If there are new
-  lines in items, a new line is used to separate lines.
-* `+columns_horizontal+`: items are displayed using columns, where text is
-  aligned on the left. The first item is on top left, the second is on same
-  line, on the right.
-* `+columns_vertical+`: items are displayed using columns, where text is aligned
-  on the left. The first item is on top left, the second is one line below.
-
-Default bars _title_, _status_ and _input_ have _horizontal_ filling, and
-default bar _nicklist_ has _vertical_ filling.
-
-Some examples of filling for bar _nicklist_:
-
-....
-┌───────────────────────────────────────────────────────────────────────┐
-│Welcome to #test, this is a test channel                               │
-│12:54:15 peter | hey!                                         │@carl   │
-│12:55:01  +Max | hello                                        │@jessika│
-│                                                              │@maddy  │
-│                                                              │%Diego  │
-│                                                              │%Melody │
-│                                                              │+Max    │
-│                                                              │ celia  │
-│                                                              │ Eva    │
-│                                                              │ freddy │
-│                                                              │ Harold^│
-│                                                              │ henry4 │
-│                                                              │ jimmy17│
-│                                                              │ jodie ▼│
-│[12:55] [6] [irc/libera] 3:#test(+n){24}                               │
-│[@carl] █                                                              │
-└───────────────────────────────────────────────────────────────────────┘
-                                     filling_left_right = vertical ▲
-
-┌───────────────────────────────────────────────────────────────────────┐
-│Welcome to #test, this is a test channel                               │
-│12:54:15 peter | hey!                                │@carl     lee    │
-│12:55:01  +Max | hello                               │@jessika  louise │
-│                                                     │@maddy    mario  │
-│                                                     │%Diego    mark   │
-│                                                     │%Melody   peter  │
-│                                                     │+Max      Rachel │
-│                                                     │ celia    richard│
-│                                                     │ Eva      sheryl │
-│                                                     │ freddy   Vince  │
-│                                                     │ Harold^  warren │
-│                                                     │ henry4   zack   │
-│                                                     │ jimmy17         │
-│                                                     │ jodie           │
-│[12:55] [6] [irc/libera] 3:#test(+n){24}                               │
-│[@carl] █                                                              │
-└───────────────────────────────────────────────────────────────────────┘
-                             filling_left_right = columns_vertical ▲
-
-┌───────────────────────────────────────────────────────────────────────┐
-│@carl    %Diego    celia    Harold^  jodie    mario    Rachel   Vince  │
-│@jessika %Melody   Eva      henry4   lee      mark     richard  warren │
-│@maddy   +Max      freddy   jimmy17  louise   peter    sheryl   zack   │
-│───────────────────────────────────────────────────────────────────────│
-│                                                                       │
-        filling_top_bottom = columns_vertical ▲
-
-┌───────────────────────────────────────────────────────────────────────┐
-│@carl    @jessika @maddy   %Diego   %Melody  +Max      celia    Eva    │
-│ freddy   Harold^  henry4   jimmy17  jodie    lee      louise   mario  │
-│ mark     peter    Rachel   richard  sheryl   Vince    warren   zack   │
-│───────────────────────────────────────────────────────────────────────│
-│                                                                       │
-      filling_top_bottom = columns_horizontal ▲
-....
-
-[[bar_conditions]]
-==== Conditions
-
-// TRANSLATION MISSING
-The option _conditions_ is a string which is evaluated to know if the bar
-must be displayed or not.
-
-The string can be:
-
-* _active_: the window must be active
-* _inactive_: the window must be inactive
-* _nicklist_: the buffer displayed in window must have a nicklist
-* an expression: it is evaluated as boolean (see command
-  <<command_weechat_eval,/eval>>)
-
-For the expression, following variables are available:
-
-* `+${active}+`: true if window is active
-* `+${inactive}+`: true if window is inactive
-* `+${nicklist}+`: true if buffer displayed in window has a nicklist
-
-Following pointers are available:
-
-* `+${window}+`: the window where condition is evaluated
-* `+${buffer}+`: the buffer of window where condition is evaluated
-
-Example to display nicklist bar in all buffers with a nicklist, and only if
-width of terminal is > 100:
-
-----
-/set weechat.bar.nicklist.conditions "${nicklist} && ${info:term_width} > 100"
-----
-
-Same condition, but always display nicklist on buffer _&bitlbee_
-(even if terminal is small):
-
-----
-/set weechat.bar.nicklist.conditions "${nicklist} && (${info:term_width} > 100 || ${buffer.full_name} == irc.bitlbee.&bitlbee)"
-----
-
-// TRANSLATION MISSING
 [[bare_display]]
 === Bare display
 
@@ -1858,159 +1525,20 @@ The screen will look like that in bare display:
 So you can click the URL from _joe_ without any problem in your terminal (of
 course this supposes that your terminal supports click on URLs).
 
-[[notify_levels]]
-=== Livelli di notifica
-
-// TRANSLATION MISSING
-[[setup_notify_levels]]
-==== Setup notify levels
-
-Sono possibili quattro livelli per i messaggi mostrati nei buffer, dal più basso
-al più alto:
-
-* _low_: messaggio di bassa importanza (ad esempio entrata/uscita/disconnessione
-  di irc)
-* _message_: messaggio da un utente
-* _private_: messaggio in un buffer privato
-* _highlight_: messaggio con notifica
-
-Ogni buffer ha un livello di notifica, che viene usato per decidere quale
-messaggio il buffer andrà ad aggiungere nella hotlist.
-
-Il livello predefinito di notifica può essere impostato usando l'opzione
-<<option_weechat.look.buffer_notify_default,weechat.look.buffer_notify_default>>,
-il valore predefinito è _all_.
-
-[width="75%",cols="2m,7",options="header"]
-|===
-| Livello di notifica | Livello del messaggio aggiunto alla hotlist
-| none                | (nessuno)
-| highlight           | _highlight_ + _private_
-| message             | _highlight_ + _private_ + _message_
-| all                 | _highlight_ + _private_ + _message_ + _low_
-|===
-
-Il livello di notifica può essere definito per un set di buffer, ad esempio
-tutti i buffer per il server irc "libera":
-
-----
-/set weechat.notify.irc.libera message
-----
-
-Imposta il livello di notifica _highlight_ solo sul canale _#weechat_:
-
-----
-/set weechat.notify.irc.libera.#weechat highlight
-----
-
-Il livello di notifica per un buffer può essere impostato con il comando `/buffer`:
-
-----
-/buffer notify highlight
-----
-
 // TRANSLATION MISSING
-[[max_hotlist_level_nicks]]
-==== Max hotlist level for nicks
-
-It is possible to set max hotlist level for some nicks, per buffer, or per group
-of buffers (like IRC servers).
-
-The buffer property "hotlist_max_level_nicks" can be set with a list of nicks
-and for each nick the max hotlist level to trigger, possible levels are:
-
-* -1: no hotlist changes for nick
-* 0: low priority (like join/part messages)
-* 1: message
-* 2: private message
-* 3: highlight (in fact useless, since it's already the default max for all messages)
-
-For example to disable highlights from "joe" and "mike" on current buffer:
-
-----
-/buffer set hotlist_max_level_nicks_add joe:2,mike:2
-----
-
-[NOTE]
-The buffer property "hotlist_max_level_nicks" is not saved in configuration. +
-You can easily save it with the script _buffer_autoset.py_: you can install it
-with `+/script install buffer_autoset.py+` and get help with `+/help buffer_autoset+`.
+[[key_bindings]]
+== Key bindings
 
 // TRANSLATION MISSING
-[[highlights]]
-=== Highlights
-
-[[highlights_words]]
-==== Add words to highlight
-
-By default, WeeChat highlights messages from other users containing your nick,
-therefore the highlight depends on the buffer (the nick can be different from
-one buffer to another).
-
-You can add other words to highlight with the option
-<<option_weechat.look.highlight,weechat.look.highlight>>, for example to
-highlight your nick and "word1", "word2" and all words beginning with "test":
-
-----
-/set weechat.look.highlight word1,word2,test*
-----
-
-If you need a more specific rule for the word, you can use regular expressions
-with the option <<option_weechat.look.highlight_regex,weechat.look.highlight_regex>>,
-for example to highlight words "flashcode", "flashcöde" and "flashy":
-
-----
-/set weechat.look.highlight_regex flashc[oö]de|flashy
-----
-
-The delimiters around words to highlight can be customized with the option
-<<option_weechat.look.word_chars_highlight,weechat.look.word_chars_highlight>>.
-
-[[highlights_tags]]
-==== Add tags to highlight
-
-Lines displayed can contain "tags", which give some info about the origin of
-message or the message itself. +
-You can display tags with the command `/debug tags` (same command to hide them).
-
-You can add specific tags to highlight with the option
-<<option_weechat.look.highlight_tags,weechat.look.highlight_tags>>.
-Tags are separated by commas, and multiple tags can be separated by `+++` to do
-a logical "and" between them.
-
-For example to highlight all messages from nick "FlashCode" and all notices
-from nicks beginning with "toto":
-
-----
-/set weechat.look.highlight_tags "nick_flashcode,irc_notice+nick_toto*"
-----
-
-[[highlights_regex_buffer]]
-==== Set extra highlights on buffer
-
-You can force highlight using a regular expression with the buffer property
-"highlight_regex".
-
-For example to force the highlight on all messages in the current buffer:
-
-----
-/buffer set highlight_regex .*
-----
-
-[NOTE]
-The buffer property "highlight_regex" is not saved in configuration. +
-You can easily save it with the script _buffer_autoset.py_: you can install it
-with `+/script install buffer_autoset.py+` and get help with `+/help buffer_autoset+`.
-
-[[key_bindings]]
-=== Associazione tasti predefinita
+WeeChat provides a lot of default key bindings, listed in the following chapters. +
+They can be changed and new ones can be added with the <<command_weechat_key,/key>> command.
 
 [[key_bindings_command_line]]
-==== Tasti per la riga di comando
+=== Tasti per la riga di comando
 
 // TRANSLATION MISSING
 [[key_bindings_cmdline_cursor_movement]]
-===== Cursor movement
+==== Cursor movement
 
 [width="100%",cols="^.^3,.^8,.^5",options="header"]
 |===
@@ -2031,7 +1559,7 @@ with `+/script install buffer_autoset.py+` and get help with `+/help buffer_auto
 
 // TRANSLATION MISSING
 [[key_bindings_cmdline_editing]]
-===== Editing
+==== Editing
 
 [width="100%",cols="^.^3,.^8,.^5",options="header"]
 |===
@@ -2066,7 +1594,7 @@ with `+/script install buffer_autoset.py+` and get help with `+/help buffer_auto
 
 // TRANSLATION MISSING
 [[key_bindings_cmdline_color_codes]]
-===== Color codes
+==== Color codes
 
 [width="100%",cols="^.^3,.^8,.^5",options="header"]
 |===
@@ -2081,7 +1609,7 @@ with `+/script install buffer_autoset.py+` and get help with `+/help buffer_auto
 
 // TRANSLATION MISSING
 [[key_bindings_cmdline_history]]
-===== Command history
+==== Command history
 
 [width="100%",cols="^.^3,.^8,.^5",options="header"]
 |===
@@ -2094,7 +1622,7 @@ with `+/script install buffer_autoset.py+` and get help with `+/help buffer_auto
 
 // TRANSLATION MISSING
 [[key_bindings_buffers]]
-==== Buffers
+=== Buffers
 
 [width="100%",cols="^.^3,.^8,.^5",options="header"]
 |===
@@ -2135,7 +1663,7 @@ with `+/script install buffer_autoset.py+` and get help with `+/help buffer_auto
 
 // TRANSLATION MISSING
 [[key_bindings_windows]]
-==== Windows
+=== Windows
 
 [width="100%",cols="^.^3,.^8,.^5",options="header"]
 |===
@@ -2155,7 +1683,7 @@ with `+/script install buffer_autoset.py+` and get help with `+/help buffer_auto
 |===
 
 [[key_bindings_bars]]
-==== Bars
+=== Bars
 
 [width="100%",cols="^.^3,.^8,.^5",options="header"]
 |===
@@ -2185,7 +1713,7 @@ with `+/script install buffer_autoset.py+` and get help with `+/help buffer_auto
 |===
 
 [[key_bindings_hotlist]]
-==== Hotlist
+=== Hotlist
 
 [width="100%",cols="^.^3,.^8,.^5",options="header"]
 |===
@@ -2203,7 +1731,7 @@ with `+/script install buffer_autoset.py+` and get help with `+/help buffer_auto
 
 // TRANSLATION MISSING
 [[key_bindings_toggle_keys]]
-==== Toggle keys
+=== Toggle keys
 
 [width="100%",cols="^.^3,.^8,.^5",options="header"]
 |===
@@ -2218,7 +1746,7 @@ with `+/script install buffer_autoset.py+` and get help with `+/help buffer_auto
 
 // TRANSLATION MISSING
 [[key_bindings_search_context]]
-==== Search context
+=== Search context
 
 Questi tasti sono usati nel contesto "search" (quando viene digitato
 kbd:[Ctrl+r] per cercare del testo nel buffer).
@@ -2243,7 +1771,7 @@ kbd:[Ctrl+r] per cercare del testo nel buffer).
 
 // TRANSLATION MISSING
 [[key_bindings_cursor_context]]
-==== Cursor context
+=== Cursor context
 
 Questi tasti sono usati nel contesto "cursor" (movimento libero del cursore
 sullo schermo.
@@ -2274,7 +1802,7 @@ sullo schermo.
 
 // TRANSLATION MISSING
 [[key_bindings_mouse]]
-==== Mouse
+=== Mouse
 
 // TRANSLATION MISSING
 These mouse actions are possible only if mouse is enabled with key kbd:[Alt+m]
@@ -2349,7 +1877,7 @@ These mouse actions are possible only if mouse is enabled with key kbd:[Alt+m]
 
 // TRANSLATION MISSING
 [[key_bindings_fset_buffer]]
-==== Fset buffer
+=== Fset buffer
 
 // TRANSLATION MISSING
 These keys and actions are used on the fset buffer (see <<fset_plugin,Fset plugin>>).
@@ -2399,7 +1927,7 @@ These keys and actions are used on the fset buffer (see <<fset_plugin,Fset plugi
 
 // TRANSLATION MISSING
 [[key_bindings_script_buffer]]
-==== Script buffer
+=== Script buffer
 
 // TRANSLATION MISSING
 These keys and actions are used on the script buffer (see <<scripts_plugins,Script plugin>>).
@@ -2425,6 +1953,258 @@ These keys and actions are used on the script buffer (see <<scripts_plugins,Scri
 [NOTE]
 ^(1)^ The action must be entered as input on the command line, followed by kbd:[Enter].
 
+// TRANSLATION MISSING
+[[configuration]]
+== Configuration
+
+// TRANSLATION MISSING
+[[colors]]
+=== Colors
+
+[[colors_basic]]
+==== Colori base
+
+I colori base in WeeChat sono:
+
+[width="75%",cols="1m,4",options="header"]
+|===
+| Nome         | Colore
+| default      | Colore predefinito del terminale (trasparente per lo sfondo)
+| black        | Nero
+| darkgray     | Grigio scuro
+| red          | Rosso scuro
+| lightred     | Rosso chiaro
+| green        | Verde scuro
+| lightgreen   | Verde chiaro
+| brown        | Marrone
+| yellow       | Giallo
+| blue         | Blu scuro
+| lightblue    | Blu chiaro
+| magenta      | Rosa scuro
+| lightmagenta | Rosa chiaro
+| cyan         | Azzurro scuro
+| lightcyan    | Azzurro chiaro
+| gray         | Grigio
+| white        | Bianco
+|===
+
+[[colors_extended]]
+==== Colori estesi
+
+WeeChat alloca dinamicamente le coppie colore quando vengono usati i colori
+sullo schermo (per mostrare buffer e barre).
+
+In aggiunta ai colori di base, si può usare un numero per il colore compreso
+tra 1 e il limite del proprio terminale.
+
+Il comando `/color` mostra i colori attivi ed i limiti. Com kbd:[Alt+c] si può
+passare temporaneamente ai colori del terminale per sceglierne uno.
+
+Se ad esempio si desidera visualizzare l'ora in arancione nel buffer:
+
+----
+/set weechat.color.chat_time 214
+----
+
+O se si desidera uno sfondo verde scuro per la barra di stato:
+
+----
+/set weechat.bar.status.color_bg 22
+----
+
+[[colors_aliases]]
+==== Alias
+
+Si possono aggiungere degli alias ai colori con il comando `/color alias` e
+usarli in ogni opzione relativa al colore.
+
+Ad esempio:
+
+----
+/color alias 214 orange
+/set weechat.color.chat_delimiters orange
+----
+
+[[colors_attributes]]
+==== Attributi
+
+Esistono alcuni attributi per i colori. Uno o più attributi vanno aggiunti prima
+del nome o del numero del colore:
+
+* `+*+` : testo in grassetto
+* `+!+` : video inverso
+* `+/+` : testo in corsivo
+* `+_+` : testo sottolineato
+* `+|+` : mantiene attributi: non ripristina grassetto/inverso/sottolineato
+  al cambio di colore
+
+Ad esempio se si vuole il proprio nick bianco e sottolineato:
+
+----
+/set weechat.color.chat_nick_self _white
+----
+
+O se si desidera l'ora nella barra di stato arancione sottolineata
+e in grassetto:
+
+----
+/set weechat.color.status_time *_214
+----
+
+Per usare un attributo con il colore predefinito del terminale (-1), bisogna
+usare un numero maggiore dell'ultimo colore del terminale, ad esempio il
+numero massimo in WeeChat: 99999.
+
+Esempio di grassetto con il colore di primo piano del terminale:
+
+----
+/set weechat.color.status_time *99999
+----
+
+[[notify_levels]]
+=== Livelli di notifica
+
+// TRANSLATION MISSING
+[[setup_notify_levels]]
+==== Setup notify levels
+
+Sono possibili quattro livelli per i messaggi mostrati nei buffer, dal più basso
+al più alto:
+
+* _low_: messaggio di bassa importanza (ad esempio entrata/uscita/disconnessione
+  di irc)
+* _message_: messaggio da un utente
+* _private_: messaggio in un buffer privato
+* _highlight_: messaggio con notifica
+
+Ogni buffer ha un livello di notifica, che viene usato per decidere quale
+messaggio il buffer andrà ad aggiungere nella hotlist.
+
+Il livello predefinito di notifica può essere impostato usando l'opzione
+<<option_weechat.look.buffer_notify_default,weechat.look.buffer_notify_default>>,
+il valore predefinito è _all_.
+
+[width="75%",cols="2m,7",options="header"]
+|===
+| Livello di notifica | Livello del messaggio aggiunto alla hotlist
+| none                | (nessuno)
+| highlight           | _highlight_ + _private_
+| message             | _highlight_ + _private_ + _message_
+| all                 | _highlight_ + _private_ + _message_ + _low_
+|===
+
+Il livello di notifica può essere definito per un set di buffer, ad esempio
+tutti i buffer per il server irc "libera":
+
+----
+/set weechat.notify.irc.libera message
+----
+
+Imposta il livello di notifica _highlight_ solo sul canale _#weechat_:
+
+----
+/set weechat.notify.irc.libera.#weechat highlight
+----
+
+Il livello di notifica per un buffer può essere impostato con il comando `/buffer`:
+
+----
+/buffer notify highlight
+----
+
+// TRANSLATION MISSING
+[[max_hotlist_level_nicks]]
+==== Max hotlist level for nicks
+
+It is possible to set max hotlist level for some nicks, per buffer, or per group
+of buffers (like IRC servers).
+
+The buffer property "hotlist_max_level_nicks" can be set with a list of nicks
+and for each nick the max hotlist level to trigger, possible levels are:
+
+* -1: no hotlist changes for nick
+* 0: low priority (like join/part messages)
+* 1: message
+* 2: private message
+* 3: highlight (in fact useless, since it's already the default max for all messages)
+
+For example to disable highlights from "joe" and "mike" on current buffer:
+
+----
+/buffer set hotlist_max_level_nicks_add joe:2,mike:2
+----
+
+[NOTE]
+The buffer property "hotlist_max_level_nicks" is not saved in configuration. +
+You can easily save it with the script _buffer_autoset.py_: you can install it
+with `+/script install buffer_autoset.py+` and get help with `+/help buffer_autoset+`.
+
+// TRANSLATION MISSING
+[[highlights]]
+=== Highlights
+
+[[highlights_words]]
+==== Add words to highlight
+
+By default, WeeChat highlights messages from other users containing your nick,
+therefore the highlight depends on the buffer (the nick can be different from
+one buffer to another).
+
+You can add other words to highlight with the option
+<<option_weechat.look.highlight,weechat.look.highlight>>, for example to
+highlight your nick and "word1", "word2" and all words beginning with "test":
+
+----
+/set weechat.look.highlight word1,word2,test*
+----
+
+If you need a more specific rule for the word, you can use regular expressions
+with the option <<option_weechat.look.highlight_regex,weechat.look.highlight_regex>>,
+for example to highlight words "flashcode", "flashcöde" and "flashy":
+
+----
+/set weechat.look.highlight_regex flashc[oö]de|flashy
+----
+
+The delimiters around words to highlight can be customized with the option
+<<option_weechat.look.word_chars_highlight,weechat.look.word_chars_highlight>>.
+
+[[highlights_tags]]
+==== Add tags to highlight
+
+Lines displayed can contain "tags", which give some info about the origin of
+message or the message itself. +
+You can display tags with the command `/debug tags` (same command to hide them).
+
+You can add specific tags to highlight with the option
+<<option_weechat.look.highlight_tags,weechat.look.highlight_tags>>.
+Tags are separated by commas, and multiple tags can be separated by `+++` to do
+a logical "and" between them.
+
+For example to highlight all messages from nick "FlashCode" and all notices
+from nicks beginning with "toto":
+
+----
+/set weechat.look.highlight_tags "nick_flashcode,irc_notice+nick_toto*"
+----
+
+[[highlights_regex_buffer]]
+==== Set extra highlights on buffer
+
+You can force highlight using a regular expression with the buffer property
+"highlight_regex".
+
+For example to force the highlight on all messages in the current buffer:
+
+----
+/buffer set highlight_regex .*
+----
+
+[NOTE]
+The buffer property "highlight_regex" is not saved in configuration. +
+You can easily save it with the script _buffer_autoset.py_: you can install it
+with `+/script install buffer_autoset.py+` and get help with `+/help buffer_autoset+`.
+
 [[mouse]]
 === Supporto del mouse
 
@@ -2549,6 +2329,240 @@ poi eseguire l'evento col mouse. Il comando inserisce il nome dell'evento
 nella riga di comando.
 
 // TRANSLATION MISSING
+[[bars]]
+=== Bars
+
+A _bar_ is an area beside the chat that can contain any type of text.
+
+The bar options can be set with options `weechat.bar.name.option` where `name`
+is the name of the bar and `option` the option for this bar.
+
+List of bar options:
+
+[width="100%",cols="2m,2,10",options="header"]
+|===
+| Option | Values | Description
+
+| type | `root`, `window` |
+// TRANSLATION MISSING
+  A bar with type `root` is displayed exactly one time on screen, outside all
+  windows. The default bar _buflist_ has type `root`. +
+  A bar with type `window` is displayed in each window, for example if you
+  split one time the screen (with `/window splith` or `/window splitv`), you
+  will have one bar in each window. The default bars _title_, _status_,
+  _input_ and _nicklist_ have type `window`.
+
+| position | `top`, `bottom`, `left`, `right` |
+  Position of the bar: above/below chat, on the left/right.
+
+| priority | integer ≥ 0 |
+  Priority for display of bar: this is used for ordering the bars on screen when
+  many bars have same type and position. +
+  The bars are displayed from the edge of the screen to the center. A higher
+  priority will display bar at the beginning, so closer to the edge. +
+  Example: _input_ bar has priority 1000, so it is displayed before the _status_
+  bar, which has priority 500.
+
+| size | integer ≥ 0 |
+  The size of the bar: number of columns for position left/right, number
+  of lines for position top/bottom. A size of `0` means automatic, so the size
+  will be computed according to content displayed in bar.
+
+| size_max | integer ≥ 0 |
+  The maximum size for a bar, `0` = no limit (this option is used only if
+  `size` = `0`).
+
+| color_bg | color |
+  The default background color for the bar.
+
+| color_fg | color |
+  The default text color for the bar.
+
+| color_delim | color |
+  The color for delimiters in bar.
+
+| hidden | `on`, `off` |
+  When option is `on`, the bar is hidden. +
+  Note: instead of changing this option, the command `/bar` is preferred, for
+  example: `/bar toggle nicklist` (see command <<command_weechat_bar,/bar>>).
+
+| separator | `on`, `off` |
+  When option is `on`, a separator (line) is displayed between this bar and
+  other bars (or chat).
+
+| items | string |
+  A list of _items_ (see <<bar_items,items>> for more info).
+
+| filling_left_right | `+horizontal+`, `+vertical+`, `+columns_horizontal+`, `+columns_vertical+` |
+  Type of filling for a bar which has position `left` or `right` (see
+  <<bar_filling,filling>> for more info).
+
+| filling_top_bottom | `+horizontal+`, `+vertical+`, `+columns_horizontal+`, `+columns_vertical+` |
+  Type of filling for a bar which has position `top` or `bottom` (see
+  <<bar_filling,filling>> for more info).
+
+| conditions | string |
+  The conditions to display the bar (see <<bar_conditions,conditions>> for more
+  info).
+|===
+
+[[bar_items]]
+==== Items
+
+The option _items_ is a string with a list of bar items, separated by a comma
+(space between items on screen) or `+++` (glued items).
+
+The list of bar items is displayed with command `/bar listitems`.
+
+// TRANSLATION MISSING
+Before or after item name, you can use chars (that are not alphanumeric, `+-+`
+or `+_+`). They will be displayed before/after item with the delimiters color
+defined in bar (option _color_delim_).
+
+Example of bar with items "[time],buffer_number+:+buffer_plugin+.+buffer_name":
+
+....
+┌───────────────────────────────────────────────────────────────────────────┐
+│[12:55] 3:irc/libera.#weechat                                              │
+└───────────────────────────────────────────────────────────────────────────┘
+....
+
+// TRANSLATION MISSING
+A special syntax can be used to force the buffer used when displaying the bar
+item: "@buffer:item" (where "buffer" is the full name of buffer and "item" is
+the name of a bar item).
+
+// TRANSLATION MISSING
+This is useful in root bars, to display item for a specific buffer which is
+not displayed in the current window (or even not displayed at all).
+
+// TRANSLATION MISSING
+Example: nicklist of bitlbee in a root bar (if the bar is called
+_bitlist_ and if bitlbee server is called _bitlbee_):
+
+----
+/set weechat.bar.bitlist.items "@irc.bitlbee.&bitlbee:buffer_nicklist"
+----
+
+[[bar_filling]]
+==== Filling
+
+There are four types of filling:
+
+* `+horizontal+`: the items are displayed horizontally, from left to right. If
+  there are new lines in items, a space is used to separate lines.
+* `+vertical+`: the items are displayed from top to bottom. If there are new
+  lines in items, a new line is used to separate lines.
+* `+columns_horizontal+`: items are displayed using columns, where text is
+  aligned on the left. The first item is on top left, the second is on same
+  line, on the right.
+* `+columns_vertical+`: items are displayed using columns, where text is aligned
+  on the left. The first item is on top left, the second is one line below.
+
+Default bars _title_, _status_ and _input_ have _horizontal_ filling, and
+default bar _nicklist_ has _vertical_ filling.
+
+Some examples of filling for bar _nicklist_:
+
+....
+┌───────────────────────────────────────────────────────────────────────┐
+│Welcome to #test, this is a test channel                               │
+│12:54:15 peter | hey!                                         │@carl   │
+│12:55:01  +Max | hello                                        │@jessika│
+│                                                              │@maddy  │
+│                                                              │%Diego  │
+│                                                              │%Melody │
+│                                                              │+Max    │
+│                                                              │ celia  │
+│                                                              │ Eva    │
+│                                                              │ freddy │
+│                                                              │ Harold^│
+│                                                              │ henry4 │
+│                                                              │ jimmy17│
+│                                                              │ jodie ▼│
+│[12:55] [6] [irc/libera] 3:#test(+n){24}                               │
+│[@carl] █                                                              │
+└───────────────────────────────────────────────────────────────────────┘
+                                     filling_left_right = vertical ▲
+
+┌───────────────────────────────────────────────────────────────────────┐
+│Welcome to #test, this is a test channel                               │
+│12:54:15 peter | hey!                                │@carl     lee    │
+│12:55:01  +Max | hello                               │@jessika  louise │
+│                                                     │@maddy    mario  │
+│                                                     │%Diego    mark   │
+│                                                     │%Melody   peter  │
+│                                                     │+Max      Rachel │
+│                                                     │ celia    richard│
+│                                                     │ Eva      sheryl │
+│                                                     │ freddy   Vince  │
+│                                                     │ Harold^  warren │
+│                                                     │ henry4   zack   │
+│                                                     │ jimmy17         │
+│                                                     │ jodie           │
+│[12:55] [6] [irc/libera] 3:#test(+n){24}                               │
+│[@carl] █                                                              │
+└───────────────────────────────────────────────────────────────────────┘
+                             filling_left_right = columns_vertical ▲
+
+┌───────────────────────────────────────────────────────────────────────┐
+│@carl    %Diego    celia    Harold^  jodie    mario    Rachel   Vince  │
+│@jessika %Melody   Eva      henry4   lee      mark     richard  warren │
+│@maddy   +Max      freddy   jimmy17  louise   peter    sheryl   zack   │
+│───────────────────────────────────────────────────────────────────────│
+│                                                                       │
+        filling_top_bottom = columns_vertical ▲
+
+┌───────────────────────────────────────────────────────────────────────┐
+│@carl    @jessika @maddy   %Diego   %Melody  +Max      celia    Eva    │
+│ freddy   Harold^  henry4   jimmy17  jodie    lee      louise   mario  │
+│ mark     peter    Rachel   richard  sheryl   Vince    warren   zack   │
+│───────────────────────────────────────────────────────────────────────│
+│                                                                       │
+      filling_top_bottom = columns_horizontal ▲
+....
+
+[[bar_conditions]]
+==== Conditions
+
+// TRANSLATION MISSING
+The option _conditions_ is a string which is evaluated to know if the bar
+must be displayed or not.
+
+The string can be:
+
+* _active_: the window must be active
+* _inactive_: the window must be inactive
+* _nicklist_: the buffer displayed in window must have a nicklist
+* an expression: it is evaluated as boolean (see command
+  <<command_weechat_eval,/eval>>)
+
+For the expression, following variables are available:
+
+* `+${active}+`: true if window is active
+* `+${inactive}+`: true if window is inactive
+* `+${nicklist}+`: true if buffer displayed in window has a nicklist
+
+Following pointers are available:
+
+* `+${window}+`: the window where condition is evaluated
+* `+${buffer}+`: the buffer of window where condition is evaluated
+
+Example to display nicklist bar in all buffers with a nicklist, and only if
+width of terminal is > 100:
+
+----
+/set weechat.bar.nicklist.conditions "${nicklist} && ${info:term_width} > 100"
+----
+
+Same condition, but always display nicklist on buffer _&bitlbee_
+(even if terminal is small):
+
+----
+/set weechat.bar.nicklist.conditions "${nicklist} && (${info:term_width} > 100 || ${buffer.full_name} == irc.bitlbee.&bitlbee)"
+----
+
+// TRANSLATION MISSING
 [[secured_data]]
 === Secured data