You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Greetings, I would like to be able to the commit history for a specific line in a file. The filepath and line number would be retrieved from my text editor before it called the command. I discovered the --filter command line option, but unfortunately that does not do what I want - it only lets you specify filepaths. What I essentially wish to do is filter the commits based on the output of git log -L(line number),+1:'path/to/file.txt'.
Is there a way I can do this currently? If not, could that capability be added?
I think the most flexible and useful solution would be a generic way to pass git log output into lazygit to filter by. That would cover my usecase, and many other usecases as well. For my purposes, it could be a flag with a git log command, or it could accept it through stdin.
Thanks for making lazygit, it's an absolutely phenomenal tool. Line history is the only thing I miss from GitLens.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Greetings, I would like to be able to the commit history for a specific line in a file. The filepath and line number would be retrieved from my text editor before it called the command. I discovered the
--filter
command line option, but unfortunately that does not do what I want - it only lets you specify filepaths. What I essentially wish to do is filter the commits based on the output ofgit log -L(line number),+1:'path/to/file.txt'
.Is there a way I can do this currently? If not, could that capability be added?
I think the most flexible and useful solution would be a generic way to pass
git log
output into lazygit to filter by. That would cover my usecase, and many other usecases as well. For my purposes, it could be a flag with agit log
command, or it could accept it through stdin.Thanks for making lazygit, it's an absolutely phenomenal tool. Line history is the only thing I miss from GitLens.
Beta Was this translation helpful? Give feedback.
All reactions