0.6 is ready. Since I added a lot, it might need to be tested by whoever is willing; I only have three linux installations to test this on (including lenny), and I have noticed one or two abstruse "off by one" errors and short over-writes between functions that did not show up until I tested it on the third system. This is because slightly different compilers, even maybe two different builds of the same gcc version (I dunno) could put memory together slightly differently, so if under one version you get away with a programming error it could still show up under another. Maybe in that sense three is a good number ;) In fact I found at least half dozen bugs exactly like this during reprogramming that took me an average of an hour each to sort out in the past few days, hopefully that was most or all of them. Anyway, I devised a little battery of simple tests. Since the executable name and /usr/local/share directory have changed, use 0.53 to uninstall. There is info in the ChangeLog and NEWS. The man page and web man page are updated. Run "seetxt" in a terminal to watch the console output. There shouldn't be any, except from gzip() when loading manpages about a broken pipe. This is explained on the gzip homepage, where they blame it on bash (which makes sense, the error is really from bash). 1) Try drag n' drop from nautilus. 2) Leave see running and then add a "copy to:" directory to your .seeconfig, then try "reconfigure" 3) Load /usr/share/X11/rgb.txt, which is in the stock filelist. 4) Presuming your rgb.txt is the lenny english version, and you successfully reconfigured, you should now be able to type "grep sea SEEBUF" (notice 1 F) into the text entry and then select "execute" from the menu. That will be this: 255 245 238 seashell 143 188 143 dark sea green 46 139 87 sea green 60 179 113 medium sea green 32 178 170 light sea green 255 245 238 seashell1 238 229 222 seashell2 205 197 191 seashell3 139 134 130 seashell4 now try the "copy out" 5) flip around the filelist, maybe leave some highlighting and come back via the filelist. You should alway return to where you last PLACED THE CURSOR, and the highlighting should remain. 6) Go back to the file with all the sea stuff from your "copy out". Do a simple search for "sea". Now toggle regexp and push. Do a search for "\bsea\b". You should see 5 seas in purple and four in yellow. Now add a watch to the file with the right-side toggle, and use "send to editor", if that is set to something usable for you. Add a big line of XXXXXXXXX somewhere and see that it appears in the updated view. 7) If you have a reasonably big /var/log/messages, that is in the stock filelist too, check that it loads. If it is less than 100000 lines, see how turning line numbering on and off goes. 8) Do anything else you can think of a sane person would do, such as an apropos search, or check to see the highlighting you left is still there. All that should be preserved between instances, so you can start and stop see during the test. If you encounter a regular problem, use "seetxt -d2" to output a debug log, which are messages about the current state and execution, etc. If you add "debug log: /some/path/file" to ~/.seeconfig, see will redirect this output to the file and you can send it to me! I haven't updated freshmeat yet, so the only source is: http://www.intergate.com/~halfcountplus/see
Attachment:
see-0.6.tar.bz2
Description: Binary data