ftilmann

I also use Overleaf quite a lot, so could be interesting but I am not sure what exactly you are proposing. Also not sure if it is really something latexdiff...

Indeed, it would be very cool to be able to do a git pull from overleaf and have the comments added to the tex in a way that they are...

> I am thinking of implementing a feature to add or suppress markup with special latexdiff comment tags inside the new file, which would make it easier to implement what...

Thanks for the report. According to my assessment, this is difficult to fix without causing problems in other situations in a general way. As marked-up versions are usually for internal...

latexdiff should now be more 'polite' about respecting definitions of graphics and line markup in the custom preamble. Please have a try. There are some heuristics in there which I...

Not a real solution, but with `--graphics-markup=NONE` \DIFaddbegin and \DIFaddend turn into null commands in the standard markup style; then the longtable environment is no longer confused by the presence...

Thank you for your comment. Deleting lines marked with %DIFAUXCMD is generally described behaviour but in this situation obviously doesn't do the right thing, as unlike the original design principles...

Thanks for reporting. I just had a quick look at the diff listing of the commit https://github.com/acidanthera/OpenCorePkg/pull/537/commits/140f35529a908c8b67ac4181ec2aa78b5f964c38 and I can see there are many changes involving \item lists, which is...

As you suspected this is an edge case that will be rather tricky to fix. A possible work-around is to change either the inner or the outer $..$ pair to...

I assigned "Low" priority to a fix as it would be relatively complicated for what I feel is a niche case, and it can be avoided by also using the...