public
/
nixpkgs
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity
nixpkgs/pkgs/applications/networking/irc/weechat/scripts/default.nix

24 lines
613 B
Nix
Raw Normal View History

weechatScripts.multiline: init at 0.6.3
2021-02-04 04:52:09 -08:00
{ callPackage, luaPackages, perlPackages, python3Packages }:
weechat: 2.1 -> 2.2; improve package configuration This aims to make the `weechat` package even more configurable. It allows to specify scripts and commands using the `configure` function inside a `weechat.override` expression. The package can be configured like this: ``` with import <nixpkgs> { }; weechat.override { plugins = { availablePlugins, ... }: { plugins = builtins.attrValues availablePlugins; init = '' /set foo bar /server add freenode chat.freenode.org ''; scripts = [ "/path/to/script.py" ]; }; } ``` All commands are passed to `weechat --run-command "/set foo bar;/server ..."`. The `plugins' attribute is not necessarily required anymore, if it's sufficient to add `init' commands, the `plugins' will be `builtins.attrValues availablePlugins' by default. Additionally the result contains `weechat` and `weechat-headless` (introduced in WeeChat 2.1) now.
2018-09-05 08:01:45 -07:00
{
weechatScripts.colorize_nicks: init at 27
2019-07-08 03:32:42 -07:00
colorize_nicks = callPackage ./colorize_nicks { };
weechatScripts.multiline: init at 0.6.3
2021-02-04 04:52:09 -08:00
multiline = callPackage ./multiline {
inherit (perlPackages) PodParser;
};
weechat: 2.1 -> 2.2; improve package configuration This aims to make the `weechat` package even more configurable. It allows to specify scripts and commands using the `configure` function inside a `weechat.override` expression. The package can be configured like this: ``` with import <nixpkgs> { }; weechat.override { plugins = { availablePlugins, ... }: { plugins = builtins.attrValues availablePlugins; init = '' /set foo bar /server add freenode chat.freenode.org ''; scripts = [ "/path/to/script.py" ]; }; } ``` All commands are passed to `weechat --run-command "/set foo bar;/server ..."`. The `plugins' attribute is not necessarily required anymore, if it's sufficient to add `init' commands, the `plugins' will be `builtins.attrValues availablePlugins' by default. Additionally the result contains `weechat` and `weechat-headless` (introduced in WeeChat 2.1) now.
2018-09-05 08:01:45 -07:00
weechat-matrix-bridge = callPackage ./weechat-matrix-bridge {
weechat-matrix-bridge: use luaffi from luaPackages
2019-08-24 03:01:01 -07:00
inherit (luaPackages) cjson luaffi;
weechat: 2.1 -> 2.2; improve package configuration This aims to make the `weechat` package even more configurable. It allows to specify scripts and commands using the `configure` function inside a `weechat.override` expression. The package can be configured like this: ``` with import <nixpkgs> { }; weechat.override { plugins = { availablePlugins, ... }: { plugins = builtins.attrValues availablePlugins; init = '' /set foo bar /server add freenode chat.freenode.org ''; scripts = [ "/path/to/script.py" ]; }; } ``` All commands are passed to `weechat --run-command "/set foo bar;/server ..."`. The `plugins' attribute is not necessarily required anymore, if it's sufficient to add `init' commands, the `plugins' will be `builtins.attrValues availablePlugins' by default. Additionally the result contains `weechat` and `weechat-headless` (introduced in WeeChat 2.1) now.
2018-09-05 08:01:45 -07:00
};
weechatScripts.wee-slack: init at 2.1.1
2018-09-06 06:10:37 -07:00
weechatScripts.weechat-matrix: init at unstable-2019-11-10
2019-11-15 06:20:38 -08:00
weechat-matrix = python3Packages.callPackage ./weechat-matrix { };
weechat-notify-send: init at 0.9
2020-03-17 08:05:41 -07:00
weechat-notify-send = python3Packages.callPackage ./weechat-notify-send { };
weechat: build with python3 by default WeeChat also supports Python3 for scripts which should be preferred as CPython2 is about to get EOLed soon: https://weechat.org/scripts/python3/
2019-09-04 09:13:50 -07:00
wee-slack = callPackage ./wee-slack { };
weechatScripts.weechat-autosort: init at unstable-2018-01-11 (#51729) Helpful weechat script to automatically keep buffers sorted. Can be activated like this: ``` nix weechat.override { configure = { ... }: { scripts = [ weechatScripts.weechat-autosort ]; }; } ```
2018-12-08 08:45:18 -08:00
weechat-autosort = callPackage ./weechat-autosort { };
weechatScripts.weechat-otr: init at 1.9.2
2019-06-05 14:47:43 -07:00
weechat: build with python3 by default WeeChat also supports Python3 for scripts which should be preferred as CPython2 is about to get EOLed soon: https://weechat.org/scripts/python3/
2019-09-04 09:13:50 -07:00
weechat-otr = callPackage ./weechat-otr { };
weechat: 2.1 -> 2.2; improve package configuration This aims to make the `weechat` package even more configurable. It allows to specify scripts and commands using the `configure` function inside a `weechat.override` expression. The package can be configured like this: ``` with import <nixpkgs> { }; weechat.override { plugins = { availablePlugins, ... }: { plugins = builtins.attrValues availablePlugins; init = '' /set foo bar /server add freenode chat.freenode.org ''; scripts = [ "/path/to/script.py" ]; }; } ``` All commands are passed to `weechat --run-command "/set foo bar;/server ..."`. The `plugins' attribute is not necessarily required anymore, if it's sufficient to add `init' commands, the `plugins' will be `builtins.attrValues availablePlugins' by default. Additionally the result contains `weechat` and `weechat-headless` (introduced in WeeChat 2.1) now.
2018-09-05 08:01:45 -07:00
}