1
0
Fork 0
mirror of https://github.com/nix-community/nixvim.git synced 2025-11-08 19:46:06 +01:00
nixvim/plugins/by-name/langmapper/default.nix
Yury Shvedov d60696f62d plugins/langmapper: init module
Change-Id: I1caf76d5a6bdd7b1bb9fecfb142a3af1f0b00bd6
2025-10-15 14:30:14 +00:00

52 lines
1.5 KiB
Nix

{
lib,
...
}:
let
inherit (lib)
mkEnableOption
mkIf
mkOption
stringToCharacters
types
;
inherit (lib.nixvim.lua) toLua;
in
lib.nixvim.plugins.mkNeovimPlugin {
name = "langmapper";
package = "langmapper-nvim";
description = "A plugin that makes Neovim more friendly to non-English input methods";
maintainers = [ lib.maintainers.shved ];
settingsExample = {
automapping_modes = stringToCharacters "invxs";
map_add_ctrl = false;
};
extraOptions = {
automapping = {
enable = mkEnableOption "calling `automapping` at the end of `init.lua`" // {
default = true;
};
argument = mkOption {
description = "An argument to `automapping` call";
type = with types; either rawLua (attrsOf anything);
default = {
global = true;
buffer = false;
};
};
};
};
extraConfig = cfg: {
# The plugin documentation says that if we need to handle built-in and vim
# script mappings, we should call this at the very end of `init.lua`. On the
# other hand it says that we have to call `setup` at the very beginning of
# plugin list initialisation. But I believe that this is enough to call this
# at very end of `init.lua` to cover the issues produced by calling `setup`
# of this plugin at the middle of plugins list
extraConfigLuaPost = mkIf cfg.automapping.enable ''
require("langmapper").automapping(${toLua cfg.automapping.argument})
'';
};
}