00:00:00 --- log: started forth/07.12.07 00:12:15 edrx: thank you thankyou! 00:14:53 :-) 00:22:35 --- join: ecraven (i=nex@eutyche.swe.uni-linz.ac.at) joined #forth 00:31:24 --- quit: cmeme ("Client terminated by server") 00:31:55 --- join: cmeme (n=cmeme@boa.b9.com) joined #forth 00:38:24 --- join: doublec (n=doublec@203-97-173-6.cable.telstraclear.net) joined #forth 01:13:39 --- join: maht (n=maht@85.189.31.174.proweb.managedbroadband.co.uk) joined #forth 01:39:55 --- join: crest_ (n=crest@p5B103D2A.dip.t-dialin.net) joined #forth 01:47:42 --- quit: Crest (Connection timed out) 02:20:56 --- quit: maht (Connection reset by peer) 02:40:53 --- quit: Quartus (Read error: 110 (Connection timed out)) 02:41:08 --- join: Quartus (n=neal@CPE0001023f6e4f-CM001947482b20.cpe.net.cable.rogers.com) joined #forth 02:41:08 --- mode: ChanServ set +o Quartus 02:51:55 --- quit: TreyB (Remote closed the connection) 02:51:58 --- join: TreyB (n=trey@cpe-66-87-192-27.tx.sprintbbd.net) joined #forth 03:16:46 --- quit: TreyB (Remote closed the connection) 03:21:25 --- join: TreyB (n=trey@cpe-66-87-192-27.tx.sprintbbd.net) joined #forth 03:35:26 --- quit: doublec () 04:01:17 --- quit: edrx (Remote closed the connection) 04:04:36 --- quit: TreyB (Remote closed the connection) 04:04:39 --- join: TreyB (n=trey@cpe-66-87-192-27.tx.sprintbbd.net) joined #forth 04:16:34 --- join: maht (n=maht@85-189-31-174.proweb.managedbroadband.co.uk) joined #forth 05:47:06 --- quit: nro (calvino.freenode.net irc.freenode.net) 05:47:06 --- quit: madgarden (calvino.freenode.net irc.freenode.net) 05:47:06 --- quit: tane (calvino.freenode.net irc.freenode.net) 05:47:11 --- join: nro (i=o@o.ihqu.fi) joined #forth 05:47:11 --- join: madgarden (n=madgarde@bas2-kitchener06-1096752101.dsl.bell.ca) joined #forth 05:47:11 --- join: tane (n=blub@p5B15D165.dip.t-dialin.net) joined #forth 05:53:07 --- quit: crest_ (Read error: 110 (Connection timed out)) 06:05:46 --- join: Crest (n=crest@p5B10577B.dip.t-dialin.net) joined #forth 06:30:06 --- join: saon (n=saon@207.138.42.211) joined #forth 06:30:19 --- part: saon left #forth 06:41:13 --- quit: proteusguy (Remote closed the connection) 06:42:21 --- join: proteusguy (n=proteusg@ppp-124.120.228.196.revip2.asianet.co.th) joined #forth 06:44:38 --- join: ziggurat (n=ziggurat@pool-71-164-227-62.dllstx.fios.verizon.net) joined #forth 06:45:51 --- join: tdlarson (n=tdlarson@65.116.199.19) joined #forth 06:47:10 since forth is used to control hardware...drifting [OT]...anyone know why an okidata dotmatrix printer would not advance as far from one page to the next as its page length setting says it should? 06:48:04 mmm 06:48:12 used to have a crappy old okidata 06:48:31 the maintainer of the linux driver for it refused to support the model I had because it was broken 06:48:43 hehe, ouch 06:48:50 but I found some user-mode (user-level) program that did it ok 06:48:57 user-space 06:49:02 that's the term 06:49:56 the paper is tractor fed, 8 1/2 inches long...but the printer advances probably about 8 inches for each logical page 06:50:19 Sure the switch settings are set for 8.5x11, and not A4 or something nutsy like that? 06:50:28 Or that your paper isn't really A4? :) 06:51:00 I had it print its settings, and it claims the rear feed is set to 8 1/2 inches long 06:51:13 What model? 06:51:26 okidata microline 395 06:52:52 I'm surprised you can still find ribbons for it. 06:52:53 also...it worked fine until a few days ago when we changed the IP address of the little box that connects it to ethernet. 06:53:07 that is when the page length problem started 06:53:35 we have had to replace the print head several times, and that has been interesting just trying to get ahold of one 06:54:45 I know the switch settings are used for when a page eject (typically control-l) is sent to the printer, so it knows how far to move the paper. It almost sounds like something else is keeping track of the paper length (typically a print driver), and it's now set for the wrong length. 06:55:13 You could test this by telling the printer the paper is a different length with the switches, and see if it has any impact. If not, you know to look upstream from the printer. 06:55:15 ah, like advancing pages by sending line feeds? 06:55:19 Yes 06:55:38 going to check on this. 06:59:30 yup, looks like you got it. 06:59:59 now to track down what is setting the number of lines it is advancing. 07:00:23 thanks for the help :) 07:00:34 Glad to help. 07:43:13 mmmm 07:43:26 homemade lemonade 07:43:40 some good organic lemon juice 07:43:45 maple sirup 07:44:07 and a touch of kayanne pepper 07:44:28 doesn't get much better 07:44:45 bight taste better with fresh lemons, but that'd be work 07:45:03 ok, back to my keybinding scheme 07:46:55 --- quit: Quartus__ (Read error: 104 (Connection reset by peer)) 07:47:31 --- quit: madwork (Read error: 110 (Connection timed out)) 08:37:28 --- quit: tdlarson (Read error: 104 (Connection reset by peer)) 08:44:58 --- join: tdlarson (n=tdlarson@65.116.199.19) joined #forth 08:49:27 *&@^#$*@#$ keyboards 08:50:19 I keep finding sets of 3 keys that my keyboard can't handle at once 09:00:44 --- join: madwork (n=foo@204.138.110.15) joined #forth 09:06:56 --- join: tdlarson_ (n=tdlarson@65.116.199.19) joined #forth 09:10:49 --- join: tdlarson__ (n=tdlarson@65.116.199.19) joined #forth 09:24:59 --- quit: tdlarson (Read error: 110 (Connection timed out)) 09:28:49 --- quit: tdlarson_ (Read error: 110 (Connection timed out)) 09:37:32 --- join: tdlarson_ (n=tdlarson@65.116.199.19) joined #forth 09:40:14 --- join: tdlarson (n=tdlarson@65.116.199.19) joined #forth 09:55:10 --- quit: tdlarson__ (Read error: 110 (Connection timed out)) 09:55:54 --- join: tdlarson__ (n=tdlarson@65.116.199.19) joined #forth 09:57:51 --- quit: tdlarson_ (Read error: 110 (Connection timed out)) 10:00:30 --- join: tdlarson_ (n=tdlarson@65.116.199.19) joined #forth 10:05:43 --- quit: tdlarson (Read error: 110 (Connection timed out)) 10:18:24 --- quit: tdlarson__ (Read error: 110 (Connection timed out)) 11:04:36 --- join: forther (n=forther@c-67-180-150-67.hsd1.ca.comcast.net) joined #forth 11:24:24 --- join: snoopy_1711 (i=snoopy_1@dslb-084-059-122-255.pools.arcor-ip.net) joined #forth 11:27:52 --- quit: Crest (Read error: 110 (Connection timed out)) 11:32:45 --- quit: Snoopy42 (Read error: 145 (Connection timed out)) 11:33:08 --- nick: snoopy_1711 -> Snoopy42 11:41:34 --- join: tdlarson__ (n=tdlarson@65.116.199.19) joined #forth 12:00:56 --- quit: tdlarson_ (Read error: 110 (Connection timed out)) 12:04:02 --- join: tdlarson_ (n=tdlarson@65.116.199.19) joined #forth 12:21:49 --- quit: tdlarson__ (Read error: 110 (Connection timed out)) 12:25:39 --- quit: tdlarson_ ("Leaving") 12:59:32 --- quit: ecraven ("bbl") 13:11:53 --- part: ziggurat left #forth 13:28:06 --- quit: proteusguy (calvino.freenode.net irc.freenode.net) 13:28:07 --- quit: cmeme (calvino.freenode.net irc.freenode.net) 13:28:07 --- quit: Deformati (calvino.freenode.net irc.freenode.net) 13:28:07 --- quit: timlarson (calvino.freenode.net irc.freenode.net) 13:28:08 --- quit: mrsbrisby (calvino.freenode.net irc.freenode.net) 13:31:48 --- join: Deformati (n=joe@c-68-61-240-49.hsd1.mi.comcast.net) joined #forth 13:32:25 --- join: cmeme (n=cmeme@boa.b9.com) joined #forth 13:43:55 --- join: mrsbrisby (i=nimh@nimh.org) joined #forth 13:44:13 --- join: timlarson (n=timlarso@user-12l37rb.cable.mindspring.com) joined #forth 13:45:12 --- join: proteusguy (n=proteusg@ppp-124.120.228.196.revip2.asianet.co.th) joined #forth 14:13:25 --- quit: ncv_ (Read error: 104 (Connection reset by peer)) 14:46:52 --- join: dogmaster (n=Tom@dpc6935113243.direcpc.com) joined #forth 14:47:30 --- part: dogmaster left #forth 14:47:49 --- join: TreyB_ (n=trey@cpe-66-87-192-27.tx.sprintbbd.net) joined #forth 14:52:43 --- join: Al2O3 (n=Al2O3@43.sub-70-215-52.myvzw.com) joined #forth 14:56:49 --- join: Al2O3__ (n=Al2O3@c-75-70-5-69.hsd1.co.comcast.net) joined #forth 14:59:02 --- quit: Al2O3__ (Client Quit) 15:03:32 --- quit: TreyB (Read error: 110 (Connection timed out)) 15:09:04 --- join: Al2O3__ (n=Al2O3@c-75-70-5-69.hsd1.co.comcast.net) joined #forth 15:10:17 --- quit: Al2O3_ (Read error: 110 (Connection timed out)) 15:14:35 --- quit: Al2O3 (Connection timed out) 15:20:09 --- join: edrx (i=edrx@189.25.33.253) joined #forth 15:33:18 --- join: saon_ (n=saon@fl-71-1-146-10.dhcp.embarqhsd.net) joined #forth 15:33:35 --- part: saon_ left #forth 17:19:38 --- part: edrx left #forth 18:27:36 --- join: Quartus__ (n=Quartus_@209.167.5.2) joined #forth 18:29:35 --- join: tane`weq (n=blub@p5B15EADC.dip.t-dialin.net) joined #forth 18:47:25 --- quit: tane (Read error: 101 (Network is unreachable)) 18:48:55 --- quit: Al2O3__ ("Eggplant & SenseTalk: Driving Success Through Automation") 18:52:58 --- join: doublec (n=doublec@203-97-173-6.cable.telstraclear.net) joined #forth 18:56:31 Hey. 19:01:43 --- join: Al2O3 (n=Al2O3@c-75-70-5-69.hsd1.co.comcast.net) joined #forth 19:18:39 --- quit: Quartus__ (Read error: 104 (Connection reset by peer)) 19:37:33 --- join: Crest (n=crest@p5B104DEE.dip.t-dialin.net) joined #forth 20:04:49 --- quit: proteusguy (Read error: 110 (Connection timed out)) 20:05:40 --- join: proteusguy (n=proteusg@ppp-124.120.216.229.revip2.asianet.co.th) joined #forth 20:16:15 --- quit: doublec () 20:47:02 --- join: doublec (n=doublec@203-97-173-6.cable.telstraclear.net) joined #forth 20:53:11 --- quit: forther ("Leaving") 21:14:41 --- quit: doublec () 23:54:32 man, weird stuff happens when I try to use the wrong three keys at once 23:54:45 I made a quick SDL program that logs key up and key down events 23:56:15 if I hold space and ; and press keys, some work, some do nothing, and some cause key up, then key down events for the space and ; keys (but don't cause any event for the key I'm actually pushing) 23:57:40 oops, guess that's the ' key, not ; 23:57:55 I moved the keycaps so it shows dvorak 23:57:58 to me it's - 23:58:00 hey 23:58:26 in xterm I can hold space and - and there's a bunch of keys that make another "- " appear on the terminal 23:58:33 hey slava 23:59:01 guess I'll have to learn to hold some other key while I type stuff into my temporary input buffer things 23:59:17 i'm debugging our regexp implementation 23:59:26 this used to kill it: "(0[lL]?|[1-9]\d{0,9}(\d{0,9}[lL])?|0[xX]\p{XDigit}{1,8}(\p{XDigit}{0,8}[lL])?|0[0-7]{1,11}([0-7]{0,11}[lL])?|([0-9]+\.[0-9]*|\.[0-9]+)([eE][+-]?[0-9]+)?[fFdD]?|[0-9]+([eE][+-]?[0-9]+[fFdD]?|([eE][+-]?[0-9]+)?[fFdD]))" 23:59:48 not kill it, but it would take about 60 mb of memory and 20 seconds to parse that regexp into a combinator 23:59:59 --- log: ended forth/07.12.07