From: John K. <jo...@kl...> - 2003-01-20 13:24:37
|
[ Copying Daniel, the author of the patch, and also the new = tkdiff-discuss list at sourceforge. ] Hi Dorothy, Good to hear from you! > Glad to hear you're taking on tkdiff again. Here's a patch someone > sent me for the version I included with tkcvs 7.1. The first part > fixes a boneheaded mistake I made, and the rest of the patch is > something that sounds like a good idea, although I haven't really > studied it yet. I'm in the middle of moving all my stuff onto a > new computer. Hmmmmmmm. Not sure what to do... Reasons: 1. Your version is a heavily-modified 3.09. 2. There's already a 3.10-in-progress in CVS (that is, a differently-modified 3.09). Any chance you'd be willing to work with us to get the relevant portions = of your version into ours, where they're appropriate? :-) What exactly did = you do to create yours? Anyway, for ignoring whitespace, the generally-accepted approach is to = use "diff" options when you invoke tkdiff. Anything tkdiff doesn't = recognize is passed on to diff, and so one usually accomplishes this particular thing = by doing something like: tkdiff -t -w firstfile secondfile The -t and -w are passed to diff, and tell it to ignore whitespace. We made a conscious decision, way back, to forgo adding new built-in = options when there already exist diff options (that can be passed through) to accomplish the same thing. Note further that under Preferences > = General, you can actually set the "-t -w" persistently, so that access to a = command line isn't required. Good to hear from you... Hope all is well! John |