git-blameall VS difftastic

Thanks, I knew about -committerdate but not that you can set it as default sort, super useful. A few notes...

1. git columns gets real confusing if you have more data than fits the screen and you need to scroll. Numbers would help...

2. git maintenance sounds great but since I do a lot of rebases and stuff, I am worried: does this lose loose objects faster than gc would? I see gc is disabled but it's not clear.

3. Regarding git blame a little known but super useful script is https://github.com/gnddev/git-blameall . (I mean, it's so little known I myself needed to port it to Python 3 and I am no Python developer by any stretch.)

The author mentions git blame which is indeed an important tool but in more complex codebases it's entire possible the original introduction would require several steps because the code was refactored since. For this, git blameall is a wonderful and almost completely unknown utility. https://github.com/gnddev/git-blameall Yours truly did a quick Python 3 port this January, mostly using the automated toolset for it and the author, much to my surprise, committed it in a week despite the last commit was in 2013. So the project is not dead :)

Does anyone know whether git blameall https://github.com/ddev/git-blameall is easy to do with Fossil? It's a lesser known tool but I found it incredibly useful (hence why I did the Python 3, mostly automated tools but still).

i want a diff tool that shows me exactly which tokens have changed, and which haven't, regardless of how they are laid out.

These already exist: https://github.com/Wilfred/difftastic

when we get that, then we should get even less merge conflicts.

Counterintuitively, that is not the case. AST-merge is a much, much, much, much, much harder problem than AST-diff.

https://github.com/Wilfred/difftastic?tab=readme-ov-file#can...

The fact that diffs can be used to drive a 3-way merge is in fact an accidental property that arises due to the sheer crudeness of the diff format. As soon as you start using more-sophisticated diff formats, solutions to "the diff problem" no longer lead directly to solutions to "the merge problem".

Yes there is an `—-override` option you can use to specify the language in which a file should be parsed.

https://github.com/Wilfred/difftastic/blob/master/CHANGELOG....

Use the fantastic difftastic instead of git's diff. https://difftastic.wilfred.me.uk/

  [alias]

difftastic provides similar capabilities in a free tool based on treesitter

difftastic? https://github.com/Wilfred/difftastic

If you're looking for a VS Code extension or a GitHub app, check out https://semanticdiff.com/. I'm a co-founder of this project.

If you prefer a CLI tool, check out https://github.com/Wilfred/difftastic. It supports more languages, but doesn't recognize when code has been replaced by an equivalent version ("invariances"). So it will show some changes (e.g. replacing a character in a string with an escape sequence) even though they are technically equivalent.

Shameless plug: I've written difftastic[1], a tool that builds ASTs and then does a structural diff of them. You can use it with git too.

It's an incredibly hard problem though, both from a computational complexity point of view, and trying to build a comprehensible UI once you've done the structural AST diff.

[1]: https://github.com/wilfred/difftastic

There is a diff tool called difftastic: https://github.com/Wilfred/difftastic

The idea is that it does not show diff based on text change, but on syntastic meaning. For that, it uses tree-sitter.

I think it still shows the trailing comma in the situation as shown in the article, but it's quite different experience than the standard text based diff.