Weechat VS fish-shell

WeeChat[0] with Bitlbee[1] supports a metric assload of services, albeit by pretending they're IRC (which does work - I spent years in weechat/irssi with bitlbee talking to various people on disparate services.)

Or if you're just after Telegram/WhatsApp, nchat[2] is ok (I can vouch for the Telegram half only.)

[0] https://weechat.org

[1] https://wiki.bitlbee.org

[2] https://github.com/d99kris/nchat

And UnrealIRCD still rocks. For a quick-and-dirty setup I've deploy ng-ircd but Unreal has always been my go-to for anything serious. If nothing else it can be useful as a backup or internal platform during the rare events that Slack or Discord are having an incident. The common complaint is a lack of channel back-log but it can be front-ended with TheLounge [1] or Convos [2]. I personally prefer to handle that with gnu screen or tmux and WeeChat [3].

[1] - https://github.com/thelounge

[2] - https://github.com/convos-chat/convos/

[3] - https://weechat.org/

The link posted was to the dev blog, the actual website can be found at [0]. On the blog, the right side menu under "Links" also links to the website.

[0] - https://weechat.org/

I’m afraid you’re in the wrong subreddit. This subreddit is dedicated to WeeChat the IRC client., not the proprietary messaging app built by Tencent.

First off, grab yourself an IRC client. On their connection info page Hackint has information for both WeeChat and Hexchat, but you could use any IRC client.

That's nothing to do with weechat? https://weechat.org/

Gajim is for XMPP. For IRC you need Hexchat or Weechat or something like that.

I am not familiar with HexChat but you might consider using a different IRC client that allows you to silence anything/everything by default and only alert you on specific keywords you are interested in. If you like command line tools, consider trying out WeeChat IRC client [1] It is very customizable and there are many scripts for it.

[1] - https://weechat.org/

Reminds of the note at the bottom of Fish's releases. It's there because the build system cannot determine the current version for some reason. Hopefully that will go away now that they have switched to a different language / build system. The custom tarball is used by Arch Linux at the very least.

https://github.com/fish-shell/fish-shell/releases/tag/3.7.1

https://github.com/fish-shell/fish-shell/issues/7772#issueco...

https://gitlab.archlinux.org/archlinux/packaging/packages/fi...

A recent practical example of the former: the fish shell re-wrote incrementally from C++ to Rust, and is almost finished https://github.com/fish-shell/fish-shell/discussions/10123

An example of the latter: c2rust, which is a work in progress but is very impressive https://github.com/immunant/c2rust

It currently translates into unsafe Rust, but the strategy is to separate the "compile C to unsafe Rust" steps and the "compile unsafe Rust to safe Rust" steps. As I see it, as it makes the overall task simpler, allows for more user freedom, and makes the latter potentially useful even for non-transpiled code. https://immunant.com/blog/2023/03/lifting/

And this discussion from November has an update on the progress: https://github.com/fish-shell/fish-shell/discussions/10123

We're using bash as our terminal shell for now (it is standard in many distros) but it is not the only one out there. If you want to test out zsh, fish or oh-my-zsh, you will see that there are a few differences and the features are usually the main differentiator. Try that, poke around.

They have a variety of reasons to move to rust, as outlined in their original rust discussion[1]. Mostly around finding other contributors, and adding an async/parallel mode they're comfortable with.

[1] https://github.com/fish-shell/fish-shell/pull/9512