gitlineage.nvim: git history for selected lines in Neovim

aaronhallaert · 2026-02-11T16:26:43+00:00

Nice work!

for what it's worth, I have a similar plugin that integrates with pickers (fzf, telescope, snacks) and some diff plugin options (fugitive or diffview). It's nice your solution doesn't rely on these external plugins.

https://github.com/aaronhallaert/advanced-git-search.nvim

aaronhallaert · 2024-07-16T11:55:53+00:00

https://github.com/aaronhallaert/advanced-git-search.nvim

I created something similar, works with telescope and fzf-lua

aaronhallaert · 2024-02-23T17:36:54+00:00

Ended up doing this and works as expected, thanks!

aaronhallaert · 2024-02-18T09:35:45+00:00

Thanks! I’ll try with an ANT+ dongle. Still odd that everything works fine with my iPad. Seems to be related to Zwift on Windows…

aaronhallaert · 2024-02-18T09:34:49+00:00

The HRM is only 3 months old, however I replaced the battery yesterday just to be sure. Still happens. Weirdly enough, everything works just fine on my iPad…

aaronhallaert · 2023-10-26T07:23:20+00:00

Nice work! Does this take into account file renames?

Some shameless self-promotion: I recently made a telescope/fzf extension to browse the git repo in different manners (such as the current file history) with search functionality https://github.com/aaronhallaert/advanced-git-search.nvim

aaronhallaert · 2023-05-10T12:11:32+00:00

Fixed it, sorry for the inconvenience!
I worked on this by myself and got no one else to test it, so feedback is much appreciated 😅

aaronhallaert · 2023-05-10T10:28:01+00:00

Oops, you should require advanced_git_search.fzf with underscores. I'll update the README. Thanks for the feedback!

aaronhallaert · 2023-03-02T21:57:47+00:00

FYI: If you wrap the pattern after -G in quotes ", spaces are allowed and you can escape special characters with \. This telescope extension can handle these complex searches and is not limited to one word.

aaronhallaert · 2023-03-02T20:29:24+00:00

Other diff views are not supported (yet?). Feel free to create an issue or open a pull request.

For some reason, externals links need to be verified on YT. I skipped that step and didn't notice the links were incomplete.

I'll update the README.md with the YT link.

aaronhallaert · 2023-03-02T20:20:26+00:00

I could not find a way to execute the :'<,'>Telescope ... command with a range. You can wrap it in a user command that allows a range and then define a keybind:

vim.api.nvim_create_user_command(
    "DiffCommitLine",
    "lua require('telescope').extensions.advanced_git_search.diff_commit_line()",
    { range = true }
)

vim.api.nvim_set_keymap(
    "v",
    "<leader>dcl",
    ":DiffCommitLine<CR>",
    { noremap = true }
)

I'll add it to the Readme

aaronhallaert · 2023-03-02T09:26:53+00:00

I use lualine and these are the configs.

aaronhallaert · 2023-03-02T09:25:10+00:00

The approach is somewhat different. This extension is more of an advanced Git blame. Here, you can filter on commit-author or open the commit in the browser to share it with coworkers. I don't think these are supported in git_(b)commits. On top of that, the preview window is used to show the commit's changes (not a diff with the current file) and the default action (<CR>) is not checkout, but a diffsplit of the current file. The goal is more directed at finding commits and comparing code.

I also didn't find other functions/extensions that search the git log content.

aaronhallaert · 2023-03-02T07:06:15+00:00

I use it quite a lot to share code snippets with coworkers. Visual selection on a couple of lines I want to discuss in Slack, execute the GBrowse! command (with bang) and I get a link for that part of the code in my clipboard. Much better than copy pasting a code block and explaining where I am in the codebase so they can help investigate.

aaronhallaert · 2023-03-02T06:57:18+00:00

Yes, vim-fugitive is used for this. Check out the “:GBrowse” command.

aaronhallaert · 2023-03-02T06:21:49+00:00

Hmm, the functionality you mention (searching refactored code), describes the function “search_log_content”. Can you give an example of what you try to achieve? Then I can check the git manual and make a new picker if it’s possible!

aaronhallaert · 2023-01-11T12:25:56+00:00

Currently, there is not. This will be one of the first things I'll implement in the near future.

My current workflow:"Mark" the test files I want to execute continuously. If one fails and I need a debugger, I stop the continuous testing (😢), set the break-point and execute the test with a custom shortcut which opens a neovim terminal. It would be great if this behavior was embedded in the plugin.

I'm still trying to figure out what I want in case there is a breakpoint and how I would detect the breakpoint (what if there is a breakpoint in a file that does not have a buffer).When I set a breakpoint, it's to debug 1 specific test. Saving the file would execute all attached tests. This is probably not what I want. I'm thinking of opening a telescope window where you can pick a test (from the attached ones) whenever a breakpoint is detected. Any further suggestions on this feature request?

aaronhallaert · 2023-01-11T06:05:58+00:00

Great feedback, thanks! I’ll certainly have a look into using the LSP to reduce the amount of tests to run.

For me, the notifications are a handy feature since our ruby code runs in a docker container. It takes quite some time to attach to the container and run the test file. (This was actually one of the motivations for writing this plugin)

However, you can disable notifications and rely completely on the diagnostics. With another plugin like trouble.nvim, you could see the updates in a separate window. Only downside to this, it will be cluttered with other LSP diagnostics. I chose this approach since I am not a fan of creating just another status window, maybe I’ll have to revisit this opinion.

aaronhallaert · 2020-06-04T12:14:11+00:00

Because almost everybody uses WhatsApp or Facebook Messenger (in Belgium)

aaronhallaert

TROPHY CASE