Johannes Altmanninger
Johannes Altmanninger
Ok I exposed it, which conveniently gives us an obvious place to document the behavior. I'm not against making it an option but I can't think of a use case...
Right. When adding text to a zero-byte file we always write it with a newline (same as before) because that's what we think is the correct style. Not sure if...
> I realized that this patch makes anyone who is using the truncate workaround truncate too much. My hope is that those folks already use Git to catch this error....
As one should have expected, this has some issues. Specifically, when the file is missing a final newline and `:format` would add one, that added newline will not be written...
I had thought that there was a shortcoming in `` and `` which would give a good motivation for this. However, I'm struggling to find such a scenario, maybe something...
meh, this patch breaks the default readline binding of `` (move one character to the right) :(
`` is already strictly better so I don't see the motivation
I wrote a script on top of `git-revise` to support a similar workflow: [git-branchless](https://git.sr.ht/~krobelus/git-branchless)
[git autofixup](https://github.com/torbiak/git-autofixup) is another tool that's very similar to `git absorb`
this broke sequences like `pick + fixup + pick + squash` which is fixed now. Still it has the potential to break scripts that override GIT_EDITOR to edit the commit...