Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Options to customize log output? #42

Open
mgeier opened this issue Sep 3, 2012 · 2 comments
Open

Options to customize log output? #42

mgeier opened this issue Sep 3, 2012 · 2 comments
Labels
feature request Functionality that is not yet possible
Milestone

Comments

@mgeier
Copy link

mgeier commented Sep 3, 2012

Is it possible to change the appearance of the log, for example

  • show (shortened) SHA1 to the left of the commit message (instead of far right) or
  • show author/committer immediately after the commit message (without space, unaligned)?

Could this be done with a vim variable (or several variables)?

@gregsexton
Copy link
Owner

Hi,

Currently, no it's not possible. If I remember correctly at least some parts of the code makes assumptions about the log output. It may not be that small a change. Is this just a personal preference or do you have a bigger reason for wanting this change?

Thanks,

Greg

@mgeier
Copy link
Author

mgeier commented Sep 18, 2012

Thanks for the answer.
No, I don't have a bigger reason, I guess. The problem is only that with columns=80 very often the SHA1 is not visible.
I don't need it very often, so it's not that important, I just thought there may be some variable to manipulate the git log --format=... option, but I guess there may be problems with the syntax highlighting and the alignment in columns.

My personal preference would be to get rid of the column alignment (and the empty space that comes with that and change the format from

*  My commit message                                                    5 days ago    Firstname Lastname  [ebf2bdc]

to

*  [ebf2bdc]  My commit message    5 days ago    Firstname Lastname

... but of course other people will have other preferenes.

BTW, gitv is great and I use it nearly every day!

@rbong rbong added this to the 1.5.2 milestone Apr 14, 2017
@rbong rbong added the feature request Functionality that is not yet possible label Jun 9, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feature request Functionality that is not yet possible
Projects
None yet
Development

No branches or pull requests

3 participants