#WEECHAT ADD SERVER SOFTWARE#

Our persistent IRC-setup is ready to rumble. We can detach (or just close the terminal, also works perfectly fine) and then reattach later to read what we have been missing out on. Now the only thing left is running a weechat inside of our tmux and we are done. This also works when we detach and then log out of our machine, log in again and then reattach our tmux. We can then type d to detach and our shell is gone.Īfterwards, we can reattach to our tmux by running tmux attach and our shell is back!

We can now hit Ctrl+b to tell tmux to await a tmux-command and not forward our typing to the shell but instead interpret it as a command to tmux itself. This is a tmux and a shell running inside of it.

We now see a green bar at the bottom ouf our screen. So we exit our weechat and are back on our shell. Tmux allows to reattach to what we have done when last SSH-ing into our server. Usually, upon SSH-disconnect, all of our processes will be killed (including our weechat). However, once we exit our weechat, we are no longer connected and missing out all the fun! So our weechat needs to run continuously. leaving channels: /close in channelbuffer.If you have scrolled up, weechat will not follow as it assumes you want to read the part you scrolled to. If we are at the very bottom of a buffer, weechat will automatically scroll down with incoming messages. We can scroll backward and forward by using the PgUp- and PgDown-Keys. We can save our changes via /save and exit weechat via /quit. To find all the channels on a IRC-server, we can issue a /list (for freenode, be aware, the list is HUGE). To enter channels on a server upon starting weechat, we can set the option, to a comma-separated list of channels '#channel1,#channel2,#channel3'. To get back to our channel-buffer, /buffer or F6 will bring you there. To get back to our server-buffer, we can type /buffer 1 or hit F5, both will bring us back to buffer 1, which is our server-buffer. In the bar right above where we type we see a 2:#mytestchannel.Įach buffer represends one server or channel. Which is a very boring channel as no one except for ChanServ and us is here, which you can see on the user list for this channel on the right.īut it technically worked and we can now just type to post messages in this channel. We can then join channels via /join #mytestchannel

Weechat also supports globbing in the optionname, so getting all options for our added server can be done by /set irc.server.*Ĭommunication on IRC happens in channels.Įach channel usually has a certain focus of stuff that happens there. Generally, options in weechat can be set by /set or read by /set. To change it persistently, we can set the corresponding option in weechat via /set 'demodude' will be the weechat-internal name for this server, can also include a port by appending it via /.Īdding the freenode-network could therefore read /server add freenode /6697 -ssl -autoconnectĪfterwards, we can connect to the freenode-network by issuing /connect freenodeĪs the autoconnect only works upon starting of weechat.Īlternatively, /quit weechat and start it again we should get autoconnected.Īnd now, we are connected to the freenode-network!īy default, our nick will be set according to our username on the system. ssl will enable encryption to the IRC network by default, -autoconnect will enable autoconnect in the server config, so that our weechat will automatically connect to that server when we start it. The options -ssl and -autoconnect are both optional. To add a server, type /server add -ssl -autoconnect In this shell we can then start weechat, a fully keyboard-controlled terminal-IRC-client. We can access our account via ssh should end up in a plain terminal prompt where we can type. This post, however, will focus on the tmux-setup.

#WEECHAT ADD SERVER SOFTWARE#

Software installed on said machine: tmux, weechatĪlternatively to tmux, screen can be used if you cannot get tmux installed on the machine you want to run this setup on, it works very similar.

an account on said machine that is accessible via SSH.

A computer that is powered and connected to the internet 24/7.

One is a so called bouncer that works like a proxy that mediates between you and the IRC network and buffers the messages.Īnother, simpler method is just running a IRC-client on a machine that is always powered on, like a server, that we can reconnect to to read our messages (and of course write new ones). There are several ways of building a persistent IRC-setup. This is obviously an unbearable state, this needs immediate fixing! Persistent IRC Setup However, when you don’t stay connected all the time (why do you shut down your computer anyways…) you are missing out a lot of that fun!

Weechat add server