GitLab

fix #3042

This way, the users can receive the result of any IRC command (although not
parsed nor formatted in anyway) when biboumi doesn’t support it

fix #2884

Messages received on an IRC server JID are forwarded as raw IRC messages.

fix #2486

This environment variable points to the location the user expects to
find every program’s config file, or if it isn’t set, ~/.config/biboumi
(with a fallback to . if $HOME isn’t set).

fix #2553

Note, in our context, is_connecting() includes the resolving part as well as
the actual connection (if we are using c-ares)

fix #3048

fix #3047

This reverts commit ad0465b3.

Conflicts:
	louloulibs

To avoid doing a double exit when receiving bot SIGINT and SIGTERM

This let users send message to nicks such as Q@CServe.quakenet.org

fix #3047

Only keep some biboumi-specific commands into biboumi_adhoc_commands.hpp/cpp

Because apparently when cloning a repository with submodules, git creates
empty sub-directories

ref #2472

in this order:
- Make sure it is utf-8 encoded
- Remove all chars that are invalid in XML
- Escape all XML special chars (&'"<>)

By using SYSTEMD_FOUND instead of SYSTEMDDAEMON_FOUND, where I forgot to
rename it…

Also fix some doc

This option lets the administrator choose a specific IRC server, and only
that server can be used with this biboumi instance.

In this mode, JIDs to use are changed like this:

- #chan%irc.example.com@biboumi.example.com      -> #chan@biboumi.example.com
- user!irc.example.com@biboumi.example.com       -> user!@biboumi.example.com
- #chan%irc.example.com@biboumi.example.com/Nick -> #chan@biboumi.example.com/Nick
- %irc.example.com@biboumi.example.com           -> no equivalent
- irc.example.com@biboumi.example.com            -> no equivalent

fix #2715