[tlamponi]

No, he uses commit messages as log of his thoughts, and commits need to have changes, thus each "log only" commit deletes or adds those same whitespaces in a never ending cycle.

In between you find some actual code changes (with also long commit messages).

It's not that he's finished - I hardly guess so because he complains that he'd need 10 years of time to polish everything out perfectly (in his opinion) and he only has one - it's just his style for a log book...

[abstractcontrol]

I can't actually program all the time. Sometimes I need to study machine learning or think about design. During those times I use commits much like journal entries.

I actually keep a separate journal and sometimes paste from it. I've been using LibreOffice Writer for it and decided to drop it recently because it would take so long to save a file - like 5s or more. Around every 3 month I'd fill in about 1000 pages of it and it was forcing me to move to a new file every time that happened. Now I just use VS Code for this sort of thing. Raw text is the best after all, but it is too bad I can't paste images into the journal anymore.

[rhencke]

If you do wish to use commits to simply journal your thoughts, and would like to do so without this requiring code or file changes, you may find the --allow-empty option useful when committing.

This allows you to create a new commit, even if no files have changed.

[jdblair]

Or, write your journal entries to a file and commit that? That's what I do. Most of my personal projects have a "notes.txt" at the top level for this purpose. Sometimes I just need to write freeform about the problem I'm trying to solve, from different angles, to work out my strategy. Sometimes I just write the despair that I'll never figure something out.

[abstractcontrol]

How would one enable this in Visual Studio?

[rhencke]

Unfortunately, as far as I am aware, Visual Studio does not directly expose this option.

However, it is quite likely you can use Visual Studio's "External Tools" feature to be able to achieve this. (https://msdn.microsoft.com/en-us/library/76712d27.aspx)

You could set up an external tool that did something like the following:

Title: Commit with Selected Text as Message

Command: path\to\git.exe

Initial Directory: $(SolutionDir)

Arguments: commit --allow-empty -m "$(CurText)"

This will allow you to create an empty commit, with the selected text becoming the commit message. (Just bear in mind if you have any files staged, they will be committed as well)

I unfortunately do not have Visual Studio currently installed, so please take the above as a rough sketch, and my apologies if it doesn't work as is. But, I hope it is of use to you.

[Bromskloss]

> commits need to have changes

Ah, yes, I remember wanting to be able commit the identity transformation (_i.e._ no change) at some point. I don't remember why. It might have been a matter of principle.

PS: I just learned about the `--allow-empty` flag. [0] I'm happy again.

[0] https://git-scm.com/docs/git-commit#git-commit---allow-empty

[jacobush]

Oh; I missed the back and forth.

But he said he was done, because he no more time for language design, and he must study AI now.