this post was submitted on 22 Mar 2024
116 points (99.2% liked)

Programming

17432 readers
229 users here now

Welcome to the main community in programming.dev! Feel free to post anything relating to programming here!

Cross posting is strongly encouraged in the instance. If you feel your post or another person's post makes sense in another community cross post into it.

Hope you enjoy the instance!

Rules

Rules

  • Follow the programming.dev instance rules
  • Keep content related to programming in some way
  • If you're posting long videos try to add in some form of tldr for those who don't want to watch videos

Wormhole

Follow the wormhole through a path of communities !webdev@programming.dev



founded 1 year ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
[–] astrsk@kbin.social -1 points 8 months ago (3 children)

I didn’t get a chance to look too deep into it, while it looks great for human reading in a terminal, can I just as easily output the diff to a patch file like I do often with ‘git diff [commit] [commit] > patch.txt and git apply it?

[–] ranting_sandfish@mander.xyz 15 points 8 months ago

Doesn't look like it, from their docs:

Non-goals

Patching. Difftastic output is intended for human consumption, and it does not generate patches that you can apply later. Use diff if you need a patch.

Since the diffs are tree-sitter based, it's interesting to think about what a tree-sitter based patch would look like. Probably wouldn't double as a human and computer friendly format like normals diffs. I suppose that you could create patches that are more robust to the source code changing since it wouldn't care about linebreaks and maybe you could have it so it doesn't care if you move code around since you could have it so its going by e.g. what the parent function is and not the line number. I gotta wonder how useful that actually is though.

[–] MonkderZweite@feddit.ch 1 points 8 months ago* (last edited 8 months ago)

Use diff for that?