- Table of contents
- How do I add accounts to my Quassel Core?
- Where can I configure the autojoin list?
- Where is the config or script directory?
- Why isn't Quassel using "Launchpad"?
- I lost my menu, how can I make it reappear?
- Quassel-Client (or Monolithic) won't start anymore (no visible window)
- How do I hide Join/Part/Quit messages?
- How do I start Quassel minimized?
- Is there a list of command-line options?
- How do I ignore specific highlights?
- How do I include special characters in Highlight/Ignore rules?
- How do I ignore CTCP requests?
- Why does clicking on the systray icon take me to some strange buffer called something like "bartol.freenode.net"?
- Why is the client showing the Core Setup Wizard when I've already set up my core?
How do I add accounts to my Quassel Core?¶
Check out the article on how to manage core users
Where can I configure the autojoin list?¶
There is no list as such. Quassel will automatically rejoin the channels you were in at the time you shut Quassel down.
Where is the config or script directory?¶
See Config Directories or Script Directories
Why isn't Quassel using "Launchpad"?¶
At the time being Launchpad doesn't support git.
I lost my menu, how can I make it reappear?¶
Do you still have the toolbar with "connect", "disconnect" and other buttons? If you have it, and right click it, 'show menubar' is the last item.
In old versions, you could press
Ctrl + M and the menu bar should reappear. This was removed as the default shortcut due to accidental use. You can click Settings>Shortcuts, and specify any custom shortcut for "Show menubar".
For other toolbars, you can display them from the submenu entitled "View".
Quassel-Client (or Monolithic) won't start anymore (no visible window)¶
~/.conf/quassel-irc.org/quasselclient.conf if there's a line with
MainWinHidden=true. If so, change that to
How do I hide Join/Part/Quit messages?¶
Right-click inside the chat and choose Joins/Parts/Quits in the "Hide Events" menu.
How do I start Quassel minimized?¶
Start Quassel with the command-line option
Is there a list of command-line options?¶
For an up to date list of command line options start Quassel with the option
How do I ignore specific highlights?¶
Version 0.13.0 and newer offer "Highlight Ignore Rules" to disable highlights in the same way you can add highlights.
For example, to ignore all pings from a bot with the nickname
qAnnounce, add a new highlight ignore rule with empty rule text and a "Sender" of "qAnnounce!*".
Or, to keep a nickname variant from highlighting you, e.g.
yournick[m], add a highlight ignore rule with a "Rule" of "yournick[m]".
How do I include special characters in Highlight/Ignore rules?¶
Version 0.13.0 and newer allow escaping special characters such as "*", "?", ";", "!", and "\" by prefixing them with an additional "\".
For example, "A question\?" would match "A question?" literally.
Sender/channel/scope are similar, with "\;" turning into a literal ";", and "\!test" matching the literal channel "!test" instead of inverting the rule. "!" only needs escaped at the beginning of scope rules.
Take a look at the full Pattern matching documentation page for additional help.
How do I ignore CTCP requests?¶
Versions 0.5.2 and newer offer a "CTCP" type in the ignorelist settingspage.
If selected, the rule is parsed as follows:
hostmask [CTCPCMD [CTCPCMD ...]]
For example "* VERSION PING" would ignore VERSION and PING requests for any hostmask.
If no CTCPCMD is given, all requests are ignored.
Only global- and per network scope are supported.
Since CTCP is ignored on the coreside, "Strictness" is always permanent.
CTCP ignore is patched into quassel 0.5.0-0ubuntu1.1 for Ubuntu Karmic users.
Why does clicking on the systray icon take me to some strange buffer called something like "bartol.freenode.net"?¶
This is a known bug that needs to be fixed. But there is a workaround (Requires Quassel 0.6.0+).
First some background:
Quassel allows to show notices sent from a specific IRC server in separate buffers. This behavior is controlled by the setting "Message Redirection -> Server Notices". The default setting is here to show them in the "Status Window". Until recently quasselcore would still create a buffer called "bartol.freenode.net" and store the messages in that buffer. When the client receives such a message it redirects them to the Status Window and the buffer "bartol.freenode.net" would be hidden from all "Chat Lists". The highlighting / notification processing still triggers the activity for the original "bartol.freenode.net" though.
Enable "Message Redirection -> Server Notices -> default target". This will make those "ghost buffers" visible and you can delete them. After that disable the setting again, so that Server Notices are only displayed in the "Status Window". Since Quassel 0.6.0 Quassel will not recreate the buffer unless you have "Message Redirection -> Server Notices -> default target" enabled.
Why is the client showing the Core Setup Wizard when I've already set up my core?¶
This can happen if the core loses the configuration for its backend (database). This is more likely to happen with PostgreSQL and system updates than with SQLite.
To fix this, close the core setup wizard and disconnect the client from the core. Then from the system hosting the core, ran the setup of the backend configuration again:
sudo -u quasselcore quasselcore --configdir=/var/lib/quassel --select-backend=PostgreSQL
This will ask for the username, password, hostname, port, and database to be used with PostgreSQL. The default values are likely okay and the password would have been set when initally setting up the backend, you will need it.
Depending on your operating system and method of install, you may have to modify the above command to match with the correct user or config directory; you may not even need to `sudo -u <user>` if you are logged in as the same user that quasselcore runs as. A mention from a user on Gentoo was to use this command:
sudo -i -u quassel -- quasselcore --configdir /var/lib/quassel --select-backend PostgreSQL
Further details to each backend type can be found on the respective Wiki pages linked in the second sentence.