Hello, I'm attempting to add Unified diff support for the changes --interactive command and I'm running into a little trouble. I am using WhatsNew.lhs as a model. In WhatsNew, when displaying a patch in the normal format it calls 'printPatch ch'. But for a Unified diff, it calls 'contextualPrintPatch s ch'.
I'm trying to figure out why unified diffs need a repository slurpy, as in, why are they contextual? I don't know much at all about patch theory and the like, but here is my guess: Normal patches show hunks of changes that can be moved around and whatnot. But with a Unified diff, it is displaying how a file will be changed by a given patch. So it needs the slurpy to see the entire file. Is that at all close to the target? When I attempt to do a contextualPrintPatch on a patch it displays some of the text in unified format and then crashes with: fromJust error at PatchViewing.lhs:65 compiled 20:30:10 Dec 18 2005 But what I am more worried about is, so Unified diffs even make sense for this type of thing? If my first assumption mentioned above is correct (which it very well may not be) Unified diffs currently only work when you are asking for a Unified diff of a repository with all patches applied, which is why it works for WhatsNew and Unrevert. I hope I made myself at least partially clear. Clear enough for someone to tell me if Unified diffs are currently possible for looking at any given set of patches, at least :P -- Zachary P. Landau <[EMAIL PROTECTED]> _______________________________________________ darcs-devel mailing list [email protected] http://www.abridgegame.org/cgi-bin/mailman/listinfo/darcs-devel
