Activity for tkdiff
-
michael-m committed [r209] on Code
grammar (of all things)
-
Please update copyright info in README.txt
-
Revised License information has been incorporated As promised, the update to remove the incorrect Mailing address for FSF, in favor of their URL has been committed, staged to take effect on whatever next operation (fix/release) will occur.
-
tkdiff 5.7 does not work with macos tcl-tk (8.5)
-
Apologies for the delay in finalizing the disposition of this Ticket As it turns out, not 24 hours earlier, V5.7 had been released with just such a README disclaimer for the Mac platform; but perhaps not as strongly worded as it should have been. As of V6.0 (strangely enough, again released just yesterday), a far more declarative statement to NOT USE that platforms "included" Tcl/Tk 8.5 offering was provided, with instructions on where to obtain a working replacement. We can only hope that Apple...
-
update of GNU license info
-
Andreas Metzler posted a comment on ticket #100
No worries, this is a beautification fix. ;-) According to https://www.fsf.org/about/contact/ the FSF indeed is no longer located at Temple Place.
-
Official TkDiff Version 6.0 is released
-
Original issue has been addressed via new Release (Version 6.0) Unfortunately the recently appended request arrived too late to be included, and will be addressed shortly, but staged for the NEXT release (whenever that may occur). Small question however - is the former Snail-Mail address INCORRECT or simply no longer en' vogue?
-
Invalid multibyte or wide char in test file causes crash with tk9.0
-
Issue has been addressed via new release (Version 6.0)
-
Not compatible with tk 9.0
-
Issue has been addressed via new release (Version 6.0)
-
Official TkDiff Version 6.0 is released
-
tkdiff released /tkdiff/6.0/tkdiff-6-0.zip
-
-
reorganized hID scheduling logic for Ratcliff inlining
-
Could you please update the FSF address (URL instead of outdated postal one) as per adjusted patch? (LICENSE.txt refreshed from https://www.gnu.org/licenses/old-licenses/gpl-2.0.txt )
-
-
... misspecifed packing option (+ unrelate tweaks)
-
-
-
-
access to topical Help directly from the newDiff Dialog
-
prevent L/R mis-alignments of OCCASIONAL Chg hunks
-
Primarily to support TclTk 9.0 (and compensate for lost V8.x.x deprecations)
-
Invalid multibyte or wide char in test file causes crash with tk9.0
-
Sadly, that document fails to describe how things GOT that way, only what one should do once it does. After a great deal of hunting, it was discovered that something called an encoding "profile" was what is NEW in V9.0.x and can now be seen from the 'encoding' and 'fconfigure OR chan configure' commands - yet oddly MISSING from 'open'!! There are 3 provided "profiles": 1. tcl8 2. replace 3. strict for which V9.x chose #3 as the DEFAULT - thus the complaints when a "mixed" encoding occurs. The #2...
-
Please update copyright info in README.txt
-
Understood, and thank you for the followup. As a "relative" neophyte to contributing to the FOSS world, I appreciate the mentoring toward 'accepted practices'. There is a new version in the works (owing to a recent upgrade to a major Tcl/Tk release) and I assure you the Copyright information will be updated at that time.
-
The upshot here is what might you be looking for as pertains to an updated Copyright list? A correct list of copyright holders serves at least two important purposes: Relicensing is impossible if the copyright holders are not known and cannot be contacted to give their permission to relicense. It is also hard to enforce a license if the actual authors are not known. Attribution: IMHO it is just a matter of basic politeness to state whom the users might be grateful to. e.g. I recently was made aware...
-
Hello, sorry in hindsight I see that my report should have been more verbose: I looked at the licenses/copyright info and found that it obviously had not seen any update for 20 years while SVN showed more than 150 changes after that. That could not be right. Looking over the commiters I saw that their number was small (no one-commit authors) and therefore suggested the list above. I did not do a full in depth review. I am no lawyer either but the FSF site has some guidance where the bar for a copyright...
-
DorothyR modified a comment on ticket #100
I'm not sure I (dorothy robinson) really deserve a copyright here. I did act as interim mantainer for, well, a fairly long interim, but I mostly just tweaked the user interface and command parsing a little bit, and accepted some patches.
-
I'm not sure I (dorothy robinson) really deserve a copyright here. I did act as interim mantainer for, well, a fairly long interim, but I mostly just tweaked the user interface an command parsing a little bit, and accepted some patches.
-
Not entirely certain of the rules (if any) governing this. While Bryan was clearly a major force in the early days of the tool and has contributed much - not only in actual code, but even an IDEA that I subsequently utilized FAR LATER, and thus is clearly a missing attribution (as is Dorothy, who presided longer than anyone, over uncounted modifications by my reckoning); yet badukaire (according to my records) contributed a patch (not in 2012, but 2005?) which then languished until I joined in 2017!!...
-
Here's the relevant tcl9.0 manpage https://www.tcl-lang.org/man/tcl9.0/TclCmd/chan.html#M48 On Sun, Jun 22, 2025 at 12:52 PM DorothyR dorothyr@users.sourceforge.net wrote: Filetype gives a clue, although I don't know how or why this happened $ file * cvsdiff: POSIX shell script, ASCII text executable dirdiff: POSIX shell script, ISO-8859 text executable tkdirdiff: POSIX shell script, ISO-8859 text executable [bugs:#101] Invalid multibyte or wide char in test file causes crash with tk9.0 Status: open...
-
Oh great it's the copyright string: 776:Copyright � 1999-2005 Paul Mackerras Here's the relevant tcl9.0 document https://www.tcl-lang.org/man/tcl9.0/TclCmd/chan.html#M48
-
Oh great it's the copyright string: 776:Copyright � 1999-2005 Paul Mackerras
-
Filetype gives a clue, although I don't know how or why this happened $ file * cvsdiff: POSIX shell script, ASCII text executable dirdiff: POSIX shell script, ISO-8859 text executable tkdirdiff: POSIX shell script, ISO-8859 text executable
-
Invalid multibyte or wide char in test file causes crash with tk9.0
-
Please update copyright info in README.txt
-
avoid TclTk 9.0 'namespace' interactions
-
improper logic supplying default revision values to 2/3rds of 12 SCMS repaired
-
Primarily to support TclTk 9.0 (and compensate for lost V8.x.x deprecations)
-
Dorothy is correct. The preference in question is on the 'General' tab of the Preferences dialog window and labeled 'Text window size' expressed in a WidthxHeight format. As the windows are side by side, that means the width of the TOOL is actually computed as TWICE the requested width (plus all the other things like scrollbars, etc). Furthermore, on the 'Appearance' tab, another preference (Text widget options) allows you to specify the FONT those text windows should USE, and is the base unit of...
-
In Edit->Preferences-General there's a Text Window Size setting. It doesn't appear do do anything on Apply, but if you Save and then restart it will be used next time.
-
Skeet Monker posted a comment on discussion Help
Love tkdiff !! The best visual diff'ing tool I have found. By default, tkdiff opens in a window that is about 75% the width of my screen. Each time I manually stretch the window to widen it to about 98% - 100% width. Is there a preference setting, or command option, to change the default window width ? Is there a line in the tkdiff script which could be edited to expand the default window width ? Thanks much!
-
Wow. I hate to admit this, but you ARE correct (frankly, that whole line should have been ELIMINATED a long time ago - which is what I intend to do going forward). Feel free to delete it as it is ALREADY covered by the one on line#32! Better yet, place an octothorp (#) as the first char ON that line (making it a comment); that way you'll still have the same line numbers in YOUR script as the 'official' one, in case you need to report yet MORE issues! The only reason it worked until now is because...
-
Sait Umar posted a comment on ticket #99
I have the line 32 but also line 15359
-
Wait - line #32 (package require Tk 8.5-) should be the ONLY place to have needed editing -- where (and why) did you make a SECOND edit?? A text searches only turns up seven additional occurrences of a 8.5 string of text, ALL of which are buried within comments, and as documentation, need not change NOR have any effect whatsoever.
-
Yes, putting 8.5- works as well (in two places). Thanks!
-
OK - so with regard to the version-check failure. I personally would contend that this is a coding bug, but whomever wrote it originally probably failed to interpret closely the exact syntax required to express the notion of a minimum, but open-ended semantic. Instead, what was actually written was a minimum, but terminated at the next MAJOR version. Accordingly, while you stated changing the version (from 8.5 to 9.0 worked for you, the real fix should be the value "8.5-" (note the trailing dash...
-
In a general sense, perhaps. But by and large, TkDiff is written well within the bounds of classic TCL scripting only, and underwent a serious (>70%) code refactoring in the V8.5-8.6 time frame, making it thus relatively impervious to a majority of changes taking place in version 9.0. Such changes are mostly those of prior announced deprecations finally being removed because of the now new MAJOR version number(eg. 8 -->> 9). Many of whose 'deprecations' date back to pre-V8.6 which, given the glacial...
-
guardus posted a comment on ticket #99
Tcl 9 is incompatible with 8. See below links for major incompatibilities and more info. https://www.tcl-lang.org/software/tcltk/9.0.html https://core.tcl-lang.org/tcl/wiki?name=Migrating+scripts+to+Tcl+9 https://wiki.tcl-lang.org/page/Porting+extensions+to+Tcl+9 https://github.com/apnadkarni/tcl9-migrate
-
Gonna need some time to investigate. Technically the version check in TkDiff should only require a MINIMUM of TK 8.5, so I don't understand WHY 9.0 (clearly more recent) is unacceptable. The fact you say it seems to RUN is encouraging (it SHOULD, as Tcl/Tk has a history of generally maintaining backward compatibility). Post anything else you find to this ticket and I'll do the same with what I can learn.
-
Not compatible with tk 9.0
-
-
Update the README to say that the tk8.5 that comes with MacOS will not work, and recommend the version on Homebrew
-
Rui Chen posted a comment on ticket #98
yeah, I have an open PR on this. Can you add some warning notes in the README or script about the default tcl-tk? (and recommend user to install tcl-tk, if they install via brew, they will get it though)
-
I don't know when it started, but I get the same error just by invoking /usr/bin/wish (shell wrapper to /System/Library/Frameworks/Tk.framework/Versions/8.5/Resources/Wish.app/Contents/MacOS/Wish) From Googling I get that this is a code signature problem with apple's wish. Anyway, invoking the default tcl-tk has produced a deprecation warning for years now, and I believe tkdiff hasn't run on it for several releases and w always say to use homebrew or macports. I think homebrew tcl-tk should be a...
-
tkdiff 5.7 does not work with macos tcl-tk (8.5)
-
highlight not working for last line difference
-
view -> inline compare (recursive) requires a reload to highlight changes
-
Well, a LOT has happened between V4.2 and V5.6; so the fact they might behave marginally different between then (over a decade ago) and now is not terribly descriptive of a "problem". Back then, the recursive approach reported EVERYTHING different in any given pair of lines. Over the past several years (and intervening releases) the recursive approach has become considerably more detailed and configurable. Nowadays you can specify exactly WHICH (if any) of the various suppression idioms (Blanks,...
-
Official TkDiff Version 5.7 is released
-
-
-
forgot to bump release to 5.7
-
chglog updated for release 5.7
-
OK. Turns out there were multiple issues (almost a wonder it functioned as well as it did) but nevertheless the fix(es) are now completed. For the record, the OBSERVED issue only involved Diff hunks whose "highlight-able" size (in lines) was SOME multiple of 5 PLUS 1; whereby the "plus 1" (aka that FINAL line) failed to get marked-up. As this is rather difficult to anticipate and CLEARLY data dependent, an updated release will be forthcoming shortly. Thank you again, both for spotting and reporting...
-
Inline instantiation realigned: prevents Heuristic+1 dropouts; broken syntax; better reading
-
Bookmark annotation prompt now tracks instance AFTER 1st use
-
highlight not working for last line difference
-
My, what sharp little eyes you have! All kidding aside, you appear to be correct, although it may take a little time to work out the exact triggering situation (eg. is it ANY 16-line hunk, the last physical hunk, only at file EOL, etc.). The 61 suggests its not some "power-of-2" related issue, but we will find out eventually. I applaud your industriousness for finding even the beginning of a "pattern". Will report more after I do some investigating. Standby.
-
Markku Ilmanen created ticket #97
highlight not working for last line difference
-
Add missing trigger event when recursive inlines are activated
-
rob m posted a comment on ticket #96
thanks! i just upgraded from 4.2 -> 5.6 so it is just the data point i have even if it is not all that useful. my tkdiffrc defaults to inline recursive to off but i like to toggle it on / off when looking at diffs to point out non-obvious things for whatever line i happen to be looking at. thanks again.
-
view -> inline compare (recursive) requires a reload to highlight changes
-
Well, a LOT has happened between V4.2 and V5.6; so the fact they might behave marginally different between then (over a decade ago) and now is not terribly descriptive of a "problem". Back then, the recursive approach reported EVERYTHING different in any given pair of lines. Over the past several years (and intervening releases) the recursive approach has become considerably more detailed and configurable. Nowadays you can specify exactly WHICH (if any) of the various suppression idioms (Blanks,...
-
tkdiff 5.6 with patch 189 on Ubuntu 22.04.3 LTS x64
-
view -> inline compare (recursive) requires a reload to highlight changes
