Skip to content

plugins/gitlineage: init#4191

Open
carl0xs wants to merge 1 commit into
nix-community:mainfrom
carl0xs:main
Open

plugins/gitlineage: init#4191
carl0xs wants to merge 1 commit into
nix-community:mainfrom
carl0xs:main

Conversation

@carl0xs
Copy link
Copy Markdown
Contributor

@carl0xs carl0xs commented Feb 6, 2026

Add gitlineage.nvim, a plugin for view git history for selected lines.

Copy link
Copy Markdown
Member

@GaetanLepage GaetanLepage left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for the contribution.

If the plugin is not yet packaged in nixpkgs, then you need to add it there first (nix run .#vimPluginsUpdater -- add LionyxML/gitlineage.nvim).

@carl0xs carl0xs force-pushed the main branch 2 times, most recently from b5a0a1c to 65f2917 Compare April 8, 2026 17:10
Copy link
Copy Markdown
Member

@GaetanLepage GaetanLepage left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This should fix it! Also, please squash your commits into a single one:
plugins/gitlineage: init

Comment thread plugins/by-name/gitlineage/default.nix Outdated
Copy link
Copy Markdown
Member

@GaetanLepage GaetanLepage left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

You can now rebase on main and remove the change to flake.lock.

Comment on lines +17 to +42
settingsOptions = {
split = defaultNullOpts.mkStr "auto" ''
Where the git lineage window should open.
Accepts "vertical", "horizontal", or "auto".
'';

keymap = defaultNullOpts.mkStr "<leader>gl" ''
Default keymap for opening the git lineage window.
Set to `null` to disable.
'';

keys =
defaultNullOpts.mkAttrsOf (types.nullOr types.str)
{
close = "q";
next_commit = "]c";
prev_commit = "[c";
yank_commit = "yc";
open_diff = "<CR>";
}
''
Keymaps inside the git lineage window.
Set individual entries to `null` to disable.
'';
};

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Now, we tend to avoid explicitly declaring settingsOptions. The settings option is already freeform by default, so it accepts arbitrary values.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants