Currently, all logs for a file are processed at start-up. This will probably lead to longer startup time on files with many commits.

Use git log -n 5 to get the first 5 logs and process the rest in the background.
See https://www.git-scm.com/docs/git-log#_commit_limiting for more parameters.

Five is used in the above command as an example. Some testing should be done to see how many log entries can be processed before a delay is noticed.

Allow the up/down arrow keys to move the 'selection' of the commit list up/down (respectively).

This should work for the entire program (at this time) - so the focus doesn't need to be on the commit list.

Currently, it appears that the List widget (

• investigate List widget to see why the label limit appears to be 35
• see if that can be changed
• if not see if there is a different widget that should be used for the list
• if there's nothing to be done add a comment to the code about the situations

Bonus:
Explore opening up a ticket with the Fyne project to discuss the reason for the limit.

Currently, the tool needs to be run in the root directory of the git repository of the file that is being examined. The tool should be able to determine the 'root' of the git repository.

The window opens up vertically minimized and the width of its current contents.

The window should have a suitable horizontal and vertical size - enabling scroll bars when needed.

This may also cause the rendering issue when switching between commits.

There should be a way to all the selection of two commits and show the diff between them. This will be the output of the following git command:

$ git diff HEAD^^ HEAD main.c
$ git diff HEAD^^..HEAD -- main.c
$ git diff HEAD~2 HEAD -- main.c

Currently, the tool shows the state of the file at that commit. It would be helpful to have a toggle button showing the change from the previous commit to the current one.

The first commit would show the file itself since nothing existed before that commit.