>>>>> "DV" == Dominik Vogt <fvwm-workers@fvwm.org> writes:
DV> On Tue, Sep 10, 2002 at 02:27:20PM -0400, Charles Hines wrote: ... >> I finially got around to looking into this problem, and turned out that >> finding where the problem and coming up with a workable fix was actually >> rather easy: DV> And it's the right fix too. And there was much rejoicing... :) ... >> At least, that seemed to make things behave properly for me. DV> Welcome back to the fvwm developer community. I'd hardly constitute this piddly little patch as my return to fvwm development. :) DV> We'd be happy to give you cvs commit rights if you want them :-) Have to pass for now as our firewall at work won't let cvs through and I still don't know how much I'd be able to get away with doing from home right now either, but thanks anyways! Maybe someday... Speaking of cvs access, however, wasn't it possible in the past to browse the cvs repository for fvwm via the cvsweb interface? The bookmark that I had to that no longer works and no amount of guessing (or looking over the links on the fvwm website) could find it. DV> I have applied the patch. Was this also a problem in 2.5.x? I DV> guess not since the faulty code was already removed, but I did not DV> try it out myself. Don't know, let me grab the code and check it out...assume it's not unless I send another message to the contrary... :) Thanks, Chuck -- Charles K. Hines <[EMAIL PROTECTED]> <[EMAIL PROTECTED]> Principal Scientist at ReQuest Technologies Inc (http://www.ReQuestTech.com/) "dis ting could have possabiwities if I put my twisted widdle mind to it!" - Bugs Bunny -- Visit the official FVWM web page at <URL:http://www.fvwm.org/>. To unsubscribe from the list, send "unsubscribe fvwm-workers" in the body of a message to [EMAIL PROTECTED] To report problems, send mail to [EMAIL PROTECTED]
