Translators:
-
Marco Paolone <marcopaolone@gmail.com>, 2009-2012
Questo manuale documenta il client di chat WeeChat, ed è parte del programma stesso.
Latest version of this document can be found on this page ↗.
WeeChat (Wee Enhanced Environment for Chat) è un client di chat libero, veloce e leggero, realizzato per diversi sistemi operativi.
Le principali caratteristiche:
-
multi-protocollo (mainly IRC)
-
connessione a server multipli (con TLS, IPv6, proxy)
-
piccolo, veloce e leggero
-
personalizzabile ed estensibile con plugin e script
-
conforme alle RFC di IRC 1459 ↗, 2810 ↗, 2811 ↗, 2812 ↗, 2813 ↗ e 7194 ↗
-
IRC proxy and relay for remote interfaces
-
multi-piattaforma (GNU/Linux, *BSD, macOS, Windows ed altre)
-
100% GPL, software libero
The list of all features can be found on this page ↗.
Per poter installare WeeChat, è necessario:
-
un sistema GNU/Linux in esecuzione (con gli strumenti di compilazione per i sorgenti), oppure OS compatibile
-
privilegi di root (per installare WeeChat in una directory di sistema)
-
some libraries (see dependencies).
I pacchetti binari sono disponibili per molte distribuzioni, incluse:
-
Arch Linux:
pacman -S weechat -
Cygwin (Windows): select WeeChat packages in setup.exe
-
Debian/Ubuntu (o qualunque distribuzione compatibile):
apt-get install weechat-curses weechat-plugins
For latest versions and nightly builds: Debian repositories ↗ -
Fedora Core:
dnf install weechat -
FreeBSD:
pkg install weechat -
Gentoo:
emerge weechat -
Mandriva/RedHat (o qualunque distribuzione compatibile con RPM):
rpm -i /path/per/weechat-x.y.z-1.i386.rpm -
openSUSE:
zypper in weechat -
Sourcemage:
cast weechat -
macOS (with Homebrew ↗):
brew install weechat(for help:brew info weechat)
Potrebbero risultare utili alcuni pacchetti addizionali, come weechat-plugins.
Per altre distribuzioni, consultare il manuale per le istruzioni di installazione.
Containers with WeeChat can be built or installed directly from the
Docker Hub ↗.
For more information, see the README in the
weechat-container ↗
repository.
WeeChat must be built with CMake.
|
Note
|
On macOS, you can use Homebrew ↗:
brew install --build-from-source weechat.
|
The following table shows the list of packages that are required to build WeeChat:
| Pacchetto (1) | Versione | Features |
|---|---|---|
C compiler (gcc / clang) |
Compile C sources. |
|
cmake |
≥ 3.0 |
Build. |
pkg-config |
Detect installed libraries. |
|
libncurses-dev |
Interfaccia ncurses. |
|
libcurl4-gnutls-dev |
Trasferimento URL. |
|
libgcrypt20-dev |
Secured data, IRC SASL authentication. |
|
libgnutls28-dev |
≥ 2.2.0 (2) |
IRC plugin: support of TLS connections, IRC SASL authentication (ECDSA-NIST256P-CHALLENGE). |
zlib1g-dev |
Logger plugin: compression of rotated log files (gzip). |
|
Note
|
(1) Name comes from the Debian GNU/Linux Bookworm distribution, version and
name can be different in other distributions. (2) GnuTLS ≥ 3.0.21 is required for IRC SASL authentication with mechanism ECDSA-NIST256P-CHALLENGE. |
The following table shows the list of packages that are optional to compile WeeChat:
| Pacchetto (1) | Versione | Features |
|---|---|---|
C++ compiler (g++ / clang++) |
Build and run tests, plugin JavaScript. |
|
gettext |
Internazionalizzazione (traduzione dei messaggi; la lingua base è l’inglese). |
|
ca-certificates |
Certificati per le connessioni TLS. |
|
libcjson-dev |
Relay plugin: protocol "api" (HTTP REST API). |
|
libzstd-dev |
≥ 0.8.1 |
Logger plugin: compression of rotated log files (zstandard). |
libaspell-dev / libenchant-dev |
Plugin spell. |
|
python3-dev |
≥ 3.0 |
Plugin python. |
libperl-dev |
Plugin perl. |
|
ruby3.1, ruby3.1-dev |
≥ 1.9.1 |
Plugin ruby. |
liblua5.4-dev |
Plugin lua. |
|
tcl-dev |
≥ 8.5 |
Plugin tcl. |
guile-3.0-dev |
≥ 2.0 |
Plugin guile (scheme). |
libv8-dev |
≤ 3.24.3 |
Plugin javascript. |
php-dev |
≥ 7.0 |
Plugin php. |
libphp-embed |
≥ 7.0 |
Plugin php. |
libxml2-dev |
Plugin php. |
|
libargon2-dev |
Plugin php (if PHP ≥ 7.2). |
|
libsodium-dev |
Plugin php (if PHP ≥ 7.2). |
|
asciidoctor |
≥ 1.5.4 |
Build man page and documentation. |
ruby-pygments.rb |
Build documentation. |
|
libcpputest-dev |
≥ 3.4 |
Build and run tests. |
|
Note
|
(1) Name comes from the Debian GNU/Linux Bookworm distribution, version and name can be different in other distributions. |
If you are using a Debian/Ubuntu based distribution, and if you have some "deb-src" source entries in your file /etc/apt/sources.list, you can install all dependencies with the command:
# apt-get build-dep weechat
-
Installazione nelle directory di sistema (richiede privilegi di root):
$ mkdir build $ cd build $ cmake .. $ make $ sudo make install
-
Installazione in una directory personalizzata (for example your home):
$ mkdir build $ cd build $ cmake .. -DCMAKE_INSTALL_PREFIX=/path/della/directory $ make $ make install
Options can be used for CMake, with format: -DOPTION=VALUE.
List of available options:
| Option | Values | Default value | Description |
|---|---|---|---|
|
|
The type of build: |
|
|
directory |
|
The directory where WeeChat will be installed. |
|
directory |
|
The default home directory when running WeeChat. |
|
|
|
Compile Alias plugin. |
|
|
|
Compile Buflist plugin. |
|
|
|
Compile Charset plugin. |
|
|
|
Support of JSON with cJSON ↗ library. |
|
|
|
Build man page. |
|
|
|
Build HTML documentation. |
|
|
|
Force build of documentation even if some plugins are not compiled (not recommended: docs will be incomplete). |
|
|
|
Compile Spell plugin with Enchant. |
|
|
|
Compile Exec plugin. |
|
|
|
Compile Fifo plugin. |
|
|
|
Compile Fset plugin. |
|
|
|
Compile Guile plugin (Scheme). |
|
|
|
Compile headless binary. |
|
|
|
Compile IRC plugin. |
|
|
|
Compile JavaScript plugin. |
|
|
|
Support of large files. |
|
|
|
Compile Logger plugin. |
|
|
|
Compile Lua plugin. |
|
|
|
Compile Ncurses interface. |
|
|
|
Enable NLS (translations). |
|
|
|
Compile Perl plugin. |
|
|
|
Compile PHP plugin. |
|
|
|
Compile Python plugin. |
|
|
|
Compile Relay plugin. |
|
|
|
Compile Ruby plugin. |
|
|
|
Compile Script plugin. |
|
|
|
Compile script plugins (Python, Perl, Ruby, Lua, Tcl, Guile, PHP). |
|
|
|
Compile Spell plugin. |
|
|
|
Compile Tcl plugin. |
|
|
|
Compile Trigger plugin. |
|
|
|
Compile Typing plugin. |
|
|
|
Compile Xfer plugin. |
|
|
|
Enable Zstandard ↗ compression. |
|
|
|
Compile tests. |
|
|
|
Compile with code coverage options. |
The other options can be displayed with this command:
$ cmake -LA
Or with Curses interface:
$ ccmake ..
Attenzione: i sorgenti Git sono per gli utenti avanzati: potrebbero non compilare o essere instabili. Siete avvisati!
Per ottenere i sorgenti Git, dare il comando:
$ git clone https://github.com/weechat/weechat.git
Poi seguire le istruzioni per i sorgenti (consultare sorgenti).
Nel caso in cui si verifichino errori, o si desideri segnalare qualsiasi errore futuro di WeeChat, è necessario:
-
compile with:
-
informazioni di debug (o installare il pacchetto binario con le informazioni di debug)
-
address sanitizer (optional)
-
-
abilitare i file core sul proprio sistema
-
installare gdb
You can additionally enable the address sanitizer, which causes WeeChat to crash immediately in case of problem:
$ cmake .. -DCMAKE_BUILD_TYPE=Debug -DCMAKE_C_FLAGS=-fsanitize=address -DCMAKE_CXX_FLAGS=-fsanitize=address -DCMAKE_EXE_LINKER_FLAGS=-fsanitize=address
|
Warning
|
You should enable address sanitizer only if you’re trying to cause a crash, this is not recommended in production. |
Then once compiled and installed, you must run WeeChat like this:
$ ASAN_OPTIONS="detect_odr_violation=0 log_path=asan.log" weechat
In case of crash, the backtrace is in file asan.log.
To enable core files, you can use option weechat.startup.sys_rlimit:
/set weechat.startup.sys_rlimit "core:-1"
For WeeChat ≤ 0.3.8 or if you want to enable core files even before WeeChat
starts, you can use ulimit command.
Ad esempio su Linux con la shell bash, aggiungere questa riga al proprio
~/.bashrc:
ulimit -c unlimited
Oppure impostare una dimensione massima:
ulimit -c 200000
When WeeChat crashes, your system will create a file core or core.12345 (12345 is process id) if the option is enabled. Questo file viene creato nella directory in cui è in esecuzione WeeChat (e non la directory dove WeeChat è installato!).
|
Note
|
On some systems like Archlinux, core dumps could be in another directory like
/var/lib/systemd/coredump and you must use the command coredumpctl to read it.For more information, see this wiki page ↗. |
Ad esempio, se weechat è installato in /usr/bin/ ed il file core si trova in /home/user/, allora eseguire gdb con questo comando:
gdb /usr/bin/weechat /home/user/core
All’interno di gdb, usare il comando bt full per visualizzare
il backtrace. Verrà mostrato qualcosa di simile a questo:
(gdb) set logging file /tmp/crash.txt
(gdb) set logging on
Copying output to /tmp/crash.txt.
(gdb) bt full
#0 0x00007f9dfb04a465 in raise () from /lib/libc.so.6
#1 0x00007f9dfb04b8e6 in abort () from /lib/libc.so.6
#2 0x0000000000437f66 in weechat_shutdown (return_code=1, crash=1)
at /some_path/src/core/weechat.c:351
#3 <signal handler called>
#4 0x000000000044cb24 in hook_process_timer_cb (arg_hook_process=0x254eb90,
remaining_calls=<value optimized out>) at /some_path/src/core/wee-hook.c:1364
hook_process = 0x254eb90
status = <value optimized out>
#5 0x000000000044cc7d in hook_timer_exec ()
at /some_path/src/core/wee-hook.c:1025
tv_time = {tv_sec = 1272693881, tv_usec = 212665}
ptr_hook = 0x2811f40
next_hook = 0x0
#6 0x000000000041b5b0 in gui_main_loop ()
at /some_path/src/gui/curses/gui-curses-main.c:319
hook_fd_keyboard = 0x173b600
tv_timeout = {tv_sec = 0, tv_usec = 0}
read_fds = {fds_bits = {0 <repeats 16 times>}}
write_fds = {fds_bits = {0 <repeats 16 times>}}
except_fds = {fds_bits = {0 <repeats 16 times>}}
max_fd = <value optimized out>
Bisogna riportare l’errore agli sviluppatori, e specificare quale azione ha causato l’errore.
Grazie per il vostro aiuto!
Per eseguire il debug di un’istanza di WeeChat in esecuzione (ad esempio se WeeChat sembra sia bloccato), è possibile usare gdb con l’id del processo (sostituire 12345 con il PID del processo weechat):
gdb /usr/bin/weechat 12345
Poi, come per un crash, usare il comando bt full:
(gdb) bt full
Per avviare WeeChat, digitare questo comando:
$ weechat
When you run WeeChat for the first time, the default configuration files are created in ~/.config/weechat with default options and values (see Files and directories).
Some extra options are available for debug purposes only:
|
Warning
|
Do NOT use any of these options in production! |
Some environment variables are used by WeeChat if they are defined:
| Name | Description |
|---|---|
|
The WeeChat home (with configuration files, logs, scripts, …). Same behavior as CMake option |
|
The passphrase used to decrypt secured data. |
|
An extra directory to load plugins (from the "plugins" directory in this path). |
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:
| $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
-
under tmux: screen-256color or tmux-256color
-
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
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
WeeChat uses XDG directories by default (according to the
XDG Base Directory Specification ↗).
A single home directory for all files can be forced by CMake option WEECHAT_HOME,
the environment variable WEECHAT_HOME or the command-line option -d / --dir.
When a single WeeChat home directory is not forced, XDG directories are used and set like this:
| Directory | Default value | Fallback value if $XDG_XXX is not defined |
|---|---|---|
config |
|
|
data |
|
|
cache |
|
|
runtime |
|
Same as cache directory |
The configuration files are created with default values the first time you run WeeChat.
The WeeChat directories are:
| Path (1) | Description |
|---|---|
|
WeeChat configuration files: |
|
WeeChat data files: logs, scripts, scripts data, xfer files, etc. |
|
Log files (one file per buffer). |
|
Python scripts. |
|
Python scripts auto-loaded on startup (2). |
|
Perl scripts. |
|
Perl scripts auto-loaded on startup (2). |
|
Ruby scripts. |
|
Ruby scripts auto-loaded on startup (2). |
|
Lua scripts. |
|
Lua scripts auto-loaded on startup (2). |
|
Tcl scripts. |
|
Tcl scripts auto-loaded on startup (2). |
|
Guile scripts. |
|
Guile scripts auto-loaded on startup (2). |
|
JavaScript scripts. |
|
JavaScript scripts auto-loaded on startup (2). |
|
PHP scripts. |
|
PHP scripts auto-loaded on startup (2). |
|
WeeChat cache files: scripts cache. |
|
WeeChat runtime files: FIFO pipe, Relay UNIX sockets. |
|
Note
|
(1) XDG directories may be different according to your environment variables XDG_*.(2) This directory often contains only symbolic links to scripts in parent directory. |
The files in the WeeChat home directory are:
| File | Description | Sensitive data |
|---|---|---|
|
Main WeeChat configuration file |
Possible (example: list of channels in a saved buffers layout). |
|
Configuration file with secured data |
Yes, highly sensitive: this file must never be shared with anyone. |
|
Plugins configuration file |
Possible, depends on plugins/scripts. |
|
Configuration file for alias plugin |
Possible, depends on aliases. |
|
Configuration file for buflist plugin |
No. |
|
Configuration file for charset plugin |
No. |
|
Configuration file for exec plugin |
No. |
|
Configuration file for fifo plugin |
No. |
|
Configuration file for fset plugin |
No. |
|
Configuration file for guile plugin |
No. |
|
Configuration file for irc plugin |
Yes: it can contain passwords for servers, nickserv and channels (if not stored in |
|
Configuration file for javascript plugin |
No. |
|
Configuration file for logger plugin |
No. |
|
Configuration file for lua plugin |
No. |
|
Configuration file for perl plugin |
No. |
|
Configuration file for php plugin |
No. |
|
Configuration file for python plugin |
No. |
|
Configuration file for relay plugin |
Yes: it can contain relay password and TOTP secret (if not stored in |
|
Configuration file for ruby plugin |
No. |
|
Configuration file for script plugin |
No. |
|
Configuration file for spell plugin |
No. |
|
Configuration file for tcl plugin |
No. |
|
Configuration file for trigger plugin |
Possible, depends on triggers. |
|
Configuration file for typing plugin |
No. |
|
Configuration file for xfer plugin |
No. |
|
WeeChat log file |
No. |
|
Important
|
It is not recommended to edit configuration files by hand because WeeChat
may write them at any time (for example on /quit)
and after any change you must run the command /reload
(with the risk of losing other changes that were not yet saved with
/save). You can use the command /set, which checks the value and applies immediately the changes. |
If a new stable version of WeeChat is released, this is time for you to switch to this version.
First of all, you must install the new version of WeeChat, either with your
package manager or by compiling yourself, so that the weechat binary and all
required files are in the same paths.
This can be done while WeeChat is running.
WeeChat can restart the new binary, in place, using the
/upgrade command: the buffer contents and non-TLS
connections are preserved.
The TLS connections are lost during upgrade and are restored automatically
after the upgrade (reload of TLS sessions is currently not possible
with GnuTLS).
The command can also be used if you have to restart the machine, for example to upgrade the kernel or to move your WeeChat to another machine:
/upgrade -quit
This saves the current state in *.upgrade files. You can then either reboot
or move the whole WeeChat directories (config, data, cache) to another machine,
and restart WeeChat later with this command:
$ weechat --upgrade
After an upgrade, it is strongly recommended to read the release notes ↗ which contain important information about breaking changes and some manual actions that could be required.
You must read the release notes of all versions between your old (excluded) and
your new version (included).
For example if you switch from version 3.0 to 3.2, you must read release notes
of versions 3.1 and 3.2.
WeeChat has an automatic upgrade of configuration files (*.conf):
-
new options are silently added with default value
-
obsolete options are automatically discarded and WeeChat displays a warning with the value read from file.
Example of warning when an option has been removed:
=!= Attenzione: /home/user/.config/weechat/sec.conf, riga 15: opzione sconosciuta per la sezione "crypt": passphrase_file = ""
That means the option sec.crypt.passphrase_file has been removed, and you
had value set to empty string, which was the default value in the previous version
(in this case no manual action is required).
Esempio di terminale con WeeChat:
▼ bar "buflist" ▼ bar "title"
┌──────────────────────────────────────────────────────────────────────────────────────┐
│1.libera │Welcome to #test, this is a test channel │
│ weechat│12:52:27 --> | Flashy (flashcode@weechat.org) has joined #test │@Flashy│
│2. #test│12:52:27 -- | Nicks #test: [@Flashy @joe +weebot peter] │@joe │
│3. #abc │12:52:27 -- | Channel #test: 4 nicks (2 ops, 1 voice, 1 normal) │+weebot│
│4. #def │12:52:27 -- | Channel created on Tue Jan 27 06:30:17 2009 │peter │
│5. #ghi │12:54:15 peter | hey! │ │
│ │12:55:01 @joe | hello │ │
│ │ │ │
│ │ │ │
│ │ │ │
│ │ │ │
│ │ │ │
│ │ │ │
│ │ │ │
│ │ │ │
│ │ │ │
│ │ │ │
│ │ │ │
│ │ │ │
│ │ │ │
│ │ │ │
│ │[12:55] [5] [irc/libera] 2:#test(+n){4}* [H: 3:#abc(2,5), 5] │
│ │[@Flashy(i)] hi peter!█ │
└──────────────────────────────────────────────────────────────────────────────────────┘
▲ bars "status" and "input" bar "nicklist" ▲
By default, the screen is divided up into the following areas:
-
area di chat (centro dello schermo) con le righe di chat, e per ogni riga:
-
ora
-
prefisso (prima di "|")
-
messaggio (dopo di "|")
-
-
barre che circondano l’area di chat, quelle predefinite sono:
-
barra buflist, on the left
-
barra titolo, in alto rispetto all’area di chat
-
barra stato, in basso rispetto all’area di chat
-
barra input, in basso rispetto alla barra di stato
-
barra nicklist, sulla destra
-
La barra buflist ha i seguenti elementi predefiniti:
| Elemento | Esempio | Descrizione |
|---|---|---|
buflist |
|
List of buffers. |
La barra title ha i seguenti elementi predefiniti:
| Elemento | Esempio | Descrizione |
|---|---|---|
buffer_title |
|
Buffer title. |
La barra status ha i seguenti elementi predefiniti:
| Elemento | Esempio | Descrizione |
|---|---|---|
time |
|
Ora. |
buffer_last_number |
|
Number of last buffer in list. |
buffer_plugin |
|
Plugin del buffer attivo (il plugin irc può aggiungere il nome del server irc usato dal buffer). |
buffer_number |
|
Numero del buffer corrente. |
buffer_name |
|
Nome del buffer attivo. |
buffer_modes |
|
Modalità canale IRC. |
buffer_nicklist_count |
|
Number of nicks displayed in nicklist. |
buffer_zoom |
! |
|
buffer_filter |
|
Indicatore filtraggio: |
scroll |
|
Indicatore di scorrimento, con il numero di righe sotto l’ultima riga visualizzata. |
lag |
|
Indicatore ritardo, in secondi (nascosto se il ritardo è basso). |
hotlist |
|
Elenco dei buffer con attività (messaggi non letti) (nell’esempio, 2 notifiche e 5 messaggi non letti su #abc, un messaggio non letto sul buffer #5). |
completion |
|
Elenco di parole per il completamento, con il numero di completamenti possibili per ogni parola. |
La barra input ha i seguenti elementi predefiniti:
| Elemento | Esempio | Descrizione |
|---|---|---|
input_prompt |
|
Prompt per l’input, for irc: nick and modes (mode "+i" means invisible on libera). |
away |
|
Indicatore di assenza. |
input_search |
|
Search indicator (see below). |
input_paste |
|
Chiede all’utente se incollare le righe. |
input_text |
|
Testo in input. |
There are two search modes:
-
search in lines, for example
[Search lines (~ str,msg)], with the following info:-
~: case insensitive -
==: case sensitive -
str: search string -
regex: search regular expression -
msg: search in messages -
pre: search in prefixes -
pre\|msg: search in prefixes and messages.
-
-
search in commands history, for example
[Search command (~ str,local)], with the following info:-
~: case insensitive -
==: case sensitive -
str: search string -
regex: search regular expression -
local: search in buffer local history -
global: search in global history.
-
La barra nicklist ha i seguenti elementi predefiniti:
| Elemento | Esempio | Descrizione |
|---|---|---|
buffer_nicklist |
|
List of nicks on current buffer. |
Other items available (not used in bars by default):
| Item | Example | Description |
|---|---|---|
buffer_count |
|
Total number of buffers opened. |
buffer_last_number |
|
Number of the latest buffer (can be different from |
buffer_nicklist_count_all |
|
Number of visible groups and nicks in nicklist. |
buffer_nicklist_count_groups |
|
Number of visible groups in nicklist. |
buffer_short_name |
|
Current buffer short name. |
buflist2 |
|
List of buffers, second bar item (see option buflist.look.use_items). |
buflist3 |
|
List of buffers, third bar item (see option buflist.look.use_items). |
buflist4 |
|
List of buffers, fourth bar item (see option buflist.look.use_items). |
buflist5 |
|
List of buffers, fifth bar item (see option buflist.look.use_items). |
fset |
|
Help on currently selected option on fset buffer. |
irc_channel |
|
Current IRC channel name. |
irc_host |
|
Current IRC host. |
irc_nick |
|
Current IRC nick. |
irc_nick_host |
|
Current IRC nick and host. |
irc_nick_modes |
|
IRC modes for self nick. |
irc_nick_prefix |
|
IRC nick prefix on channel. |
mouse_status |
|
Mouse status (empty if mouse is disabled). |
spell_dict |
|
Spelling dictionaries used on current buffer. |
spell_suggest |
|
Spelling suggestions for word under cursor (if misspelled). |
tls_version |
|
TLS version in use for current IRC server. |
window_number |
|
Current window number. |
La riga di comando di WeeChat (nella parte inferiore della finestra) consente di inserire i comandi o di inviare del testo sul buffer.
I comandi iniziano con il carattere "/", seguito dal nome del comando. Ad esempio, per consultare un elenco di opzioni:
/set
Il testo inviato ad un buffer è qualsiasi testo che non comincia con il carattere "/". Per esempio, per inviare il testo ciao sul buffer attivo:
ciao
Ad ogni modo, è possibile iniziare con il carattere "/", aggiungendone
poi un altro. Ad esempio, per inviare il testo /set sul buffer attivo:
//set
Per alcuni plugin come IRC, è possibile usare codici colori ed attributi, come segue (digitare kbd:[Ctrl+c] poi la lettera che segue, con il valore opzionale):
| Key | Description |
|---|---|
kbd:[Ctrl+c], kbd:[b] |
testo in grassetto. |
kbd:[Ctrl+c], kbd:[c], kbd:[xx] |
colore del testo |
kbd:[Ctrl+c], kbd:[c], kbd:[xx], kbd:[,], kbd:[yy] |
colore del testo |
kbd:[Ctrl+c], kbd:[d], kbd:[xxxxxx] |
Text color |
kbd:[Ctrl+c], kbd:[d], kbd:[xxxxxx], kbd:[,], kbd:[yyyyyy] |
Text color |
kbd:[Ctrl+c], kbd:[i] |
italic text. |
kbd:[Ctrl+c], kbd:[o] |
disabilita colori ed attributi. |
kbd:[Ctrl+c], kbd:[v] |
video inverso (inverte il colore del testo con quello di sfondo). |
kbd:[Ctrl+c], kbd:[_] |
testo sottolineato. |
|
Note
|
The same code (without number for kbd:[Ctrl+c], kbd:[c] and kbd:[Ctrl+c], kbd:[d]) can be used to stop the attribute. |
I codici colore per kbd:[Ctrl+c], kbd:[c] sono:
|
Note
|
To show all available colors in your terminal, you can do /color then
kbd:[Alt+c] in WeeChat or run this command in terminal: weechat --colors.
|
Esempio: visualizza "ciao Alice!" con "ciao" scritto in blu chiaro grassetto e "Alice" in rosso chiaro sottolineato:
^Cc12^Cbciao ^Cb^Cc04^C_Alice^C_^Cc !
Keys:
kbd:[Ctrl+c] kbd:[c] kbd:[1] kbd:[2] kbd:[Ctrl+c] kbd:[b]
kbd:[c] kbd:[i] kbd:[a] kbd:[o] kbd:[Space]
kbd:[Ctrl+c] kbd:[b] kbd:[Ctrl+c] kbd:[c] kbd:[0] kbd:[4] kbd:[Ctrl+c] kbd:[_]
kbd:[A] kbd:[l] kbd:[i] kbd:[c] kbd:[e]
kbd:[Ctrl+c] kbd:[_] kbd:[Ctrl+c] kbd:[c]
kbd:[!]
|
Note
|
Nel plugin irc, si possono riorganizzare i colori usando l’opzione irc.color.mirc_remap. |
Un buffer è composto da un numero, un nome, delle righe visualizzate (e altri dati).
Esempi di buffer:
-
buffer core (creato by WeeChat all’avvio, non può essere chiuso)
-
server irc (mostra i messaggi dal server)
-
canale irc
-
query irc
Una finestra (o window) è un’area dello schermo in cui viene visualizzato un buffer. È possibile dividere lo schermo in più finestre (examples below, see the /window command for details).
Ogni finestra visualizza un buffer. Un buffer può essere nascosto (non visualizzato da una finestra) o visualizzato da una o più finestre.
Screen layouts and the association between windows and buffers can be saved and restored.
Esempio di split orizzontale (/window splith):
▼ window #2 (buffer #4)
┌──────────────────────────────────────────────────────────────────────────────────────┐
│1.libera │Welcome to #def │
│ weechat│12:55:12 Max | hi │@Flashy│
│2. #test│12:55:20 @Flashy | hi Max! │Max │
│3. #abc │ │ │
│4. #def │ │ │
│5. #ghi │ │ │
│ │ │ │
│ │ │ │
│ │ │ │
│ │[12:55] [5] [irc/libera] 4:#def(+n){2} │
│ │[@Flashy] │
│ │────────────────────────────────────────────────────────────────────────────│
│ │Welcome to #abc │
│ │12:54:15 peter | hey! │@Flashy│
│ │12:55:01 @joe | hello │@joe │
│ │ │+weebot│
│ │ │peter │
│ │ │ │
│ │ │ │
│ │ │ │
│ │ │ │
│ │[12:55] [5] [irc/libera] 3:#abc(+n){4} │
│ │[@Flashy] hi peter!█ │
└──────────────────────────────────────────────────────────────────────────────────────┘
▲ window #1 (buffer #3)
Esempio di split verticale (/window splitv):
┌──────────────────────────────────────────────────────────────────────────────────────┐
│1.libera │Welcome to #abc │Welcome to #def │
│ weechat│12:54:15 peter | hey! │@Flashy│12:55:12 Max | hi │@Flashy│
│2. #test│12:55:01 @joe | hello │@joe │12:55:20 @Flashy | hi Max! │Max │
│3. #abc │ │+weebot│ │ │
│4. #def │ │peter │ │ │
│5. #ghi │ │ │ │ │
│ │ │ │ │ │
│ │ │ │ │ │
│ │ │ │ │ │
│ │ │ │ │ │
│ │ │ │ │ │
│ │ │ │ │ │
│ │ │ │ │ │
│ │ │ │ │ │
│ │ │ │ │ │
│ │ │ │ │ │
│ │ │ │ │ │
│ │ │ │ │ │
│ │ │ │ │ │
│ │ │ │ │ │
│ │[12:55] [5] [irc/libera] 3:#abc(+n) │[12:55] [5] [irc/libera] 4:#def(+n) │
│ │[@Flashy] hi peter!█ │[@Flashy] │
└──────────────────────────────────────────────────────────────────────────────────────┘
▲ window #1 (buffer #3) ▲ window #2 (buffer #4)
Esempio di split orizzontale + verticale:
▼ window #3 (buffer #5)
┌──────────────────────────────────────────────────────────────────────────────────────┐
│1.libera │Welcome to #abc │Welcome to #ghi │
│ weechat│12:54:15 peter | hey! │@Flashy│12:55:42 @Flashy | hi │@Flashy│
│2. #test│12:55:01 @joe | hello │@joe │12:55:56 alex | hi Flashy │alex │
│3. #abc │ │+weebot│ │ │
│4. #def │ │peter │ │ │
│5. #ghi │ │ │ │ │
│ │ │ │ │ │
│ │ │ │ │ │
│ │ │ │ │ │
│ │ │ │[12:55] [5] [irc/libera] 5:#ghi(+n) │
│ │ │ │[@Flashy] │
│ │ │ │──────────────────────────────────────│
│ │ │ │Welcome to #def │
│ │ │ │12:55:12 Max | hi │@Flashy│
│ │ │ │12:55:20 @Flashy | hi Max! │Max │
│ │ │ │ │ │
│ │ │ │ │ │
│ │ │ │ │ │
│ │ │ │ │ │
│ │ │ │ │ │
│ │[12:55] [5] [irc/libera] 3:#abc(+n) │[12:55] [5] [irc/libera] 4:#def(+n) │
│ │[@Flashy] hi peter!█ │[@Flashy] │
└──────────────────────────────────────────────────────────────────────────────────────┘
▲ window #1 (buffer #3) ▲ window #2 (buffer #4)
A special display, called "bare display" can be used for easy click on long URLs and selection of text (using the mouse).
The bare display has following features:
-
it displays only the content of current buffer: no window split neither bars (no title, nicklist, status, input, …)
-
the WeeChat mouse support is disabled (if it was enabled): you can use your mouse like you do in the terminal to click on URLs and select text
-
ncurses is not used, therefore URLs are not cut at the end of lines.
The default key to enable bare display is kbd:[Alt+l] (L), and same key to exit
(or by default anything changing the input will exit the bare display, see option
weechat.look.bare_display_exit_on_input).
The time format can be customized with the option weechat.look.bare_display_time_format.
The bare display can be enabled for a specific delay using the command /window.
If WeeChat looks like that:
┌──────────────────────────────────────────────────────────────────────────────────────┐
│1.libera │Welcome to #abc │
│ weechat│12:52:27 --> | Flashy (flashcode@weechat.org) has joined #abc │@Flashy│
│2. #test│12:52:27 -- | Nicks #abc: [@Flashy @joe +weebot peter] │@joe │
│3. #abc │12:52:27 -- | Channel #abc: 4 nicks (2 ops, 1 voice, 1 normal) │+weebot│
│4. #def │12:52:27 -- | Channel created on Tue Jan 27 06:30:17 2009 │peter │
│5. #ghi │12:54:15 peter | hey! │ │
│ │12:55:01 @joe | peter: hook_process: https://weechat.org/files/doc │ │
│ │ | /weechat/devel/weechat_plugin_api.en.html#_weechat │ │
│ │ | _hook_process │ │
│ │ │ │
│ │ │ │
│ │ │ │
│ │ │ │
│ │ │ │
│ │ │ │
│ │ │ │
│ │ │ │
│ │ │ │
│ │ │ │
│ │ │ │
│ │ │ │
│ │[12:55] [5] [irc/libera] 3:#abc(+n){4} │
│ │[@Flashy(i)] hi peter!█ │
└──────────────────────────────────────────────────────────────────────────────────────┘
The screen will look like that in bare display:
┌──────────────────────────────────────────────────────────────────────────────────────┐ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │12:52 --> Flashy (flashcode@weechat.org) has joined #abc │ │12:52 -- Nicks #abc: [@Flashy @joe +weebot peter] │ │12:52 -- Channel #abc: 4 nicks (2 ops, 1 voice, 1 normal) │ │12:52 -- Channel created on Tue Jan 27 06:30:17 2009 │ │12:54 <peter> hey! │ │12:55 <@joe> peter: hook_process: https://weechat.org/files/doc/weechat/devel/weechat_│ │plugin_api.en.html#_weechat_hook_process │ └──────────────────────────────────────────────────────────────────────────────────────┘
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).
Lines displayed in formatted buffers have following fields:
| Field | Displayed | Description |
|---|---|---|
date/time (message) |
Yes |
Date/time of message (may be past). |
date/time (print) |
No |
Date/time when WeeChat prints the message. |
prefix |
Yes |
Prefix of message, commonly a nick. |
message |
Yes |
The message itself. |
displayed |
No |
Boolean: true if line is displayed, false if line is filtered with command /filter. |
highlight |
No |
Boolean: true if line has a highlight, false otherwise. |
tags |
With |
Tags associated with the line (see lines tags). |
The display of lines can be customized with many look options (weechat.look.*) and color options (weechat.color.chat_*).
WeeChat uses tags in lines for different purposes:
-
highlight
-
notify level
-
logging
-
use of command /filter
Tags can be displayed with the command /debug tags (same command to hide them).
Tag usati di frequente (elenco non esaustivo):
| Tag | Descrizione |
|---|---|
|
La riga non può essere filtrata. |
|
Evidenziazione non possibile sulla riga. |
|
La riga non viene scritta nel file di log. |
|
Livello di log per la riga (consultare |
|
The line must not be added to hotlist. (1) |
|
The line is a user message. (1) |
|
The line is a private message. (1) |
|
The line is a message with highlight. (1) |
|
Self message. |
|
Il messaggio viene dal nick "xxx". |
|
Il prefisso è un nick con il colore "ccc". |
|
Username and host in message. |
|
Messaggio IRC "xxx" (può essere un comando o un numero di 3 cifre). |
|
Messaggio IRC numerico. |
|
Errore dal server IRC. |
|
Azione da un nic (comando |
|
Messaggio CTCP. |
|
Risposta ad un messaggio CTCP. |
|
Messaggio IRC filtrabile tramite lo "smart filter" (filtro intelligente). |
|
Messagio con informazioni sull’assenza. |
|
Note
|
(1) When no tag "notify_xxx" is present, the default level is "low". If a tag "notify_xxx" is present, the real notify level can be different, for example if a max hotlist level is used for a nick, the notify level can be lower than the value in the tag. |
Local variables can be defined in all buffers.
A local variable has:
-
a name (string)
-
a value (string, can be empty).
Local variables can be set by WeeChat, plugins, scripts, or manually on the command line in the buffer.
For example to add the local variable "completion_default_template":
/buffer setvar completion_default_template %(my_completion)
To list local variables in the current buffer:
/buffer listvar
To remove the local variable "completion_default_template":
/buffer delvar completion_default_template
By default WeeChat and its default plugins interpret these variables:
| Name | Value | Description |
|---|---|---|
|
any string |
Away message on the server, set by irc plugin. |
|
any string |
Channel name, set by irc/xfer plugins and debug buffer of relay/trigger plugins. |
|
any string |
Charset modifier for the server buffer, set by irc plugin. |
|
any string |
Default completion template for the buffer, overriding the option
|
|
any string |
Filter defined on some buffers like |
|
any string |
Self host (if known), set by irc plugin. |
|
any string |
Lag on the server, set by irc plugin. |
|
any string |
Buffer name (be careful, this is not the full name and this name is not enough to identify or search a buffer). |
|
any string |
Self nick, set by irc and xfer plugins. |
|
|
If set, the logger plugin does not log anything for the buffer. |
|
any string |
Name of plugin which created the buffer ( |
|
any string |
Close callback defined by a script for a buffer. |
|
any string |
Data for close callback defined by a script for a buffer. |
|
any string |
Input callback defined by a script for a buffer. |
|
any string |
Data for input callback defined by a script for a buffer. |
|
any string |
Name of the script which created the buffer. |
|
any string |
Server name, set by irc plugin and debug buffer of relay/trigger plugins. |
|
any string |
Misspelled word and suggestions (format: "misspelled:suggestions"), set by spell plugin. |
|
any string |
Trigger filter, set by trigger plugin. |
|
any string, for example:
|
Type of buffer, set by WeeChat and many plugins. |
|
Note
|
External plugins and scripts can define and use other local variables. |
Buflist plugin displays a list of buffers in a bar item called "buflist"
(four other bar items "buflist2", "buflist3", "buflist4" and "buflist5" are
available as well).
A default bar "buflist" is created on startup with this item.
Sections in file buflist.conf:
| Section | Control command | Description |
|---|---|---|
|
|
Formats used to display list of buffers. |
|
|
Look and feel. |
Options:
The cursor mode allows you to move freely the cursor anywhere on screen, in chat
area and bars, and lets you perform actions at the given position.
You can enter in cursor mode either with the command /cursor or with a mouse
middle click (mouse must have been enabled with key kbd:[Alt+m] or command
/mouse enable).
Typical use is to quote messages (chat area) or interact with nicks (nicklist bar).
See command /cursor and key bindings in cursor context for the list of actions you can perform in this mode.
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 /key command.
| Tasti | Descrizione | Comando |
|---|---|---|
kbd:[←] |
Passa al carattere precedente nella riga di comando. |
|
kbd:[→] |
Passa al carattere successivo nella riga di comando. |
|
kbd:[Shift+↑] |
Go to previous line. |
|
kbd:[Shift+↓] |
Go to next line. |
|
kbd:[Ctrl+←] |
Passa alla parola precedente nella riga di comando. |
|
kbd:[Ctrl+→] |
Passa alla parola successiva nella riga di comando. |
|
kbd:[Home] |
Go to the beginning of current line. |
|
kbd:[Shift+Home] |
Go to the beginning of command line. |
|
kbd:[End] |
Go to the end of current line. |
|
kbd:[Shift+End] |
Go to the end of command line. |
|
| Tasti | Descrizione | Comando |
|---|---|---|
kbd:[Del] |
Elimina il carattere successivo nella riga di comando. |
|
kbd:[Backspace] |
Elimina il carattere precedente nella riga di comando. |
|
kbd:[Ctrl+k] |
Delete from cursor until end of current line (deleted string is copied to the internal clipboard). |
|
kbd:[Alt+Ctrl+k] |
Delete from cursor until end of command line (deleted string is copied to the internal clipboard). |
|
kbd:[Ctrl+t] |
Inverti caratteri. |
|
kbd:[Ctrl+u] |
Delete from cursor until beginning of current line (deleted string is copied to the internal clipboard). |
|
kbd:[Alt+Ctrl+u] |
Delete from cursor until beginning of command line (deleted string is copied to the internal clipboard). |
|
kbd:[Alt+Backspace] |
Elimina la parola precedente nella riga di comando (deleted string is copied to the internal clipboard). |
|
kbd:[Ctrl+w] |
Delete previous word of command line until whitespace (deleted string is copied to the internal clipboard). |
|
kbd:[Ctrl+y] |
Paste the internal clipboard content. |
|
kbd:[Ctrl+_] |
Annulla l’ultima azione sulla riga di comando. |
|
kbd:[Alt+_] |
Ripete l’ultima azione sulla riga di comando. |
|
kbd:[Tab] |
Completa comando o nick (kbd:[Tab] di nuovo: trova prossimo completamento). |
|
kbd:[Shift+Tab] |
Senza completamento: effettua un completamento parziale, con completamento in sospeso: completa con il completamento precedente. |
|
kbd:[Invio] |
Esegue comando o invia messaggio (in modalità ricerca: ferma ricerca). |
|
kbd:[Alt+Enter] |
Insert a newline. |
|
kbd:[Alt+d] |
Elimina la parola successiva nella riga di comando (deleted string is copied to the internal clipboard). |
|
kbd:[Alt+k] |
Cattura un tasto ed inserisce il suo codice (e il comando associato se il tasto esiste) nella riga di comando. |
|
kbd:[Alt+r] |
Delete current line. |
|
kbd:[Alt+R] |
Delete entire command line. |
|
| Tasti | Descrizione | Comando |
|---|---|---|
kbd:[Ctrl+c], kbd:[b] |
Inserisce il codice per il testo in grassetto. |
|
kbd:[Ctrl+c], kbd:[c] |
Inserisce il codice per il testo colorato. |
|
kbd:[Ctrl+c], kbd:[d] |
Insert code for colored text (RGB color, as hexadecimal). |
|
kbd:[Ctrl+c], kbd:[i] |
Inserisce il codice per il testo in corsivo. |
|
kbd:[Ctrl+c], kbd:[o] |
Inserisce il codice per il reset dei colori. |
|
kbd:[Ctrl+c], kbd:[v] |
Inserisce il codice per l’inversione dei colori. |
|
kbd:[Ctrl+c], kbd:[_] |
Inserisce il codice per il testo sottolineato. |
|
| Tasti | Descrizione | Comando |
|---|---|---|
kbd:[↑] |
Chiama comando/messaggio precedente (in modalità ricerca: cerca in alto). |
|
kbd:[↓] |
Chiama comando/messaggio precedente (in modalità ricerca: cerca in basso). |
|
kbd:[Ctrl+↑] |
Chiama il comando/messaggio precedente nella cronologia globale (identico per tutti i buffer). |
|
kbd:[Ctrl+↓] |
Chiama il comando/messaggio successivo nella cronologia globale (identico per tutti i buffer). |
|
| Tasti | Descrizione | Comando |
|---|---|---|
kbd:[Ctrl+r] |
Search for text in commands history (see keys for context "histsearch"). |
|
kbd:[Ctrl+s] |
Search for text in buffer lines (see keys for context "search"). |
|
kbd:[Ctrl+x] |
Switch current buffer if buffers are merged with same number, for example switch to another IRC server buffer. |
|
kbd:[Alt+x] |
Zoom on merged buffer (kbd:[Alt+x] again: display all merged buffers). |
|
kbd:[PgUp] |
Scorre in alto di una pagina nella cronologia del buffer. |
|
kbd:[PgDn] |
Scorre di una pagina in basso nella cronologia del buffer. |
|
kbd:[Alt+PgUp] |
Scorre di qualche riga in alto nella cronologia del buffer. |
|
kbd:[Alt+PgDn] |
Scorre di qualche riga in basso nella cronologia del buffer. |
|
kbd:[Alt+Home] |
Scorre in cima al buffer. |
|
kbd:[Alt+End] |
Scorre alla fine del del buffer. |
|
kbd:[Alt+←] |
Passa al buffer precedente. |
|
kbd:[Alt+→] |
Passa al buffer successivo. |
|
kbd:[Alt+j], kbd:[Alt+f] |
Switch to first buffer. |
|
kbd:[Alt+j], kbd:[Alt+l] ( |
Passa all’ultimo buffer. |
|
kbd:[Alt+j], kbd:[Alt+r] |
Passa al buffer raw IRC. |
|
kbd:[Alt+j], kbd:[Alt+s] |
Passa al buffer server IRC. |
|
kbd:[Alt+0…9] |
Passa al buffer numero (0 = 10). |
|
kbd:[Alt+j], kbd:[01…99] |
Passa al buffer numero. |
|
kbd:[Alt+n] |
Scorre fino alla notifica successiva. |
|
kbd:[Alt+p] |
Scorre fino alla notifica precedente. |
|
kbd:[Alt+u] |
Scorre fino alla prima riga non letta nel buffer. |
|
kbd:[Alt+Shift+U] |
Imposta l’evidenziatore dei messaggi non letti su tutti i buffer. |
|
kbd:[Alt+<] |
Passa al buffer precedente nella lista dei buffer visitati. |
|
kbd:[Alt+>] |
Passa al buffer successivo nella lista dei buffer visitati. |
|
kbd:[Alt+/] |
Passa all’ultimo buffer mostrato (prima dell’ultimo passaggio ad un buffer). |
|
| Tasti | Descrizione | Comando |
|---|---|---|
kbd:[Ctrl+l] ( |
Ridisegna l’intera finestra. |
|
kbd:[Alt+l] ( |
Toggle bare display. |
|
kbd:[F7] |
Passa alla finestra precedente. |
|
kbd:[F8] |
Passa alla finestra successiva. |
|
kbd:[Alt+w], kbd:[Alt+↑] |
Passa alla finestra in alto. |
|
kbd:[Alt+w], kbd:[Alt+↓] |
Passa alla finestra in basso. |
|
kbd:[Alt+w], kbd:[Alt+←] |
Passa alla finestra sulla sinistra. |
|
kbd:[Alt+w], kbd:[Alt+→] |
Passa alla finestrs sulla destra. |
|
kbd:[Alt+w], kbd:[Alt+b] |
Bilancia le dimensioni di tutte le finestre. |
|
kbd:[Alt+w], kbd:[Alt+s] |
Scambia i buffer di due finestra. |
|
kbd:[Alt+z] |
Ingrandimento sulla finestra attiva (kbd:[Alt+z] di nuovo: ripristina lo stato iniziale della finestra, prima dell’ingrandimento). |
|
| Tasti | Descrizione | Comando |
|---|---|---|
kbd:[F1] |
Scroll up one page in buflist. |
|
kbd:[F2] |
Scroll down one page in buflist. |
|
kbd:[Alt+F1] |
Go to the beginning of buflist. |
|
kbd:[Alt+F2] |
Go to the end of buflist. |
|
kbd:[F9] |
Scorre il titolo del buffer sulla sinistra. |
|
kbd:[F10] |
Scorre il titolo del buffer sulla destra. |
|
kbd:[F11] |
Scorre di una pagina in alto nella lista nick. |
|
kbd:[F12] |
Scorre di una pagina in basso nella lista nick. |
|
kbd:[Alt+F11] |
Sposta all’inizio della lista nick. |
|
kbd:[Alt+F12] |
Sposta alla fine della lista nick. |
|
kbd:[Alt+Shift+B] |
Toggle buflist. |
|
kbd:[Alt+Shift+N] |
Toggle nicklist bar. |
|
| Tasti | Descrizione | Comando |
|---|---|---|
kbd:[Alt+a] |
Passa al buffer successivo con attività (con priorità: highligh, messagge, altro). |
|
kbd:[Alt+h], kbd:[Alt+c] |
Clear hotlist (activity notification on buffers). |
|
kbd:[Alt+h], kbd:[Alt+m] |
Remove current buffer from hotlist. |
|
kbd:[Alt+h], kbd:[Alt+r] |
Restore latest hotlist removed in the current buffer. |
|
kbd:[Alt+h], kbd:[Alt+Shift+R] |
Restore latest hotlist removed in all buffers. |
|
| Tasti | Descrizione | Comando |
|---|---|---|
kbd:[Alt+m] |
Abilita/disabilita. |
|
kbd:[Alt+s] |
Toggle spell checker. |
|
kbd:[Alt+=] |
Attiva/disattiva filtri. |
|
kbd:[Alt+-] |
Toggle filters in current buffer. |
|
These keys are used in context "search" (when kbd:[Ctrl+s] is pressed to search text in buffer lines).
| Tasti | Descrizione | Comando |
|---|---|---|
kbd:[Ctrl+x] |
Switch search type: string (default), regular expression. |
|
kbd:[Alt+c] |
Passa alla ricerca esatta. |
|
kbd:[Tab] |
Switch search in: messages (default), prefixes, prefixes + messages. |
|
kbd:[Ctrl+r] |
Cerca riga precedente. |
|
kbd:[Ctrl+s] |
Cerca riga successiva. |
|
kbd:[Enter] |
Stop search at current position. |
|
kbd:[Ctrl+q] |
Stop search and reset scroll to pre-text search state. |
|
These keys are used in context "histsearch" (when kbd:[Ctrl+r] is pressed to search text in commands history).
| Tasti | Descrizione | Comando |
|---|---|---|
kbd:[Ctrl+x] |
Switch search type: string (default), regular expression. |
|
kbd:[Alt+c] |
Switch exact case for search. |
|
kbd:[Tab] |
Switch search in: buffer local history (default), global history. |
|
kbd:[Ctrl+r] |
Search in previous (older) history entries. |
|
kbd:[Ctrl+s] |
Search in next (newer) history entries. |
|
kbd:[Enter] |
Stop search and use matching input. |
|
kbd:[Ctrl+o] |
Execute the command found in history and insert the next one in the command line. |
|
kbd:[Ctrl+q] |
Stop search and restore input to its initial value. |
|
Questi tasti sono usati nel contesto "cursor" (movimento libero del cursore sullo schermo, see Cursor mode.
| Tasto | Zona | Descrizione | Comando |
|---|---|---|---|
kbd:[↑] |
- |
Sposta il cursore di una riga in alto. |
|
kbd:[↓] |
- |
Sposta il cursore di una riga in basso. |
|
kbd:[←] |
- |
Sposta il cursore di una colonna a sinistra. |
|
kbd:[→] |
- |
Sposta il cursore di una colonna a destra. |
|
kbd:[Alt+↑] |
- |
Move cursor to the first line of the area. |
|
kbd:[Alt+↓] |
- |
Move cursor to the last line of the area. |
|
kbd:[Alt+←] |
- |
Move cursor to the first column of the area. |
|
kbd:[Alt+→] |
- |
Move cursor to the last column of the area. |
|
kbd:[Alt+Home] |
- |
Move cursor to the top left corner of the area. |
|
kbd:[Alt+End] |
- |
Move cursor to the bottom right corner of the area. |
|
kbd:[Alt+Shift+↑] |
- |
Sposta il cursore nell’area in alto. |
|
kbd:[Alt+Shift+↓] |
- |
Sposta il cursore nell’area in basso. |
|
kbd:[Alt+Shift+←] |
- |
Sposta il cursore nell’area a sinistra. |
|
kbd:[Alt+Shift+→] |
- |
Sposta il cursore nell’area a destra. |
|
kbd:[m] |
chat |
Cita messaggio. |
|
kbd:[l] |
chat |
Quote focused line. |
|
kbd:[q] |
chat |
Cita prefisso + messaggio. |
|
kbd:[Q] |
chat |
Cita ora + prefisso + messaggio. |
|
kbd:[b] |
lista nick |
Ban di un nick. |
|
kbd:[k] |
lista nick |
Kick di un nick. |
|
kbd:[K] |
lista nick |
Kick e ban di un nick. |
|
kbd:[q] |
lista nick |
Apri query con il nick. |
|
kbd:[w] |
lista nick |
Effettua un whois sul nick. |
|
kbd:[Enter] |
- |
Ferma la modalità cursore. |
|
These mouse actions are possible only if mouse is enabled with key kbd:[Alt+m]
(command: /mouse toggle).
| Tasto/Wheel (1) | Azione | Zona | Descrizione | Comando |
|---|---|---|---|---|
kbd:[■ □ □] |
- |
chat |
Passa alla finestra. |
|
kbd:[■ □ □] |
sinistra |
chat |
Passa al buffer precedente. |
|
kbd:[■ □ □] |
destra |
chat |
Passa al buffer successivo. |
|
kbd:[■ □ □] |
sinistra (lungo) |
chat |
Switch to first buffer. |
|
kbd:[■ □ □] |
destra (lungo) |
chat |
Passa all’ultimo buffer. |
|
kbd:[▲] |
- |
chat |
Scorre di qualche riga in alto nella cronologia del buffer. |
|
kbd:[▼] |
- |
chat |
Scorre di qualche riga in basso nella cronologia del buffer. |
|
kbd:[Ctrl+▲] |
- |
chat |
Scroll horizontally to the left. |
|
kbd:[Ctrl+▼] |
- |
chat |
Scroll horizontally to the right. |
|
kbd:[▲] |
- |
chat: fset buffer |
Move five lines up in fset buffer. |
|
kbd:[▼] |
- |
chat: fset buffer |
Move five lines down in fset buffer. |
|
kbd:[■ □ □] |
- |
chat: fset buffer |
Select line in fset buffer. |
|
kbd:[□ □ ■] |
- |
chat: fset buffer |
Toggle boolean (on/off) or edit the option value. |
|
kbd:[□ □ ■] |
left |
chat: fset buffer |
Decrease value for integer/color/enum, set/append to value for other types. |
|
kbd:[□ □ ■] |
right |
chat: fset buffer |
Increase value for integer/color/enum, set/append to value for other types. |
|
kbd:[□ □ ■] |
up / down |
chat: fset buffer |
Mark/unmark multiple options. |
|
kbd:[▲] |
- |
chat: /list buffer |
Move five lines up in /list buffer. |
|
kbd:[▼] |
- |
chat: /list buffer |
Move five lines down in /list buffer. |
|
kbd:[■ □ □] |
- |
chat: /list buffer |
Select line in /list buffer. |
|
kbd:[□ □ ■] |
- |
chat: /list buffer |
Join IRC channel on selected line. |
|
kbd:[▲] |
- |
chat: script buffer |
Move 5 lines up in script buffer. |
|
kbd:[▼] |
- |
chat: script buffer |
Move 5 lines down in script buffer. |
|
kbd:[■ □ □] |
- |
chat: script buffer |
Select line in script buffer. |
|
kbd:[□ □ ■] |
- |
chat: script buffer |
Install/remove script. |
|
kbd:[■ □ □] |
up / left |
buflist |
Move buffer to a lower number. |
Signal |
kbd:[■ □ □] |
down / right |
buflist |
Move buffer to a higher number. |
Signal |
kbd:[■ □ □] |
- |
buflist |
Switch to buffer (previously visited buffer if the buffer is the current one). |
Signal |
kbd:[□ □ ■] |
- |
buflist |
Switch to next visited buffer if the buffer is the current one. |
Signal |
kbd:[Ctrl+▲] |
- |
buflist |
Switch to previous buffer. |
Signal |
kbd:[Ctrl+▼] |
- |
buflist |
Switch to next buffer. |
Signal |
kbd:[■ □ □] |
su |
lista nick |
Scorre di una pagina in alto nella lista nick. |
|
kbd:[■ □ □] |
giù |
lista nick |
Scorre di una pagina in basso nella lista nick. |
|
kbd:[■ □ □] |
up (lungo) |
lista nick |
Sposta all’inizio della lista nick. |
|
kbd:[■ □ □] |
giù (lungo) |
lista nick |
Sposta alla fine della lista nick. |
|
kbd:[■ □ □] |
- |
lista nick |
Apre una query con un nick. |
|
kbd:[□ □ ■] |
- |
lista nick |
Effettua un whois su un nick. |
|
kbd:[■ □ □] |
sinistra |
lista nick |
Kick di un nick. |
|
kbd:[■ □ □] |
sinistra (lungo) |
lista nick |
Kick e ban di un nick. |
|
kbd:[□ □ ■] |
sinistra |
lista nick |
Ban di un nick. |
|
kbd:[□ □ ■] |
- |
input |
Cattura un evento del mouse e inserisce il codice nella riga di comando. |
|
kbd:[▲] |
- |
ogni barra |
Scorre la barra del -20%. |
|
kbd:[▼] |
- |
ogni barra |
Scorre la barra del +20%. |
|
kbd:[□ ■ □] |
- |
ovunque |
Avvia la modalità cursore in questo punto. |
|
|
Note
|
(1) Buttons: kbd:[◼ □ □]: click on left button kbd:[□ ◼ □]: click on middle button kbd:[□ □ ◼]: click on right button Wheel: kbd:[▲]: wheel up kbd:[▼]: wheel down |
These keys and actions are used on the fset buffer (see Fset plugin).
| Key | Action (1) | Description | Command |
|---|---|---|---|
kbd:[↑] |
Move one line up. |
|
|
kbd:[↓] |
Move one line down. |
|
|
kbd:[PgUp] |
Move one page up. |
|
|
kbd:[PgDn] |
Move one page down. |
|
|
kbd:[Alt+Home] |
|
Move to first line. |
|
kbd:[Alt+End] |
|
Move to last line. |
|
kbd:[F11] |
|
Scroll horizontally on the left. |
|
kbd:[F12] |
|
Scroll horizontally on the right. |
|
kbd:[Alt+Space] |
|
Toggle boolean value. |
|
kbd:[Alt+-] |
|
Subtract 1 from value for integer/color/enum, set value for other types. |
|
kbd:[Alt++] |
|
Add 1 to value for integer/color/enum, append to value for other types. |
|
kbd:[Alt+f], kbd:[Alt+r] |
|
Reset value. |
|
kbd:[Alt+f], kbd:[Alt+u] |
|
Unset value. |
|
kbd:[Alt+Enter] |
|
Set value. |
|
kbd:[Alt+f], kbd:[Alt+n] |
|
Set new value. |
|
kbd:[Alt+f], kbd:[Alt+a] |
|
Append to value. |
|
kbd:[Alt+,] |
|
Mark/unmark option. |
|
kbd:[Shift+↑] |
Move one line up and mark/unmark option. |
|
|
kbd:[Shift+↓] |
Mark/unmark option and move one line down. |
|
|
|
Mark options displayed that are matching filter "xxx" (any filter on option or value is allowed, see /fset command). |
||
|
Unmark options displayed that are matching filter "xxx" (any filter on option or value is allowed, see /fset command). |
||
kbd:[Ctrl+l] ( |
Refresh options and whole screen. |
|
|
|
Refresh options (keep marked options). |
||
|
Refresh options (unmark all options). |
||
kbd:[Alt+p] |
|
Toggle plugin description options ( |
|
kbd:[Alt+v] |
|
Toggle help bar. |
|
|
Sort options by fields x,y (see option fset.look.sort). |
|
|
|
Reset sort to its default value (see option fset.look.sort). |
|
|
|
Export options in file "xxx". |
|
|
|
Export options in file "xxx" without help. |
|
|
|
Export options in file "xxx" with help. |
|
|
kbd:[Ctrl+x] |
|
Switch the format used to display options. |
|
|
Close fset buffer. |
|
|
Note
|
(1) The action must be entered as input on the command line, followed by kbd:[Enter]. |
These keys and actions are used on the IRC /list buffer (see command /list).
| Key | Action (1) | Description | Command |
|---|---|---|---|
kbd:[↑] |
Move one line up. |
|
|
kbd:[↓] |
Move one line down. |
|
|
kbd:[PgUp] |
Move one page up. |
|
|
kbd:[PgDn] |
Move one page down. |
|
|
kbd:[Alt+Home] |
|
Move to first line. |
|
kbd:[Alt+End] |
|
Move to last line. |
|
kbd:[F11] |
|
Scroll horizontally on the left. |
|
kbd:[F12] |
|
Scroll horizontally on the right. |
|
kbd:[Ctrl+j] |
|
Join IRC channel on selected line. |
|
|
Show only channels with "xxx" in name or topic (case insensitive). |
||
|
Show only channels with "xxx" in name (case insensitive). |
||
|
Show only channels with "xxx" in topic (case insensitive). |
||
|
Show only channels with at least "n" users. |
||
|
Show only channels with more than "n" users. |
||
|
Show only channels with less than "n" users. |
||
|
Show only channels matching the evaluated condition "xxx", using following variables: name, name2, users, topic. |
||
|
Sort channels by fields x,y (see command /list). |
||
|
Reset sort to its default value (see command /list). |
||
|
Refresh list (run again command /list). |
||
|
Close buffer. |
|
|
Note
|
(1) The action must be entered as input on the command line, followed by kbd:[Enter]. |
These keys and actions are used on the script buffer (see script manager).
| Key | Action (1) | Description | Command |
|---|---|---|---|
kbd:[↑] |
Move one line up. |
|
|
kbd:[↓] |
Move one line down. |
|
|
kbd:[PgUp] |
Move one page up. |
|
|
kbd:[PgDn] |
Move one page down. |
|
|
kbd:[Alt+i] |
|
Install script. |
|
kbd:[Alt+r] |
|
Remove script. |
|
kbd:[Alt+l] |
|
Load script. |
|
kbd:[Alt+L] |
|
Reload script. |
|
kbd:[Alt+u] |
|
Unload script. |
|
kbd:[Alt+Shift+A] |
|
Autoload script. |
|
kbd:[Alt+h] |
|
Hold/unhold script. |
|
kbd:[Alt+v] |
|
View script. |
|
|
Sort scripts by fields x,y (see option script.look.sort). |
||
|
Reset sort to its default value (see option script.look.sort). |
||
|
Refresh list. |
||
|
Close buffer. |
|
|
Note
|
(1) The action must be entered as input on the command line, followed by kbd:[Enter]. |
Fast Set plugin displays a list of options in a buffer, and helps to set WeeChat and plugin options.
Example of fset buffer displaying options starting with weechat.look :
┌──────────────────────────────────────────────────────────────────────────────────────┐ │1.weechat│1/121 | Filter: weechat.look.* | Sort: ~name | Key(input): alt+space=toggle │ │2.fset │weechat.look.bare_display_exit_on_input: exit the bare display mode on any c│ │ │hanges in input [default: on] │ │ │----------------------------------------------------------------------------│ │ │ weechat.look.align_end_of_lines enum message │ │ │ weechat.look.align_multiline_words boolean on │ │ │ weechat.look.bar_more_down string "++" │ │ │ weechat.look.bar_more_left string "<<" │ │ │ weechat.look.bar_more_right string ">>" │ │ │ weechat.look.bar_more_up string "--" │ │ │ weechat.look.bare_display_exit_on_input boolean on │ │ │ weechat.look.bare_display_time_format string "%H:%M" │ │ │ weechat.look.buffer_auto_renumber boolean on │ │ │ weechat.look.buffer_notify_default enum all │ │ │ weechat.look.buffer_position enum end │ │ │ weechat.look.buffer_search_case_sensitive boolean off │ │ │ weechat.look.buffer_search_force_default boolean off │ │ │ weechat.look.buffer_search_regex boolean off │ │ │ weechat.look.buffer_search_where enum prefix_message │ │ │ weechat.look.buffer_time_format string "%H:%M:%S" │ │ │ weechat.look.buffer_time_same string "" │ │ │[12:55] [2] [fset] 2:fset │ │ │█ │ └──────────────────────────────────────────────────────────────────────────────────────┘
Sections in file fset.conf:
| Section | Control command | Description |
|---|---|---|
|
|
Colors. |
|
|
Formats used to display list of options. |
|
|
Look and feel. |
Options:
I colori base in WeeChat sono:
| Nome | Colore |
|---|---|
|
Colore predefinito del terminale (trasparente per lo sfondo) |
|
Nero |
|
Grigio scuro |
|
Rosso scuro |
|
Rosso chiaro |
|
Verde scuro |
|
Verde chiaro |
|
Marrone |
|
Giallo |
|
Blu scuro |
|
Blu chiaro |
|
Rosa scuro |
|
Rosa chiaro |
|
Azzurro scuro |
|
Azzurro chiaro |
|
Grigio |
|
Bianco |
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
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
Esistono alcuni attributi per i colori. Uno o più attributi vanno aggiunti prima del nome o del numero del colore:
-
%: blink -
.: "dim" (half bright) -
*: testo in grassetto -
!: video inverso -
/: testo in corsivo -
_: testo sottolineato -
|: keep attributes: do not reset blink/dim/bold/reverse/italic/underlined when changing color
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
Il plugin Charset consente di decodificare o codificare dati utilizzando i set caratteri.
Esiste un set caratteri predefinito per la codifica/decodifica, e set caratteri specifici per i buffer (o gruppi di buffer).
Questo plugin è opzionale, ma raccomandato: se non caricato, WeeChat può leggere/scrivere soltanto dati UTF-8.
Il plugin Charset dovrebbe essere caricato automaticamente da WeeChat. Per essere sicuri che sia caricato, provare con:
/charset
Se non trovato, allora si deve caricare il plugin con il comando:
/plugin load charset
Se il plugin non viene trovato, allora è necessario ricompilare WeeChat con il supporto ai plugin e a Charset.
Quando viene avviato il plugin Charset, mostra i set caratteri del terminale e quello interno. Il set caratteri dipende dal proprio locale, mentre quello interno è UTF-8.
Per esempio:
set caratteri: terminale: ISO-8859-15, interno: UTF-8
Per impostare il set caratteri globale per la codifica e la decodifica,
utilizzare il comando /set.
Per esempio:
/set charset.default.decode ISO-8859-15 /set charset.default.encode ISO-8859-15
Se il set caratteri globale per la decodifica non è impostato (ad esempio durante il primo caricamento del plugin Charset), verrà impostato automaticamente sul set caratteri del terminale (se diverso da UTF-8), oppure su ISO-8859-1.
Il valore di codifica predefinito è vuoto, perciò il testo viene inviato per default con il set caratteri interno (UTF-8).
Per impostare il set caratteri del server IRC, utilizzare il comando charset
sul buffer del server. Se viene immesso solo il set caratteri, allora i valori
di codifica e decodifica saranno gli stessi.
Ad esempio:
/charset ISO-8859-15
È l’equivalente di:
/charset decode ISO-8859-15 /charset encode ISO-8859-15
Per impostare il set caratteri per il canale IRC (o il privato), utilizzare gli stessi comandi per il server, ma sul buffer del canale (o quello privato).
To set charset for all channels/privates of an IRC server:
/set charset.encode.irc.libera ISO-8859-15
Per visualizzare tutti i set caratteri utilizzati, utilizzare il comando seguente:
/set charset.*
Per qualunque problema con i set caratteri, per favore consultare le Domande Frequenti di WeeChat / Charset ↗.
Sections in file charset.conf:
| Section | Control command | Description |
|---|---|---|
|
|
Default decoding/encoding charset. |
|
|
Decoding charset by buffer (options can be added/removed in section). |
|
|
Encoding charset by buffer (options can be added/removed in section). |
Options:
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 weechat.look.buffer_notify_default, il valore predefinito è all.
| Livello di notifica | Livello del messaggio aggiunto alla hotlist |
|---|---|
|
(nessuno) |
|
highlight + private |
|
highlight + private + message |
|
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
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 setauto hotlist_max_level_nicks_add joe:2,mike:2
You can disable highlights with option
weechat.look.highlight_disable_regex
(regular expression).
When a highlight is disabled with this option, the other highlight options are
ignored.
For example to disable any highlight on messages with a word beginning with "flash" between chevrons:
/set weechat.look.highlight_disable_regex "<flash.*>"
This can also be set with the buffer property "highlight_disable_regex".
Same example, specific to the current buffer:
/buffer setauto highlight_disable_regex <flash.*>
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 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 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 weechat.look.word_chars_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
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*"
Il plugin Logger consente di salvare il contenuto dei buffer su file, con opzioni a proposito su cosa e come viene salvato.
Il logging viene effettuato con un livello per ogni buffer. Il livello predefinito è il 9 (registra tutti i messaggi visualizzati sul buffer). È possibile cambiare il livello per un buffer, oppure per un gruppo di buffer.
I livelli possibili sono da 0 a 9. Zero vuol dire "non registrare nulla" mentre 9 "registra tutto".
I plugin utilizzano livelli diversi per i messaggi visualizzati. Il plugin IRC usa i seguenti livelli:
-
livello 1: messaggio da un utente (su canale o privato)
-
livello 2: cambio nick (proprio o di qualcun altro)
-
livello 3: ogni messaggio del server (esclui entrata/uscita/disconnessione)
-
livello 4: messaggio del server entrata/uscita/disconnessione
Se viene impostato il livello 3 per un canale IRC, WeeChat registrerà tutti i messaggi, ma non quelli di entrata/uscita/disconnessione.
Alcuni esempi:
-
imposta il livello 3 per il canale IRC #weechat:
/set logger.level.irc.libera.#weechat 3
-
set level 3 for libera server buffer:
/set logger.level.irc.server.libera 3
-
imposta il livello 3 per tutti i canali sul server libera:
/set logger.level.irc.libera 3
-
imposta il livello 2 per tutti i buffer IRC:
/set logger.level.irc 2
È possibile definire un mask per il nome del file di ogni buffer, ed utilizzare le variabili buffer locali per costruire il nome del file. To see available local variables for current buffer:
/buffer listvar
Masks will be matched on options in descending order of specificity on
logger.mask.$plugin.*, with logger.file.mask as fallback option.
Ad esempio, sul buffer "irc.libera.#weechat", WeeChat cercherà un mask con il nome dell’opzione, in quest’ordine:
logger.mask.irc.libera.#weechat logger.mask.irc.libera logger.mask.irc logger.file.mask
Ciò vuol dire che si hanno dei mask specifici per alcuni server IRC ("logger.mask.irc.libera") o per un plugin ("logger.mask.irc").
Per avere file di log per data, è possibile usare specificatori data/ora
nei mask (consultare man stfrtime per i formati), ad esempio:
/set logger.file.mask "%Y/%m/$plugin.$name.weechatlog"
Si avranno i seguenti file:
~/.local/share/weechat
└── logs
├── 2010
│ ├── 11
│ │ ├── irc.server.libera.weechatlog
│ │ └── irc.libera.#weechat.weechatlog
│ └── 12
│ ├── irc.server.libera.weechatlog
│ └── irc.libera.#weechat.weechatlog
├── 2011
│ ├── 01
│ │ ├── irc.server.libera.weechatlog
│ │ └── irc.libera.#weechat.weechatlog
│ ├── 02
...
Se si desidera avere una directory per il server IRC ed una per il canale al suo interno:
/set logger.mask.irc "irc/$server/$channel.weechatlog"
Si avranno i seguenti file:
~/.local/share/weechat
└── logs
└── irc
├── libera
│ ├── libera.weechatlog
│ ├── #weechat.weechatlog
│ └── #mychan.weechatlog
├── oftc
│ ├── oftc.weechatlog
│ ├── #channel1.weechatlog
│ └── #channel2.weechatlog
...
It is possible to define a max size for log files, and when it is reached, there is automatic rotation of log file.
The rotated log files can be compressed with gzip or zstd ↗.
|
Note
|
As the compression of a file can take some time, it is performed in background. |
Example with a max size of 2GB and compression with gzip, using good compression level (slower than default one):
/set logger.file.rotation_compression_type gzip /set logger.file.rotation_compression_level 80 /set logger.file.rotation_size_max "2g"
If you want to use a decimal number, you can use the unit below and multiply by 1000, for example to set max size to 2.5GB:
/set logger.file.rotation_size_max "2500m"
With these settings, you’ll end with files like these ones (in this example there is rotation only for the log of #weechat channel):
~/.local/share/weechat
└── logs
├── core.weechat.weechatlog
├── irc.server.libera.weechatlog
├── irc.libera.#weechat.weechatlog
├── irc.libera.#weechat.weechatlog.1.gz
├── irc.libera.#weechat.weechatlog.2.gz
└── irc.libera.#weechat.weechatlog.3.gz
Sections in file logger.conf:
| Section | Control command | Description |
|---|---|---|
|
|
Look and feel. |
|
|
Colors. |
|
|
Options for log files. |
|
|
Log level by buffer (options can be added/removed in section). |
|
|
Filename mask by buffer (options can be added/removed in section). |
Options:
WeeChat supporta i click e le azioni del mouse. Funziona con il terminale locale, e da remoto via connessione ssh con o senza screen/tmux.
Per abilitare il mouse all’avvio:
/set weechat.look.mouse on
Per abilitarlo subito, digitare kbd:[Alt+m] oppure eseguire il seguente comando:
/mouse enable
È possibile disabilitarlo temporaneamente, e associare il comando ad un tasto. Ad esempio il tasto kbd:[Alt+%] per disabilitare il mouse per 10 secondi:
/key bind meta-% /mouse toggle 10
|
Important
|
When mouse is enabled in WeeChat, all mouse events are caught by WeeChat, so
actions such as copy/paste or clicks on URLs are not sent to the terminal. Using kbd:[Shift] key causes the events to be sent directly to the terminal, as if the mouse was disabled (on some terminals like iTerm, you have to use kbd:[Alt] instead of kbd:[Shift]). |
|
Note
|
Per qualunque problema con il mouse, consultare FAQ di WeeChat / Mouse ↗. |
Molti eventi del mouse predefiniti sono già definiti da WeeChat (consultare mouse actions).
È possibile cambiare o aggiungere combinazioni con il comando /key usando il
contesto "mouse" (per la sintassi, consultare comando
/key).
Il nome dell’evento consiste di un modificatore (opzionale), il nome di un
pulsante/rotellina e un’azione (opzionale). Elementi diversi sono separati da -.
List of modifiers (by order in the event name):
| Modificatore | Descrizione |
|---|---|
|
Tasto kbd:[Alt] |
|
Tasto kbd:[Ctrl] |
|
Tasto kbd:[Shift] (1) |
|
Note
|
(1) The shift modifier can rarely be used in WeeChat because many terminals
use this modifier to catch directly mouse events.
|
Several modifiers can be combined, for example:
-
alt-ctrl -
ctrl-shift -
alt-ctrl-shift
Elenco di pulsanti/rotellina:
| Pulsante/rotellina | Descrizione |
|---|---|
|
Click sul tasto sinistro |
|
Click sul tasto destro |
|
Click sul tasto centrale (spesso click sulla rotellina) |
|
Click sui pulsanti extra |
|
Rotellina (su) |
|
Rotellina (giù) |
Elenco di azioni (solo per i pulsanti, non la rotellina):
| Azione | Distanza |
|---|---|
|
3 … 19 |
|
≥ 20 |
|
3 … 19 |
|
≥ 20 |
|
3 … 39 |
|
≥ 40 |
|
3 … 39 |
|
≥ 40 |
List of incomplete events (only for buttons, useful for plugins/scripts):
| Event | Description |
|---|---|
|
Button was pressed but not released yet |
|
Mouse was moved with button pressed down |
Esempio di eventi:
-
button1 -
ctrl-button1 -
button1-gesture-right -
button1-event-down -
button1-event-drag -
alt-button2-gesture-down-long -
wheelup -
alt-ctrl-wheeldown -
…
|
Tip
|
Quando si associa un tasto nel contesto "mouse", è possibile far corrispondere
più eventi usando * all’inizio o alla fine del nome, ad esempio
button1-gesture-* corrisponderà ad ogni azione compiuta col tasto sinistro.
|
|
Tip
|
È possibile trovare il nome di un evento con il comando /input grab_mouse
poi eseguire l’evento col mouse. Il comando inserisce il nome dell’evento
nella riga di comando.
|
Il plugin Spell consente di verificare l’ortografia nella riga di comando. È possibile utilizzare più lingue per buffer.
Spell checking is disabled by default and can be toggled with key kbd:[Alt+s].
Before using spell checking, dictionaries must be defined, either globally or specific to buffers.
Multiple dictionaries can be used at same time: WeeChat will check words in all dictionaries.
For example to use English and French:
/set spell.check.default_dict "en,fr"
It is possible to use a different dictionary on a specific buffer, for example on a German channel:
/spell setdict de
You can also specify a dictionary for a group of buffers, for example English for all channels on libera IRC server:
/set spell.dict.irc.libera en
For more information, see the command /spell.
Le opzioni ortografiche possono essere definite aggiungendo opzioni nella sezione "opzioni" della configurazione di aspell.
Il nome dell’opzione è un parametro di configurazione per aspell. L’elenco delle opzioni disponibili può essere trovato nel terminale col seguente comando:
$ aspell config
Ad esempio, per abilitare l’opzione "ignore-case":
/set spell.option.ignore-case "true"
Suggestions are displayed in a bar item called "spell_suggest". The number of suggestions is set in option spell.check.suggestions.
To enable suggestions you must set option spell.check.suggestions to an integer ≥ 0 and add the bar item "spell_suggest" to a bar, like status.
Example of suggestions with English dictionary (en):
│[12:55] [6] [irc/libera] 3:#test(+n){4} [print,prone,prune] │
│[@Flashy] prinr █ │
└─────────────────────────────────────────────────────────────────────────────────┘
Example of suggestions with English and French dictionaries (en,fr):
│[12:55] [6] [irc/libera] 3:#test(+n){4} [print,prone,prune/prime,primer,primé] │
│[@Flashy] prinr █ │
└─────────────────────────────────────────────────────────────────────────────────┘
Sections in file spell.conf:
| Section | Control command | Description |
|---|---|---|
|
|
Colors. |
|
|
Options to control spell checking. |
|
|
Dictionaries used by buffer (options can be added/removed in section). |
|
|
Look and feel. |
|
|
Opzioni ortografiche (options can be added/removed in section). |
Options:
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:
| Option | Values | Description |
|---|---|---|
|
|
A bar with type |
|
|
Position of the bar: above/below chat, on the left/right. |
|
integer ≥ 0 |
Priority for display of bar: this is used for ordering the bars on screen when
many bars have same type and position. |
|
integer ≥ 0 |
The size of the bar: number of columns for position left/right, number
of lines for position top/bottom. A size of |
|
integer ≥ 0 |
The maximum size for a bar, |
|
color |
The default background color for the bar. |
|
color |
The default text color for the bar. |
|
color |
The color for delimiters in bar. |
|
|
When option is |
|
|
When option is |
|
string |
A list of items (see items for more info). |
|
|
Type of filling for a bar which has position |
|
|
Type of filling for a bar which has position |
|
string |
The conditions to display the bar (see conditions for more info). |
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.
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,[buffer_last_number]":
┌───────────────────────────────────────────────────────────────────────────┐ │[12:55] 3:irc/libera.#weechat [9] │ └───────────────────────────────────────────────────────────────────────────┘
An item called spacer can be used to align items (left, center, right).
When at least one spacer item is used in a bar, the whole bar width is used:
the spacers auto expand with the same size (or almost).
When the bar is not large enough for all items, spacers are not displayed.
|
Note
|
The spacer bar item can be used only in bars with position top or bottom,
filling horizontal and size 1.
|
Example of bar with items "[time],spacer,buffer_number+:+buffer_plugin+.+buffer_name,spacer,[buffer_last_number]":
┌───────────────────────────────────────────────────────────────────────────┐ │[12:55] 3:irc/libera.#weechat [9]│ └───────────────────────────────────────────────────────────────────────────┘
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).
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).
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"
Custom bar items can be added with the /item command, each new item having two properties defined via configuration options:
-
conditions: evaluated conditions to display the bar item, for example to restrict the bar item to some specific buffers (if empty, the bar item is displayed everywhere) -
content: evaluated content of bar item.
In both options, the following variables can be used:
-
window: pointer to the window where the bar is displayed (NULLfor root bars) -
buffer: pointer to buffer where the bar is displayed (current buffer for root bars).
Examples of conditions:
| Condition | Description |
|---|---|
|
Displayed in window bars only |
|
Displayed in all buffers with number = 1 |
|
Displayed in all IRC buffers |
|
Displayed in all buffers where local variable |
|
Displayed in all buffers where local variable |
|
Note
|
There’s no builtin way to refresh the custom bar items. You can use the Trigger plugin to force the refresh, for example via one or more signals received. |
For more information and examples, see the /item command.
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 ▲
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 /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)"
WeeChat can encrypt passwords or private data using secured data, stored in file sec.conf.
This configuration file is read before any other file, and the values stored inside can be used in various WeeChat or plugins/scripts options.
You can set a passphrase to encrypt data in sec.conf. This is not mandatory but highly recommended, otherwise data is stored as plain text in file.
/secure passphrase this is my passphrase
When a passphrase is set, WeeChat will ask you to enter it on startup
(but not on /upgrade).
If you are using a password manager, you can run an external program to read
the passphrase instead of having to type it manually on WeeChat startup.
For example with password-store (command pass):
/set sec.crypt.passphrase_command "/usr/bin/pass show weechat/passphrase"
The program may ask you unlock your GPG key or enter another passphrase to
read the secret. WeeChat will wait for the end of the command to read the
passphrase on the standard output (it must be on the first line without any
extra character).
If the output contains no passphrase or if it is wrong, WeeChat will then ask
you to enter it.
The encryption of data is made in 3 steps:
-
Derive a key from the passphrase (with optional salt).
-
Compute hash of data to encrypt.
-
Encrypt the hash + data (output is: salt + encrypted hash/data).
|
Note
|
The cipher block mode is CFB. |
The result is put as hexadecimal string in file sec.conf, for example:
[data] __passphrase__ = on libera = "53B1C86FCDA28FC122A95B0456ABD79B5AB74654F21C3D099A6CCA8173239EEA59533A1D83011251F96778AC3F5166A394"
To add secured data, use /secure set, for example a password for libera
IRC server:
/secure set libera mypassword
For comfort, secured data can be displayed in a dedicated buffer (kbd:[Alt+v] on buffer to see values), just do:
/secure
Secured data can be used in some options that can contain private data like
password, using this format: "${sec.data.xxx}" where "xxx" is the name of
secured data (used with /secure set xxx …).
For a complete list of supported options, see /help secure.
To use the libera password, for example with SASL authentication:
/set irc.server.libera.sasl_password "${sec.data.libera}"
Il plugin Alias consente di creare alias per i comandi (da WeeChat o altri plugin).
Some aliases are created by default, with name in upper case (to make them
different from standard commands); commands are not case sensitive in WeeChat,
so for example /close runs the alias /CLOSE.
List of default aliases:
Sections in file sec.conf:
| Section | Control command | Description |
|---|---|---|
|
|
Options for encryption. |
|
Secured data. |
Options:
Sections in file weechat.conf:
| Section | Control command | Description |
|---|---|---|
|
|
Debug level, for core and plugins (options can be added/removed in section). |
|
|
Startup options. |
|
|
Look and feel. |
|
|
Color aliases (options can be added/removed in section). |
|
|
Colors. |
|
|
Completion options. |
|
|
History options (commands and buffers). |
|
|
Proxy options. |
|
|
Network/TLS options. |
|
|
Options on plugins. |
|
|
Options on signals. |
|
|
Bar options. |
|
Layouts. |
|
|
Properties auto-applied on buffers when they are opened. |
|
|
Notify levels for buffers (options can be added/removed in section). |
|
|
Filters. |
|
|
Keys in default context. |
|
|
Keys in search context. |
|
|
Keys in cursor context. |
|
|
Keys in mouse context. |
Options:
Il plugin IRC è realizzato per chattare tramite protocollo IRC con altre persone.
È multi-server, ed offre tutti i comandi IRC supportati inclusi la chat DCC ed il trasferimento file (tramite plugin xfer, consultare plugin Xfer).
È possibile fornire un URL per uno o più server IRC, come segue:
irc[6][s]://[nick[:password]@]irc.esempio.org[:porta][/#canale][,#canale[...]]
Esempio per entrare in #weechat e #weechat-fr sul server irc.libera.chat, porta predefinita (6667), con il nick alice:
$ weechat irc://alice@irc.libera.chat/#weechat,#weechat-fr
By default no servers are defined. You can add as many servers as you want with the /server command.
For example to connect to libera.chat ↗ with TLS (encrypted trafic):
/server add libera irc.libera.chat/6697 -tls
You can tell WeeChat to auto-connect to this server on startup:
/set irc.server.libera.autoconnect on
To authenticate, it is recommended to use SASL (if supported on the server), with the password stored as secured data (see also chapter on SASL authentication):
/set irc.server.libera.sasl_username "alice"
/secure set libera xxxxxxx
/set irc.server.libera.sasl_password "${sec.data.libera}"
If SASL is not supported, you can use a command to send a message to nickserv:
/set irc.server.libera.command "/msg nickserv identify ${sec.data.libera}"
|
Note
|
By sending a message to nickserv, you may authenticate after joining channels
which could be a problem on some channels requiring you to be authenticated
to join. In this case, you can set a command delay:
/set irc.server.libera.command_delay 5.
|
Server options are named irc.server.<server>.<option> where <server> is the
internal name of the server and <option> the name of an option.
The value of a server option is inherited from irc.server_default.xxx
if the server option has the special value null.
For example if you created the libera server with the commands above, you’ll
see this with the command /fset libera:
irc.server.libera.addresses string "irc.libera.chat/6697"
irc.server.libera.anti_flood_prio_high integer null -> 2
irc.server.libera.anti_flood_prio_low integer null -> 2
irc.server.libera.autoconnect boolean on
irc.server.libera.autojoin string null -> ""
irc.server.libera.autojoin_dynamic boolean null -> off
irc.server.libera.autoreconnect boolean null -> on
irc.server.libera.autoreconnect_delay integer null -> 10
irc.server.libera.autorejoin boolean null -> off
irc.server.libera.autorejoin_delay integer null -> 30
irc.server.libera.away_check integer null -> 0
irc.server.libera.away_check_max_nicks integer null -> 25
irc.server.libera.capabilities string null -> "*"
irc.server.libera.charset_message enum null -> message
irc.server.libera.command string null -> ""
irc.server.libera.command_delay integer null -> 0
irc.server.libera.connection_timeout integer null -> 60
irc.server.libera.default_chantypes string null -> "#&"
irc.server.libera.ipv6 boolean null -> on
irc.server.libera.local_hostname string null -> ""
irc.server.libera.msg_kick string null -> ""
irc.server.libera.msg_part string null -> "WeeChat ${info:version}"
irc.server.libera.msg_quit string null -> "WeeChat ${info:version}"
irc.server.libera.nicks string null -> "alice,alice1,alice2,alice3,alice4"
irc.server.libera.nicks_alternate boolean null -> on
irc.server.libera.notify string null -> ""
irc.server.libera.password string null -> ""
irc.server.libera.proxy string null -> ""
irc.server.libera.realname string null -> ""
irc.server.libera.sasl_fail enum null -> reconnect
irc.server.libera.sasl_key string null -> ""
irc.server.libera.sasl_mechanism enum null -> plain
irc.server.libera.sasl_password string "${sec.data.libera}"
irc.server.libera.sasl_timeout integer null -> 15
irc.server.libera.sasl_username string "alice"
irc.server.libera.split_msg_max_length integer null -> 512
irc.server.libera.tls boolean on
irc.server.libera.tls_cert string null -> ""
irc.server.libera.tls_dhkey_size integer null -> 2048
irc.server.libera.tls_fingerprint string null -> ""
irc.server.libera.tls_password string null -> ""
irc.server.libera.tls_priorities string null -> "NORMAL:-VERS-SSL3.0"
irc.server.libera.tls_verify boolean null -> on
irc.server.libera.usermode string null -> ""
irc.server.libera.username string null -> "alice"
For example if you want to automatically connect to all servers you define without having to do it on each server, you can do:
/set irc.server_default.autoconnect on
And then you can reset the server option so that it uses the default inherited
value, which is now on instead of the default value off:
/unset irc.server.libera.autoconnect
Al momento della connessione al server IRC con TLS, WeeChat verifica in maniera predefinita che la connessione sia completamente fidata.
Esistono alcune opzioni per controllare la connessione TLS:
- weechat.network.gnutls_ca_system
-
load system’s default trusted certificate authorities on startup
- weechat.network.gnutls_ca_user
-
extra file(s) with certificate authorities
- irc.server.xxx.tls_cert
-
file del certificato TLS usato per identificare automaticamente il proprio nick ad esempio CertFP su oftc (a seguire)
- irc.server.xxx.tls_dhkey_size
-
dimensione della chiave usata durante lo Scambio Chiavi Diffie-Hellman (predefinita; 2048)
- irc.server.xxx.tls_verify
-
verifica che la connessione TLS sia totalmente fidata (opzione attivata in maniera predefinita)
|
Note
|
L’opzione "tls_verify" è attivata per default, in questo modo la verifica è rigorosa e potrebbe fallire, anche se funziona senza problemi con versioni precedenti la 0.3.1. |
-
Importare certificati nella shell:
$ mkdir -p ~/.config/weechat/tls $ wget -O ~/.config/weechat/tls/CAs.pem https://www.spi-inc.org/ca/spi-cacert.crt
|
Note
|
You must replace ~/.config/weechat by the path to your WeeChat config directory
which can also be for example ~/.weechat.
|
|
Note
|
E possibile concatenare più certificati nel file CAs.pem. |
-
In WeeChat, with "oftc" server already added:
/connect oftc
-
Creare un certificato nella shell:
$ mkdir -p ~/.config/weechat/tls $ cd ~/.config/weechat/tls $ openssl req -nodes -newkey rsa:2048 -keyout nick.pem -x509 -days 365 -out nick.pem
|
Note
|
You must replace ~/.config/weechat by the path to your WeeChat config directory
which can also be for example ~/.weechat.
|
-
In WeeChat, with "oftc" server already added:
/set irc.server.oftc.tls_cert "${weechat_config_dir}/tls/nick.pem"
/connect oftc
/msg nickserv cert add
For more information, please look at this page ↗.
WeeChat supports SASL authentication, using different mechanisms:
-
plain: password in chiaro (default)
-
scram-sha-1: SCRAM with SHA-1 digest algorithm
-
scram-sha-256: SCRAM with SHA-256 digest algorithm
-
scram-sha-512: SCRAM with SHA-512 digest algorithm
-
ecdsa-nist256p-challenge: challenge with public/private key
-
external: certificato TLS da lato client
Le opzioni nel server sono:
-
sasl_mechanism: meccanismo da usare (see above)
-
sasl_timeout: timeout (in secondi) per l’autenticazione
-
sasl_fail: action to perform if authentication fails
-
sasl_username: nome utente (nick)
-
sasl_password: password
-
sasl_key: file with ECc private key (for mechanism ecdsa-nist256p-challenge)
You must generate a private key in order to authentify with the ECDSA-NIST256P-CHALLENGE mechanism (no password is required on connection).
You can generate the key with this command:
$ openssl ecparam -genkey -name prime256v1 -out ~/.config/weechat/ecdsa.pem
|
Note
|
You must replace ~/.config/weechat by the path to your WeeChat config directory
which can also be for example ~/.weechat.
|
Get the public key (encoded as base64) with this command:
$ openssl ec -noout -text -conv_form compressed -in ~/.config/weechat/ecdsa.pem | grep '^pub:' -A 3 | tail -n 3 | tr -d ' \n:' | xxd -r -p | base64
Connect to the server, identify (for example with "nickserv identify") and set your public key in your account, using nickserv (replace the base64 value with your public key):
/connect libera /msg nickserv identify your_password /msg nickserv set pubkey Av8k1FOGetUDq7sPMBfufSIZ5c2I/QYWgiwHtNXkVe/q
Configure the SASL options in the server:
/set irc.server.libera.sasl_mechanism ecdsa-nist256p-challenge
/set irc.server.libera.sasl_username "your_nickname"
/set irc.server.libera.sasl_key "${weechat_config_dir}/ecdsa.pem"
Reconnect to the server:
/reconnect libera
You can connect to server with the /connect command:
/connect libera
To disconnect:
/disconnect libera
Or just this if you are on any buffer belonging to libera server (server, channel, private):
/disconnect
When you connect to multiple servers at same time, server buffers are merged
by default and you can switch between them with the kbd:[Ctrl+x] key.
It is possible to disable auto merge of server buffers to have independent
server buffers:
/set irc.look.server_buffer independent
Some servers support connections with Tor ↗, a network of virtual tunnels that allows people and groups to improve their privacy and security on the Internet.
Il primo passo consiste nell’installare Tor. Per Debian (e derivate):
$ sudo apt-get install tor
In WeeChat è necessario creare un proxy socks5 per il servizio Tor (nome host/IP e porta dipendono dalla propria configurazione di Tor):
/proxy add tor socks5 127.0.0.1 9050
Now, add a new server (replace server name "irc-tor" and the address by a valid one):
/server add irc-tor this.is.the.address.onion
Impostare il proxy per Tor:
/set irc.server.irc-tor.proxy "tor"
Set SASL authentication with ECDSA-NIST256P-CHALLENGE (see the chapter SASL ECDSA-NIST256P-CHALLENGE to generate a private key):
/set irc.server.irc-tor.sasl_mechanism ecdsa-nist256p-challenge
/set irc.server.irc-tor.sasl_username "your_nickname"
/set irc.server.irc-tor.sasl_key "${weechat_config_dir}/ecdsa.pem"
And finally, connect to the server:
/connect irc-tor
WeeChat supports the following IRCv3 extensions ↗:
By default all capabilities supported by the server and WeeChat are automatically enabled (see option irc.server_default.capabilities).
Tables with comparison of different IRC clients, including WeeChat, are available on this page ↗.
Specification: account-notify ↗
This capability allows the server to send messages when users identify or
unidentify on the server.
WeeChat displays such messages if the option
irc.look.display_account_message
is enabled (default value).
Examples:
-- alice has identified as Alice01 -- alice has unidentified
Specification: account-tag ↗
This capability allows the server to send account as message tag to commands
sent to the client.
WeeChat parses this tag and saves it in the message, but it is not used or
displayed. It can be used in /filter command to filter
messages matching specific accounts.
Example of raw IRC message received:
@account=Alice01 :user@example.com PRIVMSG #test :Hello!
Message displayed in channel:
<alice> Hello!
Message with tags:
<alice> Hello! [irc_privmsg,irc_tag_account_Alice01,notify_message,prefix_nick_lightcyan,nick_alice,host_user@example.com,log1]
Specification: away-notify ↗
This capability allows the server to send away notifications for users present on the same channels as you.
When the away status is changed for a user (away or back), this is reflected with a specific color in the nicklist, using the following options:
Specification: batch ↗
This capability allows the server to send batched events (grouping of several messages that are related).
For now, WeeChat only stores messages received in a batch and processes as usual later, when the batch ends.
Specification: cap-notify ↗
This capability allows the server to advertise on new or removed capabilities
on the server (via CAP NEW and CAP DEL commands).
Examples:
-- irc: client capability, now available: sasl -- irc: client capability, removed: sasl
Specification: chghost ↗
This capability allows the server to send messages when users change name or host.
When the option irc.look.smart_filter_chghost
is enabled (default value), the host changes are automatically hidden if the nick
has not spoken for several minutes.
The color of the change host message is controlled by the option
irc.color.message_chghost.
Example:
-- alice (user@example.com) has changed host to test.com
Specification: multiline ↗
This capability allows the client and server to send messages with multiple lines, using the batch capability, that must be enabled as well.
There are limits in term of bytes or number of lines in a multiline message that are given in the capability sent by the server, for example:
CAP alice LS * :draft/multiline=max-bytes=4096,max-lines=24
This sets a limit of 4096 bytes and 24 lines for a multiline batched content.
If the limits are not given by the server, the default in WeeChat are:
-
max bytes: 4096
-
max lines: 24
Only standard messages and those send by the /notice
command can be multiline.
ACTION CTCP messages sent with command /me are not affected
by this capability. That means multiline actions are sent as multiple actions.
|
Warning
|
As the specification is a "draft", it may change and the multiline support can
possibly break at any time in WeeChat. The capability is automatically enabled if the server supports it and can be disabled with this command: /set irc.server_default.capabilities "*,!draft/multiline".When the capability is disabled, a multiline message is sent as multiple messages, as if they were sent sequentially to the server. |
Example of IRC messages sent for a user message with two lines (this is a test
/ on two lines), send to channel #test:
BATCH +i8Je7M7gquddoyC9 draft/multiline #test @batch=i8Je7M7gquddoyC9 PRIVMSG #test :this is a test @batch=i8Je7M7gquddoyC9 PRIVMSG #test :on two lines BATCH -i8Je7M7gquddoyC9
Display of the message sent in WeeChat:
19:01:45 alice | this is a test
| on two lines
Specification: echo-message ↗
This capability forces the server to send PRIVMSG, NOTICE and TAGMSG messages back to WeeChat.
WeeChat displays only the message received and not the message sent, so a delay can be noticed between the send and the display. When the message is displayed, it means it has been properly received by the server and propagated to other clients connected to the server as well.
Specification: extended-join ↗
This capability allows the server to send account and real name when users
join channels.
WeeChat displays this additional information in join messages if the option
irc.look.display_extended_join
is enabled (default value).
Example:
--> john [John01] (John Doe) (~user@example.com) has joined #test
Specification: invite-notify ↗
This capability allows the server to send invite messages when users are invited to channels.
Example:
-- alice ha invitato bob in #test
Specification: message-tags ↗
This capability allows to add metadata in messages.
These tags can be displayed using the command /debug tags.
It must be enabled to use typing notifications.
Specification: monitor ↗
This capability allows the server to send notifications when clients become
online/offline.
WeeChat automatically uses this extension if available when using the
/notify command.
Specification: multi-prefix ↗
|
Note
|
For now, WeeChat doesn’t display all prefixes in the /names output, even if
they are received and properly saved internally.
|
Example: output of /whois alice:
-- [alice] @%+#test
Specification: server-time ↗
This capability allows the server to send time for messages as message tag.
When the time is received in a message, WeeChat uses it to display the message
(it can then be displayed with a past date).
The IRC proxy in Relay plugin supports this capability, so any IRC client of Relay should enable it to display the real message time in the backlog sent upon connection.
Specification: setname ↗
This capability lets you change your real name by using the /setname command.
Specification: userhost-in-names ↗
This capability allows the server to send hostnames in /names responses.
|
Note
|
WeeChat doesn’t display hostnames in the /names output.
|
Example of raw IRC messages received without the capability:
:irc.server 353 alice = #test :@alice bob +carol
Example of raw IRC messages received with the capability:
:irc.server 353 alice = #test :@alice!user1@host1 bob!user2@host2 +carol!user3@host3
You can join channels with the /join command:
/join #channel
Part a channel (keeping the buffer open):
/part [quit message]
The channels you joined are not saved. If you want to join them automatically
when connecting to the server, you must set the server autojoin option:
/set irc.server.libera.autojoin "#weechat,#weechat-fr"
|
Note
|
Some scripts can help to automatically set this option,
see /script search autojoin.
|
Be careful, spaces can be used only to separate list of channels from keys,
for example if #channel1 requires a key but not #channel2:
/set irc.server.libera.autojoin "#channel1,#channel2 key1"
For help on the format, see /help irc.server.libera.autojoin.
You can send a private message with the /query command, which opens a separate buffer:
/query bob hi, how are you?
Without arguments the command just opens the buffer (or selects it if already open):
/query bob
To close the private buffer, you can do this command on the private buffer:
/close
A smart filter is available to filter some messages when someone did not write anything in the channel during a configurable delay:
-
join: user joins the channel
-
part: user leaves the channel
-
quit: user quits the server
-
account: user changes its account
-
chghost: user changes name or host
-
mode: mode changes on channel
-
nick: user changes its nick
-
setname: user changes its real name
Smart filter is enabled by default, but you must add a filter to hide lines on buffers, for example:
/filter add irc_smart * irc_smart_filter *
It is possible to create filter for one channel only or channels beginning with
same name (see /help filter):
/filter add irc_smart_weechat irc.libera.#weechat* irc_smart_filter *
You can setup a longer delay (in minutes):
/set irc.look.smart_filter_delay 10
If someone did not write anything during last 10 minutes, its messages like join/part/quit will be hidden by default on channel, and you can use key kbd:[Alt+=] (toggle filters) to see them.
È possibile personalizzare le risposte CTCP, o bloccare alcune richieste CTCP (non rispondere).
Ad esempio, per personalizzare la richiesta CTCP "VERSIONE", utilizzare il seguente comando:
/set irc.ctcp.version "Uso WeeChat ${version}, fico!"
|
Note
|
The name of CTCP must be in lower case. That means option irc.ctcp.VERSION would not work. |
Se si desidera bloccare CTCP "VERSIONE" (non rispondere ad una query), allora basta impostare una stringa vuota:
/set irc.ctcp.version ""
Anche un CTCP sconosciuto può essere personalizzato, per esempio si può rispondere "BLABLA":
/set irc.ctcp.blabla "Questa è la mia risposta a CTCP BLABLA"
È possibile personalizzare CTCP per un solo server, utilizzando il suo nome interno prima del nome CTCP:
/set irc.ctcp.libera.version "WeeChat ${version} (per libera)"
Se si desidera ripristinare la risposta CTCP standard, allora disabilitare l’opzione:
/unset irc.ctcp.version
The CTCP replies are evaluated (see command /eval) and the following extra variables are available:
| Variable | Descrizione | Valore/esempio |
|---|---|---|
|
Elenco di CTCP supportate |
|
|
Versione di WeeChat |
|
|
Versione di WeeChat + Git version (1) |
|
|
Git version (1) |
|
|
Data di compilazione di WeeChat |
|
|
Informazioni sull’OS |
|
|
Sito di WeeChat |
|
|
Sito di WeeChat, pagina di download |
|
|
Data/ora correnti |
|
|
Nome utente sul server IRC |
|
|
Nome reale sul server IRC |
|
|
Note
|
(1) The Git version is the output of command git describe. It is known only
if WeeChat has been compiled inside the Git repository and if Git was installed.
|
The default CTCP replies are:
| CTCP | Formato risposta | Esempio |
|---|---|---|
CLIENTINFO |
|
|
SOURCE |
|
|
TIME |
|
|
VERSION |
|
|
È possibile personalizzare il buffer di destinazione per i messaggi IRC
(buffer usato per visualizzare messaggi) con l’opzione irc.msgbuffer.*.
Per alcuni messaggi IRC (elenco in basso), si possono usare i seguenti valori:
- current
-
buffer attivo (se è il buffer IRC, oppure sul buffer del server, come predefinito)
- private
-
buffer privato per il nick, o il buffer corrente se non trovato (in base all’opzione irc.look.msgbuffer_fallback)
- server
-
buffer del server
- weechat
-
Il buffer "core" di WeeChat
Quando l’opzione non è impostata (default), WeeChat sceglie il buffer appropriato, di solito quello del server o del canale.
Ecco una lista incompleta dei messaggi IRC o degli alias che è possibile personalizzare:
| messaggio | alias | descrizione |
|---|---|---|
|
errore |
|
|
invitato su un canale |
|
|
ingresso nel canale |
|
|
kick |
|
|
kill |
|
|
mode |
|
|
notifica |
|
|
part |
|
|
quit |
|
|
topic |
|
|
wallops |
|
|
ctcp (inviato o ricevuto, in un messaggio privato o di notifica) |
|
|
stringa modalità utente |
|
|
|
whois (connessione sicura) |
|
|
whois (assente) |
|
ison |
|
|
|
presente |
|
|
assente |
|
|
whois (nick registrato) |
|
|
whois (modalità aiuto) |
|
|
whois (utente) |
|
|
whois (server) |
|
|
whois (operatore) |
|
|
whowas |
|
|
who (fine) |
|
|
whois (inattività) |
|
|
whois (fine) |
|
|
whois (canali) |
|
|
whois (utente identificato) |
|
|
list (inizio) |
|
|
list (canale) |
|
|
list (fine) |
|
|
whois (con privilegi di operatore) |
|
|
whois (host) |
|
URL del canale |
|
|
data di creazione del canale |
|
|
|
whois (loggato come) |
|
nessun argomento per il canale |
|
|
argomento del canale |
|
|
informazioni sull’argomento |
|
|
|
whois (è un bot su) |
|
|
whois (host) |
|
invito |
|
|
|
whois (è opered come) |
|
|
reop sul canale |
|
|
reop sul canale (fine) |
|
|
lista di inviti |
|
|
lista di inviti (fine) |
|
|
lista di eccezioni |
|
|
lista di eccezioni (fine) |
|
versione del server |
|
|
|
who |
|
|
elenco di utenti su un canale |
|
|
fine dell’elenco /names |
|
|
elenco dei ban |
|
|
fine della lista dei ban |
|
|
whowas (fine) |
|
|
whois (connesso da) |
|
|
whois (usa le modalità) |
|
|
no such nick/channel |
|
|
no such server |
|
nick errato |
|
|
nick già utilizzato |
|
|
non autorizzato a cambiare nick |
|
|
|
whois (connessione sicura) |
|
|
quiet list |
|
|
end of quiet list |
|
|
list of monitored nicks |
|
|
list of monitored nicks (end) |
|
ora si è loggati |
Anche altri comandi numerici possono essere personalizzati.
Il messaggio può essere preceduto dal nome del server per essere più
precisi (ad esempio: libera.whois).
Alcuni esempi:
-
visualizza il risultato di
/whoissu un buffer privato:
/set irc.msgbuffer.whois private
-
ripristina il buffer predefinito per il whois (buffer del server):
/unset irc.msgbuffer.whois
-
visualizza inviti sul buffer corrente, solo per il server "libera":
/set irc.msgbuffer.libera.invite current
-
visualizza messaggio "303" (ison) sul buffer "core" di WeeChat:
/set irc.msgbuffer.303 weechat
Sections in file irc.conf:
| Section | Control command | Description |
|---|---|---|
|
|
Look and feel. |
|
|
Colors. |
|
|
Network options. |
|
|
Buffer di destinazione per i messaggi IRC (options can be added/removed in section). |
|
|
Risposte CTCP (options can be added/removed in section). |
|
Ignore people. |
|
|
|
Default values for servers (used when options in server are not defined). |
|
|
Servers. |
Options:
Il plugin Xfer fornisce:
-
chat diretta (tra due host, senza server): per esempio "DCC Chat" tramite plugin IRC
-
trasferimento file, per esempio "DCC" tramite il plugin IRC
Sections in file xfer.conf:
| Section | Control command | Description |
|---|---|---|
|
|
Look and feel. |
|
|
Colors. |
|
|
Network options. |
|
|
Options for files sent/received. |
Options:
The typing plugin is used to inform other users you are typing messages and show a list of users currently typing a message on the buffer.
It is used by IRC plugin on channel and private buffers, when the "message-tags"
capability is enabled (you can check with /cap command).
Under the hood, typing client tag is used, following
this specification ↗.
For privacy considerations, the typing feature is disabled by default.
If you want to use it, you must enable options in both typing and irc plugins:
/set typing.look.enabled_nicks on /set typing.look.enabled_self on /set irc.look.typing_status_nicks on /set irc.look.typing_status_self on
The typing notifications are displayed at the end of the status bar.
Example of status bar with the "typing" item: "bob" is typing a message and "alice" was typing a message but made a pause:
│[12:55] [6] [irc/libera] 3:#test(+n){4} [Typing: bob, (alice)] │
│[@Flashy] █ │
└─────────────────────────────────────────────────────────────────────────────────┘
When you are typing a message (not a command starting with /), the typing
plugin sends signals to inform other plugins (like IRC) that you are typing,
and these plugins can then send typing notifications to other users.
The following signals are sent when you are typing messages:
| Signal | Arguments | Description |
|---|---|---|
typing_self_typing |
Pointer: buffer. |
You are typing a message. |
typing_self_paused |
Pointer: buffer. |
You made a pause while typing a message. |
typing_self_cleared |
Pointer: buffer. |
You cleared the command line without sending the message. |
typing_self_sent |
Pointer: buffer. |
You sent the message to the buffer. |
The typing plugin is catching some signals that can be sent by other plugins (like IRC), to update internal hashtables used to store the typing state of nicks on buffers. These hashtables are used to build the content of "typing" bar item.
The following signals are caught by the typing plugin:
| Signal | Arguments | Description |
|---|---|---|
typing_set_nick |
String: buffer pointer + ";" + state (one of: "off", "typing", "paused",
"cleared") + ";" + nick. |
Set typing state for a nick on a buffer. |
typing_reset_buffer |
Pointer: buffer. |
Remove typing state for all nicks on a buffer. |
Sections in file typing.conf:
| Section | Control command | Description |
|---|---|---|
|
|
Look and feel. |
Options:
Il plugin Relay viene utilizzato per inoltrare i dati via rete, facendo uso di protocolli differenti:
-
irc: proxy IRC: usato per condividere le connessioni ai server IRC con uno o più client IRC
-
weechat: protocol used by remote interfaces to display and interact with WeeChat, see this page ↗.
It is highly recommended to set a password for relay, with these commands:
/secure set relay miapass
/set relay.network.password "${sec.data.relay}"
This password is used for irc and weechat protocols.
TOTP (Time-based One-Time Password) can be used as secondary authentication factor for weechat protocol, in addition to the password.
This is optional and increases the security level.
One-time passwords can be generated with applications, for example:
The TOTP secret must be set in WeeChat and the application used to generate one-time passwords.
It must be a string encoded in base32, with only letters and digits from 2 to 7, for example:
/secure set relay_totp secretpasswordbase32
/set relay.network.totp_secret "${sec.data.relay_totp}"
È possibile usare TLS creando un certificato e una chiave privata, e usando il prefisso "tls." nel nome del protocollo.
The default path to certificate/key is defined by option relay.network.tls_cert_key.
È possibile creare un certificato e una chiave privata con i seguenti comandi:
$ mkdir -p ~/.config/weechat/tls $ cd ~/.config/weechat/tls $ openssl req -nodes -newkey rsa:2048 -keyout relay.pem -x509 -days 365 -out relay.pem
|
Note
|
You must replace ~/.config/weechat by the path to your WeeChat config directory
which can also be for example ~/.weechat.
|
Se WeeChat è già in esecuzione, è possibile ricaricare il certificato e la chiave privata con il comando:
/relay tlscertkey
The Relay plugin can act as an IRC proxy: it will simulate an IRC server, and you can connect to WeeChat with any other IRC client (including WeeChat itself).
You can define one port by IRC server, or one generic port for all servers.
When using one port for all servers, the client must send the internal name of server in the IRC "PASS" command, with this format (see example below):
PASS server:miapass
Example: IRC proxy with TLS for any server (client will choose):
/relay add tls.irc 8000
Example: IRC proxy without TLS only for server "libera":
/relay add irc.libera 8000
Now you can connect on port 8000 with any IRC client using server password "miapass" (or "libera:miapass" if no server was specified in the relay).
For example if you use WeeChat as IRC client of the relay, with a server called "relay" and the relay password "secret", you can setup the password with these commands:
/secure set relay_libera libera:secret
/set irc.server.relay.password "${sec.data.relay_libera}"
Il plugin Relay può inviare dati alle interfacce remote usando il protocollo WeeChat.
You can connect with a remote interface, see this page ↗.
|
Important
|
WeeChat itself can NOT connect to another WeeChat with this protocol. |
Ad esempio:
/relay add weechat 9000
Ora è possibile connettersi sulla porta 9000 con un’interfaccia remota usando la password "miapass".
WebSocket protocol (RFC 6455 ↗) is supported in Relay plugin for all protocols.
The WebSocket handshake is automatically detected and socket becomes ready for WebSocket if required headers are found in handshake and if origin is allowed (see option relay.network.websocket_allowed_origins).
A WebSocket can be opened in a HTML5 with a single line of JavaScript:
websocket = new WebSocket("ws://server.com:9000/weechat");The port (9000 in example) is the port defined in Relay plugin. The URI must always end with "/weechat" (for irc and weechat protocols).
Using the protocol option "unix" with the /relay add command, you can listen
using any protocol on a UNIX domain socket at a given path. For example:
/relay add unix.weechat ${weechat_runtime_dir}/relay_socket
This allows clients to connect using the weechat protocol to /run/user/1000/weechat/relay_socket. This is particularly useful to allow SSH forwarding for relay clients, when other ports cannot be opened.
Using OpenSSH:
$ ssh -L 9000:.weechat/relay_socket user@hostname
This redirects local relay clients connecting on port 9000 to the WeeChat instance running on "hostname".
Sections in file relay.conf:
| Section | Control command | Description |
|---|---|---|
|
|
Look and feel. |
|
|
Colors. |
|
|
Network options. |
|
|
Options specific to irc protocol (irc proxy). |
|
|
Ports used for relay (irc and weechat protocols) (options can be added/removed in section). |
Options:
The /exec command lets you execute external commands inside WeeChat and
display the output locally, or send it to a buffer.
Sections in file exec.conf:
| Section | Control command | Description |
|---|---|---|
|
|
Options for commands. |
|
|
Colors. |
Options:
È possibile controllare da remoto WeeChat, inviando comandi o del testo ad una pipe FIFO (se l’opzione "fifo.file.enabled" è abilitata, e lo è per default).
The FIFO pipe is located in WeeChat runtime directory and is called weechat_fifo_12345 by default (where 12345 is the WeeChat process id).
La sintassi per i comandi/testo della pipe FIFO è una delle seguenti:
plugin.buffer *testo o comando qui *testo o comando qui
Backslashes can be interpreted with this format, where * is replaced by \,
allowing for example to send multiline messages:
plugin.buffer \text or command here \text or command here
Alcuni esempi:
-
Change nick on IRC server libera to "newnick":
$ echo 'irc.server.libera */nick newnick' >/run/user/1000/weechat/weechat_fifo_12345
-
Send a message on IRC #weechat channel:
$ echo 'irc.libera.#weechat *hello!' >/run/user/1000/weechat/weechat_fifo_12345
-
Send a multiline message on IRC #test channel, if capability "draft/multiline" is enabled on the ergo server:
$ echo 'irc.ergo.#test \hello\n...on two lines!' >/run/user/1000/weechat/weechat_fifo_12345
-
Send a message on current buffer:
$ echo '*hello!' >/run/user/1000/weechat/weechat_fifo_12345
-
Inviare due comandi per scaricare/caricare gli script Python (è necessario separarli con "\n"):
$ printf '%b' '*/python unload\n*/python autoload\n' >/run/user/1000/weechat/weechat_fifo_12345
Sections in file fifo.conf:
| Section | Control command | Description |
|---|---|---|
|
|
FIFO pipe control. |
Options:
Trigger is the Swiss Army knife for WeeChat: it can hook many things (signal, modifier, print, …), change the content of data, and execute one or more commands. A condition can be used to prevent the trigger to run in some circumstances.
Using triggers require you to know how the signals, modifiers, … are working. So you might consider reading the WeeChat plugin API reference / Hooks ↗.
WeeChat creates 5 triggers by default, which can be disabled, updated or deleted:
-
a beep trigger for notifications
-
four other triggers to hide passwords on screen
List of default triggers:
| Name | Hook | Description |
|---|---|---|
|
Beep on highlight/private message. |
|
|
modifier |
Hide password in commands:
|
|
modifier |
Hide password in command |
|
modifier |
Hide password in IRC auth message displayed (message received from server after the user issued the command). |
|
modifier |
Hide server password in commands |
A trigger has the following options (names are
trigger.trigger.<name>.<option>):
| Option | Values | Description |
|---|---|---|
|
|
When option is |
|
|
The hook used in trigger. For more information, see WeeChat plugin API reference / Hooks ↗. |
|
string |
The arguments for the hook, it depends on the hook type used. |
|
string |
Conditions to execute the trigger; they are evaluated (see command /eval). |
|
string |
One or more POSIX extended regular expressions, to change data received in the hook callback (and some stuff added by trigger plugin), see regular expression. |
|
string |
Command to execute (many commands can be separated by semicolons); it is evaluated (see command /eval). |
|
|
The return code of callback (default is |
|
|
Action to take on the trigger after execution (default is |
For example, the default beep trigger has following options:
trigger.trigger.beep.enabled = on
trigger.trigger.beep.hook = print
trigger.trigger.beep.arguments = ""
trigger.trigger.beep.conditions = "${tg_displayed} && (${tg_highlight} || ${tg_msg_pv})"
trigger.trigger.beep.regex = ""
trigger.trigger.beep.command = "/print -beep"
trigger.trigger.beep.return_code = ok
trigger.trigger.beep.post_action = none
When a trigger callback is called, following actions are executed, in this order, if triggers are globally enabled and if the trigger itself is enabled:
-
check trigger conditions: if false, exit
-
replace text in trigger using regular expression(s)
-
execute command(s)
-
exit with a return code (except for hooks modifier, line, focus, info and info_hashtable)
-
perform post action (if different from
none).
The arguments depend on the hook used. They are separated by semicolons.
| Hook | Arguments | Examples | Documentation (API) |
|---|---|---|---|
signal |
1. signal name (priority allowed) (required) |
|
|
hsignal |
1. signal name (priority allowed) (required) |
|
|
modifier |
1. modifier name (priority allowed) (required) |
|
|
line |
1. buffer type |
|
|
1. buffer name |
|
||
command |
1. command name (priority allowed) (required) |
|
|
command_run |
1. command (priority allowed) (required) |
|
|
timer |
1. interval in milliseconds (required) |
|
|
config |
1. option name (priority allowed) (required) |
|
|
focus |
1. area name (priority allowed) (required) |
|
|
info |
1. info name (priority allowed) (required) |
|
|
info_hashtable |
1. info name (priority allowed) (required) |
|
The conditions are used to continue processing in trigger, or stop everything.
They are evaluated, and data available in callback can be used (see data in callbacks and command /eval).
Example: the default beep trigger uses this condition to make a beep only on highlight or private message:
${tg_displayed} && (${tg_highlight} || ${tg_msg_pv})
The regular expression is used to change variables in callback hashtable.
Format is one of the following:
/string1/string2 /string1/string2/var s/string1/string2 s/string1/string2/var y/string1/string2 y/string1/string2/var
Fields:
-
sory: a letter with the command; if missing, default command issand the first char is then used as the delimiter:-
s: regex replacement: first string is a regular expression, second string is the replacement for every matching string -
y: chars translation: first string is a set of characters that are replaced by the characters in the second string; once evaluated, each string must have exactly the same number of UTF-8 chars
-
-
/: the regex delimiter; the char "/" can be replaced by any char (one or more identical chars) -
string1: the first string (use depends on the command) -
string2: the second string (use depends on the command) -
var: the hashtable variable to update
Many regular expressions can be separated by a space, for example:
s/regex1/replace1/var1 y/abcdef/ABDDEF/var2
For the command s, the format is: s/regex/replace or s/regex/replace/var
(where var is a variable of the hashtable).
As s is the default command, it can be omitted, so /regex/replace is also
valid (but the first char, which is the delimiter, must not be a letter).
Matching groups can be used in replace:
-
${re:0}to${re:99}:${re:0}is the whole match,${re:1}to${re:99}are groups captured -
${re:}+: the last match (with highest number) -
${hide:c,${re:N}}: match "N" with all chars replaced by "c" (example:${hide:*,${re:2}}is the group #2 with all chars replaced by*).
Example: use bold for words between *:
s/\*([^ ]+)\*/*${color:bold}${re:1}${color:-bold}*/
Example: default trigger server_pass uses this regular expression to hide
password in commands /server and /connect (chars in passwords are replaced
by *):
s==^(/(server|connect) .*-(sasl_)?password=)([^ ]+)(.*)==${re:1}${hide:*,${re:4}}${re:5}
|
Note
|
In this example, the delimiter used is "==" because there is a "/" in the regular expression. |
For the command y, the format is: y/chars1/chars2 or y/chars1/chars2/var
(where var is a variable of the hashtable).
Example: replace "a", "b" and "c" by upper case letter:
y/abc/ABC/
Example: rotate arrows clockwise:
y/←↑→↓/↑→↓←/
Example: convert all letters to lower case:
y/${chars:upper}/${chars:lower}/
Example: shift each letter by one position, preserving case: a→b, b→c … y→z, z→a:
y/${chars:a-z}${chars:A-Z}/${chars:b-z}a${chars:B-Z}A/
If var does not exist in the hashtable, it is created automatically with an empty value. This allows to create custom temporary variables.
If var is not specified, the default variable is used, it depends on hook type:
| Hook | Default variable | Update allowed (1) |
|---|---|---|
signal |
tg_signal_data |
|
hsignal |
||
modifier |
tg_string |
tg_string |
line |
message |
buffer, buffer_name, y, date, date_usec, date_printed, date_usec_printed, str_time, tags, notify_level, highlight, prefix, message |
tg_message |
||
command |
tg_argv_eol1 |
|
command_run |
tg_command |
|
timer |
tg_remaining_calls |
|
config |
tg_value |
|
focus |
||
info |
tg_info |
tg_info |
info_hashtable |
all variables received in hashtable |
|
Note
|
(1) All variables can be updated in the trigger, but only these variables have an effect on the value returned by the trigger and used by WeeChat. |
The command is executed after replacement of text with the regular expression. Many commands can be separated by semicolons.
It is evaluated (see command /eval) and text replaced with a regular expression can be used in the command.
Example: default beep trigger uses this command to make a beep (BEL):
/print -beep
Data received in callbacks are stored in hashtables (pointers and strings) and can be used in following options:
-
conditions
-
regex
-
command
The content of hashtables depend on the hook type.
A convenient way to see data in a trigger is to open trigger monitor buffer, using the command:
/trigger monitor
All callbacks set following variables in hashtable:
| Variable | Type | Description |
|---|---|---|
|
string |
Name of trigger. |
|
string |
Hook type: "signal", "command", etc. |
The "signal" callback sets following variables in hashtable:
| Variable | Type | Description |
|---|---|---|
|
string |
Name of signal. |
|
string |
Data sent with the signal. |
If the signal contains an IRC message, the message is parsed and following data is added in hashtable:
| Variable | Type | Description |
|---|---|---|
|
pointer |
Pointer to IRC server (variables in hdata of type "irc_server" can be used, like |
|
pointer |
Pointer to IRC channel (variables in hdata of type "irc_channel" can be used, like |
|
string |
Name of server (example: "libera"). |
|
string |
Tags in message (rarely used). |
|
string |
Message without tags. |
|
string |
Nick. |
|
string |
Hostname. |
|
string |
IRC command (example: "PRIVMSG", "NOTICE", …). |
|
string |
IRC channel. |
|
string |
Arguments of command (includes value of channel). |
|
string |
Text (for example user message). |
|
string |
The index of command in message ("-1" if command was not found). |
|
string |
The index of arguments in message ("-1" if arguments was not found). |
|
string |
The index of channel in message ("-1" if channel was not found). |
|
string |
The index of text in message ("-1" if text was not found). |
When the data is a pointer, the variable tg_signal_data can be used like this
to read a hdata property (in this example this is a pointer on a buffer):
${buffer[${tg_signal_data}].full_name}
The "hsignal" callback sets following variables in hashtable:
| Variable | Type | Description |
|---|---|---|
|
string |
Name of signal. |
The hashtable contains all keys/values from hashtable received (type: string/string).
The "modifier" callback sets following variables in hashtable:
| Variable | Type | Description |
|---|---|---|
|
string |
Name of modifier. |
|
string |
Data sent with modifier. |
|
string |
The string that can be modified. |
|
string |
The string without color codes. |
For the weechat_print modifier, variables using message tags are added (see hook print below), and following variables:
| Variable | Type | Description |
|---|---|---|
|
pointer |
Buffer where message is printed. |
|
string |
Plugin of buffer where message is printed. |
|
string |
Full name of buffer where message is printed. |
|
string |
Prefix of message printed. |
|
string |
Prefix without color codes. |
|
string |
Message printed. |
|
string |
Message without color codes. |
If the modifier contains an IRC message, the message is parsed and extra data is added in hashtable (see hook signal).
The "line" callback sets following variables in hashtable:
| Variable | Type | Description |
|---|---|---|
|
pointer |
Buffer. |
|
string |
Buffer name. |
|
string |
Buffer type ("formatted" or "free"). |
|
string |
Line number for a buffer with free content (≥ 0), -1 for a buffer with formatted content. |
|
string |
Line date (timestamp). |
|
string |
Microseconds of line date. |
|
string |
Date when line was displayed (timestamp). |
|
string |
Microseconds of date when line was displayed. |
|
string |
Date for display. It may contain color codes. |
|
string |
Tags of message (with comma added at beginning/end of string). |
|
string |
"1" if displayed, "0" if line filtered. |
|
string |
"-1" = no notify, "0" = low level, "1" = message, "2" = private message, "3" = highlight |
|
string |
"1" if highlight, otherwise "0". |
|
string |
Prefix. |
|
string |
Prefix without color codes. |
|
string |
Message. |
|
string |
Message without color codes. |
Variables set using tags in message:
| Variable | Type | Description |
|---|---|---|
|
string |
Number of tags in message. |
|
string |
Nick (from tag "nick_xxx"). |
|
string |
Color of nick in prefix (from tag "prefix_nick_ccc"). |
|
string |
User name and host, format: username@host (from tag "host_xxx"). |
|
string |
Notify level (none, message, private, highlight). |
|
string |
IRC message tag (key "xxx"). (1) |
|
string |
Notify level, if different from none. |
|
string |
"1" for a private message, otherwise "0". |
|
Note
|
(1) Commas are replaced by semicolons in IRC tag (key and value). |
The "print" callback sets following variables in hashtable:
| Variable | Type | Description |
|---|---|---|
|
pointer |
Buffer. |
|
string |
Message date/time (format: |
|
string |
"1" if displayed, "0" if line filtered. |
|
string |
"1" if highlight, otherwise "0". |
|
string |
Prefix. |
|
string |
Prefix without color codes. |
|
string |
Message. |
|
string |
Message without color codes. |
Variables set using tags in message:
| Variable | Type | Description |
|---|---|---|
|
string |
Tags of message (with comma added at beginning/end of string). |
|
string |
Number of tags in message. |
|
string |
Nick (from tag "nick_xxx"). |
|
string |
Color of nick in prefix (from tag "prefix_nick_ccc"). |
|
string |
User name and host, format: username@host (from tag "host_xxx"). |
|
string |
Notify level (none, message, private, highlight). |
|
string |
IRC message tag (key "xxx"). (1) |
|
string |
Notify level, if different from none. |
|
string |
"1" for a private message, otherwise "0". |
|
Note
|
(1) Commas are replaced by semicolons in IRC tag (key and value). |
The "command" callback sets following variables in hashtable:
| Variable | Type | Description |
|---|---|---|
|
pointer |
Buffer. |
|
string |
The number of arguments (the command itself counts for one). |
|
string |
Argument #N ( |
|
string |
From argument #N until end of arguments ( |
|
string |
The number of arguments with a split like the shell does (the command itself counts for one). |
|
string |
Argument #N with a split like the shell does ( |
The "command_run" callback sets following variables in hashtable:
| Variable | Type | Description |
|---|---|---|
|
pointer |
Buffer. |
|
string |
Command executed. |
The "timer" callback sets following variables in hashtable:
| Variable | Type | Description |
|---|---|---|
|
string |
Number of remaining calls. |
|
string |
Current date/time (format: |
The "config" callback sets following variables in hashtable:
| Variable | Type | Description |
|---|---|---|
|
string |
Option. |
|
string |
Value. |
The "focus" callback sets following variables in hashtable:
| Variable | Type | Description |
|---|---|---|
|
pointer |
Window. |
|
pointer |
Buffer. |
The hashtable contains all keys/values from hashtable received (type: string/string).
The "info" callback sets following variables in hashtable:
| Variable | Type | Description |
|---|---|---|
|
string |
Name of info. |
|
string |
Arguments. |
|
string |
Empty string (the info to return). |
Display URLs in green:
/trigger add url_color modifier weechat_print "${tg_notify}" "==[a-zA-Z0-9_]+://[^ ]+==${color:green}${re:0}${color:reset}=="
|
Note
|
The simple regex used to detect URL may not catch well all URLs, but it is faster than a complex regex. |
When someone sends a "ping" in a private buffer, this trigger will auto-reply
with pong:
/trigger add pong print "" "${type} == private && ${tg_message} == ping" "" "pong"
Following triggers can be used to customize things displayed when the size of terminal is changed:
/trigger add resize_small signal signal_sigwinch "${info:term_width} < 100" "" "/bar hide nicklist"
/trigger add resize_big signal signal_sigwinch "${info:term_width} >= 100" "" "/bar show nicklist"
The triggers catch the signal "signal_sigwinch", which is sent by WeeChat when signal SIGWINCH is received (when terminal size is changed).
The condition with ${info:term_width} checks the width of terminal (you can
also use ${info:term_height} if needed).
In the example, when the terminal becomes small, the nicklist is hidden. And the bar is restored when the width is greater or equal to 100 chars.
You can automatically save configuration files (*.conf), for example each
hour:
/trigger add cfgsave timer 3600000;0;0 "" "" "/mute /save"
Arguments for the timer hook are:
-
3600000: 3600 * 1000 milliseconds, the callback is called each hour
-
0: alignment on second (not aligned here)
-
0: max number of calls (0 = no end for the timer)
The command /mute /save will silently save configuration files (nothing
displayed on core buffer).
Sections in file trigger.conf:
| Section | Control command | Description |
|---|---|---|
|
|
Look and feel. |
|
|
Colors. |
|
|
Trigger options. |
Options:
WeeChat has a modular design and can be extended with plugins and scripts.
È importante evidenziare la differenza tra un plugin ed uno script: un
plugin è un file binario compilato e caricato con il comando /plugin,
mentre uno script è un file di testo caricato con un plugin come python
con il comando /python.
Un plugin è una libreria dinamica, scritta in C e compilata, che viene caricata da WeeChat. In GNU/Linux, il file ha estensione ".so", ".dll" in Windows.
I plugin trovati vengono caricati automaticamente all’avvio di WeeChat, ed è possibile caricare o scaricare i plugin durante l’esecuzione del programma.
È possibile utilizzare il comando /plugin per caricare/scaricare un plugin,
oppure elencare tutti i plugin caricati.
When a plugin is unloaded, WeeChat removes:
-
buffers
-
configuration options (options are written in files)
-
all hooks: commands, modifiers, process, etc.
-
infos and infolists
-
hdata
-
bar items.
Esempi per caricare, scaricare oppure elencare i plugin:
/plugin load irc /plugin unload irc /plugin list
I plugin predefiniti sono:
| Plugin | Descrizione |
|---|---|
alias |
Definisce gli alias per i comandi. |
buflist |
Bar item with list of buffers. |
charset |
Set di caratteri per la codifica/decodifica nei buffer. |
exec |
Execution of external commands in WeeChat. |
fifo |
pipe FIFO utilizzata per inviare comandi da remoto su WeeChat. |
fset |
Fast set of WeeChat and plugins options. |
irc |
protocollo chat per IRC. |
logger |
Registra i buffer su file. |
relay |
Relay dei dati via rete. |
script |
Gestore script. |
python |
API per lo scripting in Python. |
perl |
API per lo scripting in Perl. |
ruby |
API per lo scripting in Ruby. |
lua |
API per lo scripting in Lua. |
tcl |
API per lo scripting in TCL. |
guile |
API per lo scripting in Guile (scheme). |
javascript |
API per lo scripting in JavaScript. |
php |
API per lo scripting in PHP. |
spell |
Controllo ortografico per la riga di comando. |
trigger |
Text replacement and command execution on events triggered by WeeChat/plugins. |
typing |
Display users currently writing messages. |
xfer |
Trasferimento file e chat diretta. |
Per saperne di più riguardo lo sviluppo di plugin o script (tramite le API), per favore consultare Riferimento API dei Plugin per WeeChat ↗ oppure Guida allo Scripting di WeeChat ↗.
WeeChat fornisce 8 plugin per lo scripting: Python, Perl, Ruby, Lua, Tcl, Guile (scheme), JavaScript, PHP. Questi plugin possono caricare, eseguire e scaricare gli script per questi linguaggi.
Per maggiori informazioni su come scrivere gli script, o le API WeeChat per gli script, consultare la Guida allo Scripting di WeeChat ↗.
The script manager (command /script) is used to load/unload scripts of any language, and install/remove scripts of WeeChat scripts repository, which are visible on this page ↗.
For privacy considerations, the download of scripts is disabled by default.
To enable it, type this command:
/set script.scripts.download_enabled on
Then you can download the list of scripts and display them in a new buffer with the /script command:
┌──────────────────────────────────────────────────────────────────────────────────────────────────────────────┐ │1.weechat│368/368 scripts (filter: *) | Sort: i,p,n | Alt+key/input: i=install, r=remove, l=load, L=reload, u=│ │2.scripts│* autosort.py 3.9 2020-10-11 | Automatically keep buffers grouped by server│ │ │* multiline.pl 0.6.3 2016-01-02 | Multi-line edit box, also supports editing o│ │ │* highmon.pl 2.7 2020-06-21 | Adds a highlight monitor buffer. │ │ │*ia r grep.py 0.8.5 0.8.5 2021-05-11 | Search regular expression in buffers or log │ │ │* autojoin.py 0.3.1 2019-10-06 | Configure autojoin for all servers according│ │ │* colorize_nicks.py 28 2021-03-06 | Use the weechat nick colors in the chat area│ │ │*ia r go.py 2.7 2.7 2021-05-26 | Quick jump to buffers. │ │ │* text_item.py 0.9 2019-05-25 | Add bar items with plain text. │ │ │ aesthetic.py 1.0.6 2020-10-25 | Make messages more A E S T H E T I C A L L Y│ │ │ aformat.py 0.2 2018-06-21 | Alternate text formatting, useful for relays│ │ │ alternatetz.py 0.3 2018-11-11 | Add an alternate timezone item. │ │ │ amarok2.pl 0.7 2012-05-08 | Amarok 2 control and now playing script. │ │ │ amqp_notify.rb 0.1 2011-01-12 | Send private messages and highlights to an A│ │ │ announce_url_title.py 19 2021-06-05 | Announce URL title to user or to channel. │ │ │ anotify.py 1.0.2 2020-05-16 | Notifications of private messages, highlight│ │ │ anti_password.py 1.2.1 2021-03-13 | Prevent a password from being accidentally s│ │ │ apply_corrections.py 1.3 2018-06-21 | Display corrected text when user sends s/typ│ │ │ arespond.py 0.1.1 2020-10-11 | Simple autoresponder. │ │ │ atcomplete.pl 0.001 2016-10-29 | Tab complete nicks when prefixed with "@". │ │ │ audacious.pl 0.3 2009-05-03 | Display which song Audacious is currently pl│ │ │ auth.rb 0.3 2014-05-30 | Automatically authenticate with NickServ usi│ │ │ auto_away.py 0.4 2018-11-11 | A simple auto-away script. │ │ │ autoauth.py 1.3 2021-11-07 | Permits to auto-authenticate when changing n│ │ │ autobump.py 0.1.0 2019-06-14 | Bump buffers upon activity. │ │ │ autoconf.py 0.4 2021-05-11 | Auto save/load changed options in a .weerc f│ │ │ autoconnect.py 0.3.3 2019-10-06 | Reopen servers and channels opened last time│ │ │[12:55] [2] [script] 2:scripts │ │ │█ │ └──────────────────────────────────────────────────────────────────────────────────────────────────────────────┘
Sections in file script.conf:
| Section | Control command | Description |
|---|---|---|
|
|
Look and feel. |
|
|
Colors. |
|
|
Options for download of scripts. |
Options:
Sections in file python.conf:
| Section | Control command | Description |
|---|---|---|
|
|
Look and feel. |
Options:
Sections in file perl.conf:
| Section | Control command | Description |
|---|---|---|
|
|
Look and feel. |
Options:
Sections in file ruby.conf:
| Section | Control command | Description |
|---|---|---|
|
|
Look and feel. |
Options:
Sections in file lua.conf:
| Section | Control command | Description |
|---|---|---|
|
|
Look and feel. |
Options:
Sections in file tcl.conf:
| Section | Control command | Description |
|---|---|---|
|
|
Look and feel. |
Options:
Sections in file guile.conf:
| Section | Control command | Description |
|---|---|---|
|
|
Look and feel. |
Options:
Sections in file php.conf:
| Section | Control command | Description |
|---|---|---|
|
|
Look and feel. |
Options:
Before asking for support, be sure you’ve read documentation and FAQ provided with WeeChat.
For support with IRC, on server irc.libera.chat:
-
official channels (with developers):
-
#weechat (English)
-
#weechat-fr (French)
-
-
non-official channels:
-
#weechat-de (German)
-
#weechat-fi (Finlandese)
-
For other ways of support, see this page ↗.