We offer E-Z Arch Laminating Clamps and many more solutions for your radius millwork department. Make curved woodwork a profitable part of your business. Put our 20 years of architectural millwork experience to work for you. Arch Linux AUR If you use Arch Linux, you’ll be happy to know that there’s a Slack-term AUR package available. To start the installation process of the Slack-term AUR package, install “Base-devel” and “Git” with the Pacman command below. Sudo pacman -S base-devel git. Slack is a new way to communicate with your team. It’s faster, better organized, and more secure than email. They are the relative newcomer Arch Linux (created in 2002) and venerable battle-tested Slackware Linux (created in 1993 and currently the oldest actively-maintained Linux distro—kids who were born when Slackware was released are driving cars today).

1. Slack Archive
2. Slack Architecture
3. Slack Arch Linux

Artist: Karen Slack
Dedicated: August 20, 1981
Medium: Painted Steel
Park: Dunn Park
History: In the 1970s, an agreement between Kansas City Parks and Recreation and the Sculpture Department of the Kansas City Art Institute was made to display chosen student sculptures from the Art Institute on Kansas City’s boulevards and parkways. This helped fulfill the idea of KCPR to add art and interest to the boulevards at very little cost, and gave the students an opportunity to have their artistic creations on temporary display. The ownership stayed with the student and the KCPR Board of Commissioners retained the right to remove or replace the sculpture at any time.

One of these students was Karen Slack. Her creation was a 16-foot metal sculpture which she envisioned as type of gate along the lines of a Japanese gate called a torii. Karen was from near Manhattan, Kansas. Before her sculpture was placed in Kansas City, she was killed by a hit-and-run driver as she was walking in Manhattan in August 1979.

Karen’s parents gave the sculpture to KCPR and it was put in Wilbur Dunn Park at 67^th and The Paseo, which was one of the possible locations that Karen proposed for the sculpture’s placement.

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-git^AUR for the development version.

Usage

WeeChat provides two executables:

• 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:

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.

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:

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

Errors loading plugins

You may see output like the following in the main window after starting weechat:

Slack Archive

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:

1. Installruby, lua, aspell and/or tcl from the official repositories.
2. 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

Slack Architecture

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

Slack Arch Linux

• 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)