diff options
Diffstat (limited to 'doc/it/weechat_user.it.adoc')
| -rw-r--r-- | doc/it/weechat_user.it.adoc | 148 |
1 files changed, 74 insertions, 74 deletions
diff --git a/doc/it/weechat_user.it.adoc b/doc/it/weechat_user.it.adoc index e15f9b9bd..ac62414de 100644 --- a/doc/it/weechat_user.it.adoc +++ b/doc/it/weechat_user.it.adoc @@ -585,80 +585,6 @@ Poi, come per un crash, usare il comando `bt full`: (gdb) bt full ---- -// TRANSLATION MISSING -[[upgrade]] -== Upgrade - -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. - -// TRANSLATION MISSING -[[upgrade_command]] -=== Upgrade command - -WeeChat can restart the new binary, in place, using the -<<command_weechat_upgrade,/upgrade>> command: the buffer contents and non-SSL -connections are preserved. + -The SSL connections are lost during upgrade and are restored automatically -after the upgrade (reload of SSL 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 ----- - -// TRANSLATION MISSING -[[restart_after_upgrade]] -=== Restart after upgrade - -[[restart_release_notes]] -==== Release notes - -After an upgrade, it is *strongly recommended* to read the -https://weechat.org/files/releasenotes/ReleaseNotes-devel.html[release notes ^↗^,window=_blank] -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. - -[[restart_configuration_upgrade]] -==== Configuration upgrade - -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). - [[running_weechat]] == Esecuzione di WeeChat @@ -862,6 +788,80 @@ You can use the command <<command_weechat_set,/set>>, which checks the value and applies immediately the changes. // TRANSLATION MISSING +[[upgrade]] +== Upgrade + +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. + +// TRANSLATION MISSING +[[upgrade_command]] +=== Upgrade command + +WeeChat can restart the new binary, in place, using the +<<command_weechat_upgrade,/upgrade>> command: the buffer contents and non-SSL +connections are preserved. + +The SSL connections are lost during upgrade and are restored automatically +after the upgrade (reload of SSL 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 +---- + +// TRANSLATION MISSING +[[restart_after_upgrade]] +=== Restart after upgrade + +[[restart_release_notes]] +==== Release notes + +After an upgrade, it is *strongly recommended* to read the +https://weechat.org/files/releasenotes/ReleaseNotes-devel.html[release notes ^↗^,window=_blank] +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. + +[[restart_configuration_upgrade]] +==== Configuration upgrade + +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). + +// TRANSLATION MISSING [[interface]] == Interface |