Ready for Python 2.1 ?
Before starting to work on postponed patches and checking them in: is the current CVS tree ready for new checkins (tags applied, etc.) ?
M.-A. Lemburg writes:
Before starting to work on postponed patches and checking them in: is the current CVS tree ready for new checkins (tags applied, etc.) ?
Yes; I posted a note re-opening the tree yesterday (or late Monday night; I can't remember that far back). We've just been too tired to do a lot since the release. ;)
-Fred
Tim> my-wrists-are-killing-me-ly y'rs - tim
You need my typing watcher:
http://www.musi-cal.com/~skip/python/watch.py
Only problem is I never figured out how to make it watch keystrokes directly. It detects mouse movement. Since I do most of my typing in Emacs, I fudged the keystroke thing by having the auto-save hook jiggle the mouse a little...
I've tried, so far unsuccessfully, to make this a SourceForge project. I've even asked for help from SF, but their response wasn't helpful, and the round-trip time for a response is too long to make pursuing that path worthwhile. The watch project is at
http://sourceforge.net/projects/watch/
All I have is a CVSROOT/modules file. Nothing I've tried has successfully imported the one project file into cvs.
If anyone has any suggestions for kickstarting this thing, it would be much appreciated.
Thx,
Skip
On Wed, Oct 18, 2000 at 12:19:25PM -0500, Skip Montanaro wrote:
Tim> my-wrists-are-killing-me-ly y'rs - tim
You need my typing watcher:
Given his remark about suicide attempts, I'm not sure if Tim really meant 'RSI' when he wrote that :-)
http://www.musi-cal.com/~skip/python/watch.py
Only problem is I never figured out how to make it watch keystrokes directly. It detects mouse movement. Since I do most of my typing in Emacs, I fudged the keystroke thing by having the auto-save hook jiggle the mouse a little...
Funny, a colleague of mine has a similar tool. Also written in Python, I think, though it may have been created in his Perl Period. On a linux box, you can determine keystrokes by using /proc/interrupts. At least, if your keyboard has an interrupt all for itself. (Pretty likely, really :)
Thomas> On a linux box, you can determine keystrokes by using Thomas> /proc/interrupts. At least, if your keyboard has an interrupt Thomas> all for itself. (Pretty likely, really :)
Thanks, Neil S. sent me a patch for that already. I'll try to work it into the code. Anyone have any idea how to monitor keystrokes on Windows, Mac or other Unix flavors? I suspect I'll just have to bite the bullet and work in platform-dependent code for this.
Skip
Skip Montanaro skip@mojam.com:
Thanks, Neil S. sent me a patch for that already. I'll try to work it into the code. Anyone have any idea how to monitor keystrokes on Windows, Mac or other Unix flavors? I suspect I'll just have to bite the bullet and work in platform-dependent code for this.
Might this monitoring function be a candidate for the Python library when it's done?
Skip Montanaro writes:
Thanks, Neil S. sent me a patch for that already. I'll try to work it into the code. Anyone have any idea how to monitor keystrokes on Windows, Mac or other Unix flavors? I suspect I'll just have to bite the bullet and work in platform-dependent code for this.
Can't tell you about Windows or Mac, but for Unix I'd read the file driver/timers.c in the XScreensaver distribution (www.jwz.org). This code is pretty sophisticated and runs on all the major Unix flavors.
Charles> ... but for Unix I'd read the file driver/timers.c in the Charles> XScreensaver distribution (www.jwz.org). This code is pretty Charles> sophisticated and runs on all the major Unix flavors.
Thanks, Charles. I will check it out.
Those of you who are former (or current) od users will appreciate Jamie Zawinski's home page even if you're not interested in this topic. I revisit his site periodically. I'm never disappointed...
Skip
Skip Montanaro discourseth:
Those of you who are former (or current) od users will appreciate Jamie Zawinski's home page even if you're not interested in this topic. I revisit his site periodically. I'm never disappointed...
Looks more like emacs hexl-mode to me.
Hmm..I guess you got this thread off topic. :)
E
participants (8)
-
Charles G Waldman -
Eric S. Raymond -
est＠hyperreal.org -
Fred L. Drake, Jr. -
M.-A. Lemburg -
Skip Montanaro -
Thomas Wouters -
Tim Peters