Introduction to Linux - A Hands on Guide This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
- $ systemctl status wksmitx State: running Jobs: 0 queued Failed: 0 units Since: Tue 2021-03-23 11:02:04 CET; 1min 3s ago CGroup: / ├─user.slice │ └─user-1000.slice │ ├─user@1000.service │ │ ├─app.slice │ │ │ ├─app-flatpak-com.slack.Slack-3434.scope │ │ │ │ ├─3434 bwrap -args 41 /app/bin/zypak.
- When the files are done downloading to your Arch Linux PC, use the CD command to move into the “slack-term” directory. Build and install Slack-term on your Arch Linux PC by executing the makepkg command. Be aware that this build may fail. If you need help troubleshooting, refer to the comment section of the package.
This article or section needs language, wiki syntax or style improvements. See Help:Style for reference.
WeeChat is a highly extendable and feature rich IRC client.
Installation
Install the weechat package, or weechat-gitAUR for the development version.
Usage
WeeChat provides two executables:
Blackarch Linux Live
weechat, the curses interface, see weechat(1)weechat-headless, the headless version, see weechat-headless(1)
Read the quick start guide. For details consult the user's guide.
Configuration
By default WeeChat stores its configuration files in ~/.weechat. Editing these files directly is not recommended because WeeChat may write them at any time.[1]
Instead you should use the /set command. You can get a list of all configurable options by running /set in the WeeChat buffer window. Since there are nearly 600 default configurable options, you can search through them with a wildcard syntax: /set irc.server.* or /set *server* as an example. You can get help on each option with the /help command:
~/.weechat directory somewhere else (like in your $XDG_CONFIG_HOME), use this option: $ weechat -d $XDG_CONFIG_HOME/weechat or set the environment variable WEECHAT_HOME.Connecting to a server
You can connect to a IRC server by adding it and then using /connect:
See the WeeChat documentation and /help server for more information.
Black Ark Linux
/connect, without previously adding the server, is not allowed. To enable this functionality, use /set irc.look.temporary_servers on.Configuring SSL
Many IRC servers, including freenode where #archlinux is, support SSL.
If you're making a server with /server, add the SSL port (usually 6697) and -ssl to the end of the line. For example:
set irc.server.freenode.ssl_dhkey_size 1024 or /set irc.server.chat.freenode.net.ssl_dhkey_size 1024 (see the server log)You may also want to change the location where WeeChat looks for trusted authorities (the default value is %h/ssl/CAs.pem which translates to ~/.weechat/ssl/CAs.pem):
Tips and Tricks
Upgrading
WeeChat can be upgraded without disconnecting from the IRC servers (non-SSL connections only):
This will load the new WeeChat binary and reload the current configuration.
Aliases
Aliases can be created to simplify commonly executed commands. A nice example is Wraithan's smart filter alias:
Smart Filter
First, we need to enable smart filters:
Next, we will create the sfilter alias:
We can now type
in any buffer, and the smart filter will only be enabled for that buffer.
The following alias will remove a previously enabled smart filter in the current buffer. Add the alias:
and execute it by
Exec command
A new plugin called 'exec' has been added, with command /exec. It will execute external command and can display output to the current buffer with the -o option or locally (default).
Key Bindings
See /help key.
SSH connection lost when idle
If you're connecting to your WeeChat through a remote shell using SSH, for example running it in GNU Screen or tmux you might experience getting disconnected after a while when idle. There are multiple factors in play why this might happen, but the easiest way to change this is to force the connection to be kept alive by appending this to your SSH-configuration on the remote shell.
This has nothing to do with WeeChat itself, but losing connection when idle won't happen with it's alternative irssi by default, and thus is a common situation for those converting to WeeChat.
Or have a look at Mosh.
Slack
There is a native client for slack: wee-slack
Desktop notifications
To receive desktop notifications for mentions or private messages, the weechat-notify-send script by Petr Zemek can be used.
To install, use:
The script uses libnotify and is known to work with both KDE and Gnome.
Another alternative with the built-in trigger plugin is to set a value for trigger.trigger.beep.command.
Mobile device notifications
To receive notifications for mentions or private messages to an Android mobile device, you can use the IrssiNotifier port to WeeChat from here. This script requires a Google Account, and a registration step with the service provider to obtain an API key. Then, install the plugin
and intialize the API token and end-to-end encryption password in WeeChat
An alternative that does not require a Google Account is a Ruby script for NotifyMyAndroid.com from here, with a similar installation procedure to the above, but into ~/.weechat/ruby.
WeeChat Relay with a Systemd User Service
To use your WeeChat instance as a WeeChat relay for other WeeChat clients (not to be confused with the IRC relay feature) you can use the WeeChat relay plugin and either a systemd user service, if you only want headless operation, or a combination of a systemd user service and tmux to maintain full command line functionality.
Either method involves creating a service file in the directory ~/.config/systemd/user/
Tmux Method
Due to the incompatibilities between how systemd manages jobs and the client-server behavior of tmux you will want to use the -L option to separate your default tmux sessions from the WeeChat one being managed by systemd. If this is the first tmux session started using the default socket then stopping and restarting the WeeChat user service will kill all the sessions connected to the default tmux socket. If the WeeChat tmux session is started after another default tmux session then the WeeChat session will die once systemd moves onto the next service unit. Sequestering the WeeChat tmux server to its own socket forces the expected behaviors when invoking systemctl start, stop, and restart. This does however mean that you will not see the WeeChat session when using tmux without using -L to select the correct socket.
Once the service is in place all you need to do is enable it with systemctl --user enable weechat and loginctl enable-linger
From there you can start the service and connect to the tmux session in order to configure the weechat relay plugin.
From there you can configure the WeeChat relay plugin with the desired settings on the console: https://www.weechat.org/files/doc/stable/weechat_user.en.html#relay_plugin
Headless Method
A key difference with this method is that you will either need to start WeeChat normally, configure the relay plugin, stop WeeChat, and then start the service or edit your relay.conf file manually while WeeChat is not running and then start your service. Either way you will need to configure your relay settings before starting your systemd WeeChat service: https://www.weechat.org/files/doc/stable/weechat_user.en.html#relay_plugin
Note that we do not need an ExecStop defined because systemd will automatically track the PID and send the appropriate shutdown signal to the daemon.
Once the service is in place all you need to do is enable it with systemctl --user enable weechat-headless
When you are ready to start your headless relay use systemctl --user start weechat-headless
Troubleshooting
Arch Slack Stock
Errors loading plugins
You may see output like the following in the main window after starting weechat:
The default configuration for weechat attempts to load all plugins found in /usr/lib/weechat/plugins which in this case includes ruby, lua, aspell and tcl. These packages are not required by the weechat package and may not be installed on your machine. There are two options if these errors bother you:
- Installruby, lua, aspell and/or tcl from the official repositories.
- Or, run
/set weechat.plugin.autoload '*,!ruby,!lua,!aspell,!tcl'which will prevent loading those plugins with a bang (!) prefix.
Problem loading multiline.pl
This problem happens with perl version >= 5.31.1
The script multiline.pl depends on the Pod::Select module. However, since perl version v5.31.1 Pod::Select has been removed.
To fix the problem, install perl-pod-parser.
Getting Help
To access WeeChat's built-in help, simply type
and the help will be displayed in the main buffer (usually buffer 1).
See also
Guides
- Official WeeChat quick start guide - a good place to start
- FiXato's guide to WeeChat - A Weechat Contributers Guide
- My always up-to-date WeeChat configuration - r3m (weechat-dev)