Skip to main content

X-Chat power-user upload

xchat (2.8.8-7ubuntu2) raring; urgency=low

  * Optimise default settings for efficient chatting
    + Make tab completion by default use last-used order, not alphabetical.
      This way for example if one is chatting with cjwatson, typing
      "cj" will complete to cjwatson and not cjohnston.
      Manual migration: ~/.xchat/xchat.conf: completion_sort = 1
    + Do not focus channel upon entering, as that clears highlights when using a znc proxy.
      To be honest, there should be a distinction between manually joining
      new channels & auto-joining. (LP: #189222)
      Manual migration: ~/.xchat/xchat.conf: tab_new_to_front = 0
    + Do not clear buffer with Ctrl-L shortcut. (LP: #304477)
      That shortcut is dominated by web-browsers changing URLs and causes
      context loss if the focus was accidently left on xchat.
  * Fix ftbfs, should link against gmodule.
  * Add xchat-indicator to recommends. (LP: #1048335)
  * Include svg icon (LP: #840673)
 -- Dmitrijs Ledkovs <>   Sun, 24 Feb 2013 23:03:52 +0000

This upload should make xchat more pleasant to work with for avid irc chatters. Note that since xchat doesn't track what is default vs custom set, one may want to adjust to the new default settings:
  • tab_new_to_front = 0
  • completion_sort =1
The first one prevents focusing channels upon (auto-)joining. This prevents loosing highlights and backscroll marker on high velocity channels as well as when using an irc proxy like ZNC.

The second one makes tab completion to prefer recently used nicks, over alphabetically sorted once. In practice this means highlighting the wrong people less.

I hope you enjoy this upload. It seems like these fixes also affect hexchat... I do wonder if that one should be uploaded into ubuntu/debian. Duplicate code/bugs for some parts...


  1. This sounds awesome!

    What about xchat-gnome? Does it support the same settings?

    1. I am not sure if xchat-gnome support same settings, it may be missing UI to set them. I personally dislike xchat-gnome as being less stable and less feature-full than xchat.


Post a Comment

Popular posts from this blog

How to disable TLS 1.0 and TLS 1.1 on Ubuntu

Example of website that only supports TLS v1.0, which is rejected by the client Overivew TLS v1.3 is the latest standard for secure communication over the internet. It is widely supported by desktops, servers and mobile phones. Recently Ubuntu 18.04 LTS received OpenSSL 1.1.1 update bringing the ability to potentially establish TLS v1.3 connections on the latest Ubuntu LTS release. Qualys SSL Labs Pulse report shows more than 15% adoption of TLS v1.3. It really is time to migrate from TLS v1.0 and TLS v1.1. As announced on the 15th of October 2018 Apple , Google , and Microsoft will disable TLS v1.0 and TLS v1.1 support by default and thus require TLS v1.2 to be supported by all clients and servers. Similarly, Ubuntu 20.04 LTS will also require TLS v1.2 as the minimum TLS version as well. To prepare for the move to TLS v1.2, it is a good idea to disable TLS v1.0 and TLS v1.1 on your local systems and start observing and reporting any websites, systems and applications that

Ubuntu 23.10 significantly reduces the installed kernel footprint

Photo by Pixabay Ubuntu systems typically have up to 3 kernels installed, before they are auto-removed by apt on classic installs. Historically the installation was optimized for metered download size only. However, kernel size growth and usage no longer warrant such optimizations. During the 23.10 Mantic Minatour cycle, I led a coordinated effort across multiple teams to implement lots of optimizations that together achieved unprecedented install footprint improvements. Given a typical install of 3 generic kernel ABIs in the default configuration on a regular-sized VM (2 CPU cores 8GB of RAM) the following metrics are achieved in Ubuntu 23.10 versus Ubuntu 22.04 LTS: 2x less disk space used (1,417MB vs 2,940MB, including initrd) 3x less peak RAM usage for the initrd boot (68MB vs 204MB) 0.5x increase in download size (949MB vs 600MB) 2.5x faster initrd generation (4.5s vs 11.3s) approximately the same total time (103s vs 98s, hardware dependent) For minimal cloud images that do not in

Ubuntu Livepatch service now supports over 60 different kernels

Linux kernel getting a livepatch whilst running a marathon. Generated with AI. Livepatch service eliminates the need for unplanned maintenance windows for high and critical severity kernel vulnerabilities by patching the Linux kernel while the system runs. Originally the service launched in 2016 with just a single kernel flavour supported. Over the years, additional kernels were added: new LTS releases, ESM kernels, Public Cloud kernels, and most recently HWE kernels too. Recently livepatch support was expanded for FIPS compliant kernels, Public cloud FIPS compliant kernels, and as well IBM Z (mainframe) kernels. Bringing the total of kernel flavours support to over 60 distinct kernel flavours supported in parallel. The table of supported kernels in the documentation lists the supported kernel flavours ABIs, the duration of individual build's support window, supported architectures, and the Ubuntu release. This work was only possible thanks to the collaboration with the Ubuntu C