00:00:00 --- log: started forth/04.02.13 00:54:55 --- quit: MarkT (Read error: 104 (Connection reset by peer)) 00:55:44 --- quit: cmeme (Read error: 60 (Operation timed out)) 02:08:56 * warpzero is away: Ah, grab that squeejy. 02:37:51 --- quit: arke (Read error: 104 (Connection reset by peer)) 02:38:38 --- join: arke (~Chris@wbar8.lax1-4-11-099-104.dsl-verizon.net) joined #forth 02:47:21 --- quit: Nutssh ("Client exiting") 03:44:54 --- join: Nutssh (~Foo@gh-1177.gh.rice.edu) joined #forth 04:20:24 --- quit: ree (Read error: 110 (Connection timed out)) 04:21:41 --- join: ree (~jwm@ns.fasthost.net) joined #forth 04:22:56 --- join: qFox (C00K13S@cp12172-a.roose1.nb.home.nl) joined #forth 04:25:37 --- quit: arke (Read error: 104 (Connection reset by peer)) 04:25:38 --- join: arke_ (~Chris@wbar8.lax1-4-11-099-104.dsl-verizon.net) joined #forth 04:42:56 --- part: Nutssh left #forth 05:20:50 --- join: arke (~arke@wbar8.lax1-4-11-099-104.dsl-verizon.net) joined #forth 05:21:01 hey arke 05:21:16 hehe, thats my telnet session 05:21:21 whats up ree? 05:21:30 hehe 05:21:36 not much atm.. work 05:21:41 you? 05:21:57 well, playing around with a language...making an IRC client 05:22:07 :) 05:22:20 I decided to use the linux kernel for DNOS 05:22:36 since DNOS is a "small" step for the real projects (networks) 05:22:40 cool 05:22:47 --- nick: arke -> arke_telnet 05:22:50 --- nick: arke_ -> arke 05:22:53 no other typical unix stuff in it though 05:22:59 dump init 05:23:04 init is slow :) 05:23:20 of course hehe 05:23:57 --- quit: arke_telnet (Client Quit) 05:24:37 freenode isn't stnadard RFC.. 05:25:51 yay 05:25:57 IRC client can connect to freenode 05:26:08 no user input yet tho 05:26:54 doing it in forth? 05:29:24 Hehe. 05:32:10 no ;( 05:32:32 its a specialized RAD language 05:32:35 called jamagi 05:32:37 called jamagic 05:32:43 very RAD oriented 05:35:18 I got a very whitespaced non-interactive IRC client in 14 lines 05:51:16 CRLF=0x1013 right? 05:51:29 CR = 0x10, LF = 0x13 05:51:58 erm, nevermind 05:53:00 --- join: proteusguy (proteusguy@27.sub-166-153-36.myvzw.com) joined #forth 05:53:06 hi proteusguy 05:53:41 howdy arke 05:54:35 howa re ya 05:56:24 actually a bit concerned. My gf was stuck in Chicago last night, stayed at the airport waiting for a flight out here but now I can't reach her. Maybe her cell's dead... 05:58:12 :( 06:01:12 dammit 06:01:24 it inserts the newline, but also spits out garbage 06:01:24 dammit 06:01:53 aah, now I got it 06:04:04 blah test 06:44:34 --- quit: ree (Read error: 110 (Connection timed out)) 06:45:09 --- join: ree (~jwm@ns.fasthost.net) joined #forth 07:05:03 --- quit: qFox (Read error: 104 (Connection reset by peer)) 07:07:05 --- quit: ree (Read error: 60 (Operation timed out)) 08:00:21 --- join: _proteus (proteusguy@242.sub-166-153-50.myvzw.com) joined #forth 08:01:13 --- nick: _proteus -> protuesguy 08:12:07 --- quit: proteusguy (Read error: 113 (No route to host)) 08:35:22 hi all 08:38:23 hi 08:38:38 --- join: qFox (C00K13S@cp12172-a.roose1.nb.home.nl) joined #forth 09:27:05 --- quit: protuesguy ("Leaving") 09:28:37 --- join: ASau (~asau@158.250.48.196) joined #forth 09:28:43 Dobryjj vecher! 09:29:01 --- join: kc5tja (~kc5tja@66-91-231-74.san.rr.com) joined #forth 09:29:06 --- mode: ChanServ set +o kc5tja 09:29:08 Dobryjj vecher, kc5tja! 09:29:37 --- quit: kc5tja (Client Quit) 09:29:51 ASau, remember your discussion about argument order for combinators? I guess you think [ code ] [ list ] map is better too? 09:29:51 --- join: kc5tja (~kc5tja@66-91-231-74.san.rr.com) joined #forth 09:29:58 --- mode: ChanServ set +o kc5tja 09:31:06 I'd say [ list ] [ code ] map is better. 09:31:40 ASau, this is what i have now 09:31:49 ASau, but why then [ if ] [ else ] [ condition ] ifte? 09:32:53 arke, can I see your IRC code please/ 09:34:22 My heuristic is: the most constant part should be the rightmost. 09:34:45 So you could feel like dealing with combinators. 09:40:48 --- quit: qFox (Read error: 104 (Connection reset by peer)) 09:49:39 --- join: qFox (C00K13S@cp12172-a.roose1.nb.home.nl) joined #forth 09:53:15 --- quit: kc5tja ("THX QSO ES 73 DE KC5TJA/6 CL ES QRT AR SK") 10:02:04 --- quit: qFox (Read error: 104 (Connection reset by peer)) 10:03:09 --- join: qFox (C00K13S@cp12172-a.roose1.nb.home.nl) joined #forth 10:14:59 --- join: cmeme (~cmeme@216.184.11.30.unused.swcp.com) joined #forth 11:17:58 --- join: proteusguy (proteusguy@36.sub-166-153-39.myvzw.com) joined #forth 11:26:26 --- quit: ASau () 13:39:03 --- quit: proteusguy (Read error: 113 (No route to host)) 13:50:16 --- join: proteusguy (proteusguy@6.sub-166-153-54.myvzw.com) joined #forth 13:57:36 --- join: ASau (~asau@158.250.48.196) joined #forth 13:58:27 Dobraja noch'! 13:58:42 russian? 14:13:47 privet ASau! 14:13:48 kak deal? 14:13:54 kak dela? 14:20:50 I've got a dilemma: blocks vs. files. 14:21:06 "To be or not to be?" 14:21:17 No. 14:21:38 two bee or not to bee? 14:21:49 ASau, database backed storing source, like smalltalk! 14:22:34 I don't know SmallTalk. Links? Or a tale? 14:23:21 Better, <> (Majakovskijj vs. Shakespare) 14:23:31 ASau, download squeak smalltalk, its open source... 14:23:49 ASau, i'm not very familiar with it, but it stores methods as separate records in a database repos. 14:24:42 slava, it complexificates my system to large extent. 14:25:19 then i suggest files :) 14:38:27 I cannot access squeak.org, it seems to be down. 14:39:28 niether can i 15:08:45 smalltalk rulez 15:38:07 --- quit: arke (Read error: 54 (Connection reset by peer)) 16:11:06 --- quit: proteusguy (No route to host) 16:14:57 --- join: arke (~Chris@wbar8.lax1-4-11-099-104.dsl-verizon.net) joined #forth 16:15:10 So, who's read the Windows source yet? 16:15:39 i don't want to learn bad technique 16:16:03 lol 16:16:22 Actually, I am VERY interested in seeing it, as part of the rendering engine is in it 16:16:26 i havent read it yet 16:16:29 i want to see how it looks 16:17:14 It's probably just some BASIC code. 16:17:33 arke, don't look at it 16:17:37 arke, you will be "tainted" 16:18:56 If I get a chance without risk getting caught (unlikely :( ) Then I definetely will. 16:19:35 Window's graphics system is multiple times faster than Xf86, and many people will tell you that. 16:19:47 Also, Win2k graphics are quite stable. 16:19:59 (other things are contributing to the slowdown) 16:21:35 arke, you won't figure out why its faster just by glancing at the code. anyway i suspect its due to nothing more than simple profiling, and the fact that video drivers are better. 16:22:36 Hrm, I would say that from the amount it is faster, that its not just the drivers 16:24:10 I ran some tests too. 16:24:30 Xf86 on SuSE, WinXP, Win2k 16:24:53 the windowses were running 1280x1024x32xunaccel 16:25:03 xf86 was the same at 16 16:25:11 WinXP was by far the fastest 16:25:11 who cares? 16:25:17 Just saying 16:25:18 both get very good framerates in games 16:25:24 so its just bad apps 16:25:27 windows can be slow too 16:25:37 under cpu load, or if one program hangs and you can't move its windows or send them to the background 16:25:38 Windows is slow, but not its rendering system. 16:25:55 Heh 16:26:16 the average SDL-Win32 app gets an average of 4 more fps than the average SDL-xf86 app 16:26:17 until it decides to block everything 16:26:21 (the same app there) 16:43:39 4 fps is not a big deal and can probably be attributed to differences in the SDL impl, video driver, and so on. i doubt win32 graphics is fundamentally better than xfree 16:53:57 --- join: Sonarman (~matt@adsl-67-113-235-189.dsl.snfc21.pacbell.net) joined #forth 17:07:38 --- join: proteusguy (proteusguy@102.sub-166-153-42.myvzw.com) joined #forth 17:25:02 factor factor factor 17:35:46 --- join: kc5tja (~kc5tja@66-91-231-74.san.rr.com) joined #forth 17:35:53 --- mode: ChanServ set +o kc5tja 18:03:04 --- join: _proteus (proteusguy@102.sub-166-153-42.myvzw.com) joined #forth 18:06:16 --- quit: qFox (Read error: 104 (Connection reset by peer)) 18:06:51 --- join: qFox (C00K13S@cp12172-a.roose1.nb.home.nl) joined #forth 18:20:15 --- quit: proteusguy (Read error: 110 (Connection timed out)) 18:26:27 --- join: blockhead (default@dialin-871-tnt.nyc.bestweb.net) joined #forth 18:35:47 kc5tja: check out the w2ksp1 source yet? :) 18:36:02 No, and I don't particularly care. 18:36:21 why not? 18:36:59 Because it's Windows, I'm very tired, and I have lots of other (commercial) work to do at the moment. 18:38:00 Besides, I already have a perfectly fine OS running on my desktop, with multi-megabytes of source. I don't want to clutter up my drive with another OS' source code, only to never compile and use it. :) 18:38:45 but to look at it? :) 19:09:24 --- join: jstahuman (~justahuma@pcp053338pcs.brlngt01.nj.comcast.net) joined #forth 19:10:20 --- join: Robert_ (~snofs@c-8f5a71d5.17-1-64736c10.cust.bredbandsbolaget.se) joined #forth 19:18:56 arke: Again, not really interested. Sorry. 19:19:21 --- join: Robert__1 (~snofs@c-8f5a71d5.17-1-64736c10.cust.bredbandsbolaget.se) joined #forth 19:20:44 --- quit: Robert_ (Read error: 104 (Connection reset by peer)) 19:26:55 --- quit: Robert (Read error: 110 (Connection timed out)) 19:29:20 --- quit: _proteus (No route to host) 19:37:28 Ahh, Nethack... joyous gleeful distraction. 19:37:48 0^_^ 19:48:32 --- quit: qFox ("if at first you dont succeed, quit again") 19:52:21 Are there any speed readers here? 19:53:39 speed forth readers? 19:53:58 No, just people who read really fast. :) 20:12:59 ME 20:14:51 definitely not me :) 20:19:00 What's your technique? 20:28:08 madgarden: I read fast, but I think it's because I read a lot at an early age (novels at ten years old). So no technique, just lotsa practice. 20:30:49 Well, how fast? Give me a rate, say, #forth logs per hour. ;) 20:31:13 (assuming kc5tja was present that day) 20:31:51 * blockhead doesn't get the reference. forth logs? 20:32:24 on a good day (like, nothing else needs doing) two novels. 20:32:44 http://bespin.org/~nef/logs/forth/ 20:34:24 * blockhead checks the link 20:35:08 oh, logs of this channel 20:35:45 Yea. 20:37:21 Part of speed-reading seems to be the ability to not audibly "voice" the words in your head. 20:38:30 * blockhead agrees. 20:38:58 sort of like bypassing the regular parser :D 20:39:10 ALso, being able to see and absorb a group of words at a time, soak up the context without having to read the words individually. 20:40:06 reading forth logs might not be a good benchmark beacuse of the side-to-side window-scrolling to read everything 20:40:30 Well, I was just kidding about that anyway. 20:40:37 "D 20:40:41 :D, I meant 20:41:20 hey, I see myself in a log :D 20:42:25 * blockhead keeps reading hte log. So Robert was the one who encouraged me to start writing a forth. I knew it was somehone here but I forgot who. 20:42:42 Me too. Hey, look! I typed "hey, look!" in the log there! Followed by "in the log there!" 20:43:57 :) 20:44:03 I read pretty fast, I think 20:44:14 for the same reason as above (LOTS of practice 20:44:21 arke, what's your method? 20:44:39 arke, do you employ any of the techniques I mentioned? 20:44:47 No.. 20:44:51 I just read alot 20:44:55 so I can read fast now. 20:45:13 It usually takes me about half the time to read something as my classmates 20:45:17 less than that too 20:45:44 If I want to soak up the words, i choose to read slower and have the voices audibly in my head 20:45:52 but I can also do without 20:46:16 Yep. So it's either skimming to just get the jist of the text, or slow reading to more fully experience it. 20:46:23 (more or less) 20:46:30 well, even if I skim, I usually get all the details 20:47:10 madgarden: why do you ask? 20:47:38 Information overload, not enough time in the day to read all the cool stuff I want to. My programming projects suffer. ;) 20:48:00 oh. :( soory. 20:48:04 sorry, even 20:48:45 blockhead, yes, it's entirely *your* fault. 20:51:22 How's your Forth coming along? 20:52:10 it progresses, although slower than before. I had a bad problem yesterday but I fixed it today ... by deleting the problem words and redoign them from scratch. 20:52:55 I *think* I'm almost done with the primary (assembler) words. I want to code the rest using only secondary (forth) words. 20:53:19 Then I add the outer interpreter ... I hope :/ 20:53:25 :) 20:54:29 x86? 20:54:58 yeah, using DOS calls. 20:55:11 keeps it simple 20:55:17 and easier to write 20:55:32 arke, blockhead: although practice helped you develope your good technique for reading, that doesn't mean that if other people practice a lot they will end up with a good stratagy 20:55:55 people usually just get better at using their current stratagy 20:56:32 Herkamire: how long does it take you to read an average-sized novel? 20:57:05 5 days 20:57:26 how many hours in a day though? 20:57:32 (that you read) 20:57:49 Several months. 20:57:51 donno 5 maybe 20:58:07 so five hours per day reading, for five days? 20:58:12 I read about the spead other people read aloud. or a little slower 20:58:25 oh wow. 20:58:26 blockhead: that's my estimate 20:58:43 and it's not because I don't read much. I'm reading stuff on the computer all the time. 20:59:17 problem is I have a shitty strategy 20:59:18 turn off the computer and your reading speed will soar upwards 20:59:41 it is a distraction 20:59:52 ? 21:00:09 hard to read #forth without the cmputer on 21:00:28 oh, I was thinking in terms of reading a book. :o 21:00:57 * blockhead can't read a book and the computer at the same time. it slows me down a lot. 21:01:06 I know, but I don't see what's harder about reading from the computer 21:01:29 the fact that there are all those neat buttons to press and scrollbars to drag is an obstacle for me :) 21:01:39 I don't see either. but I jus tknow I read faster from hardcopy than screen 21:01:57 Sonarman: exactly: computers create distractions 21:01:58 Sonarman: I've done a pretty good job eliminating buttons and scroll bars 21:02:24 narrower paragraphs really helps 21:02:41 it wasn't until I was maybe 20 that I learned about good reading techniques 21:02:51 schools don't teach you how to read well. 21:03:22 they just teach you phonetics, and hope you'll develop a good stratagy on your own 21:03:42 most people develop pretty decent strategies, some very good, and some quite poor 21:04:10 if they taught good reading stratagies in school, then just about everyone would be able to speed read 21:05:16 I think it is also motivation. For example: I wanted to read before I knew how to. I used to look at comic books and stuff and want to read them. 21:05:37 Well, apparently speedreading isn't all that hard to pick up as an adult. It's a technique which can be learned. 21:05:58 I knew I was missing something cool so I wanted to learn and I practiced a lot :D 21:06:24 * blockhead remembers they used to have classes in speed reading. he remembers the ads on TV. 21:07:02 why don't they teach reading techniques in school? 21:07:03 The mental oration is the biggest obstacle, it seems. 21:07:09 why don't they teach memory techniques in school? 21:07:20 "Who's THEY?" 21:07:27 all schools 21:07:27 Herkamire: they actually tuaght us Speed Reading in sixth grade. Oddly enough, I did terribly at it :D 21:07:28 (don't you hate that... ;)) 21:07:41 Yes, memory techniques, oh how I could benefit. 21:07:53 now memory training. that I could use. 21:08:02 most people say that the hard part about speed reading is getting rid of the auditory "saying it to yourself" 21:08:16 I'm a scatterbrained forgetternaut. 21:08:18 That's how we were taught to read. 21:08:31 Yep... we sound out the words as kids. 21:08:32 we were taught to read by sounding it out 21:08:45 Then, they tell us to shut up when we get older, and that's it. 21:08:46 Herkamire, they should stop teaching kids to say it to themselves then =) 21:08:55 fridge: exactly 21:09:14 that's how they taught me to read, so that's how I read 21:09:53 why don't they just teach you to read correctly in the first place? 21:10:13 Same reason they don't teach people to program correctly. 21:10:29 humans suck. 21:10:53 schools generally teach content, and leave it completely up to the students to find a good way to think 21:11:45 Yea. 21:11:52 Not only that, each kid is different. 21:12:08 yes 21:12:10 They think differently. 21:12:46 given that the vast vast majority of people that do math visually are good at it and find it easy, and that the majority of those that don't do it visually, find it difficult, and usually do badly at it.... you'd think schools would teach the students to do it visually. 21:12:47 So some are just fine with using the most direct method for thinking, it's wired into them. Others, their minds are just all over the place. 21:12:51 but noooo 21:13:01 I suck at math, generally. 21:13:23 madgarden: me too, although if I can visuallze it, it helps 21:13:33 Yea, if I know what I want to use it for, then kick ass. 21:13:39 so I did good at geometry, until we got to proofs 21:14:21 Too many abstract details. 21:14:39 Can't translate interally into visual objects. 21:14:51 STACK UNDERFLOW 21:14:51 ok 21:16:44 --- join: Nutssh (~Foo@gh-1081.gh.rice.edu) joined #forth 21:17:24 Dobre jitro! 21:18:14 Just a question: how do you count blocks from 0 or from 1? 21:19:08 0 21:19:27 always do everything from 0 21:19:32 it makes life a lot simpler 21:19:36 yes 21:20:15 I first read about forth in an older book, it used the forth-79 standard. Everythign started from 1, even loops. Right annoying 21:20:23 Argh. 21:20:46 And 79 + 1 is what? 80. So there you go. Use 0. 21:21:11 definately use 0, 1 is right annoying 21:22:07 C programmers don't have a problem with starting at 0. but seems that Fortran, Pascal and Cobol programmers do. 21:22:17 probably visual basic too 21:22:24 madgarden: by "forth-79" I meant it came out in 1979 21:22:46 fortran and cobol are wayyyy older than c, that's why. don;t know how old pascal is 21:22:49 i was still wetting myself in 79... 21:23:03 I can't do 0 LOAD and blocks 4-5 should contain messages, so what is utility in screen #0? 21:23:06 OrngeTide: thank you for sharing :D :D 21:23:12 OrngeTide: :) I wasn't even born 21:23:12 pascal is early 70s 21:23:28 zardon: thanks. I didn't know 21:23:40 blockhead, i'm still wetting myself, but not nearly as often because of my improved bladder capacity. 21:23:45 i still lack self control 21:23:50 blockhead, yes... I know. Just me being a dork, as usual. 21:24:06 Cobol is late 50s early 60s 21:24:12 C is ~72 21:24:14 madgarden: 'k. I wasn't sure :) 21:24:25 Fortran 57 21:24:36 back to hacking~ 21:24:48 well wasn't unix like 1970? so some rough form of C was around then. 21:24:56 blockhead, get used to it from me. ;) 21:25:12 OrngeTide, C started later than UNIX. 21:25:23 not much later. 21:25:29 72. 21:25:34 okay. 21:25:35 C was the 'portable assembler' for Unix 21:25:52 C is still not much more than a glorified macro assembler. :P 21:25:53 portable my ass! 21:26:02 so unix was not orignally written in c? gasp! 21:26:04 notice the '' 21:26:10 C was never "portable assembler". It was HLL. 21:26:16 hell 21:26:24 blockhead, UNIX was written in asm. 21:26:37 ASau: I didn't know that! wow! 21:27:00 asm written on punchcards 21:27:11 but that was PDP-11 asm wasn't it? which isn't all painful like x86 or modern risc asm. 21:27:13 Read about early days of UNIX. 21:27:34 risc is not painfull 21:27:40 i just remember it had orthogonal addressing modes. 21:27:41 OrngeTide, it was PDP-6 or 7 or smth like. Not 11 21:27:58 zardon, superscalar risc is painful. 21:28:12 there isn't much point to non superscalar risc architecture. :P 21:28:19 ASau, oh. that's right. 21:28:22 I would like to look at VMS one day, but afaik there is no free version 21:28:24 i get my 7s and 11s confused:) 21:28:29 not really, if you refer to pipeline action, it can be a challange 21:28:37 fridge, you should write one. hehe 21:29:11 zardon, it's easy to write poorly performing risc asm. I've done that when writing POST code for PPC850 and 860. 21:29:11 * blockhead used VMS a while back. Fun. Only problem (for me was) the word size was like 27 bits or some odd size like that 21:29:13 PDP-11 has pretty good machine code. It's easy to program in octal. 21:29:43 OrngeTide: yes, pipeline packing can be fun :) 21:30:11 ASau: yes, evertyhign had to be octal :o 21:30:17 blockhead: VAX/11 was a true 32-bit machine. 21:30:22 MIPS is kind of a pain in the ass. i had all sorts of problems getting the instruction cache to function correctly. 21:30:38 god, VAX is horrible, CRC on memory.... 21:30:46 blockhead, it's easier sometimes to program x86 in octal rather than hex. 21:30:51 CRC? eww 21:30:54 yeah 21:30:56 kc5tja: your right. I'm sorry .. I confused the VAX witht eh DEC 21:30:57 nasty++ 21:30:59 i like ECC 21:31:10 with a nice wide word size, ECC is pretty cheap too 21:31:12 the vax was 32 bit, the dec was the odd one 21:31:27 blockhead: which DEC? DEC made quite a few. 21:31:27 * blockhead neverminds 21:31:31 The PDP/10 was 36 bits wide. 21:31:36 alpha? 21:31:46 Alpha is a 32-bit RISC. 21:31:48 fridge: check out o3one: http://www.o3one.org 21:32:04 kc5tja: I'm not sure. It's been a while. I want to say "dec-20" but I am probably incorrect 21:32:19 yeah 21:33:06 Well, so what is utility of screen #0? Why count from 0? 21:33:35 i thought the whole thrill of the alpha was that it had 64-bit addressing? 21:33:59 oh shit, thats right 21:34:02 Oops, you're right. I got confused. 21:34:04 AXP is 64 21:34:10 Sorry. 21:34:14 must be the booze:)) 21:34:15 yeah, and they messed up and put 0 after 9... idiots! 21:34:18 ASau: counting from 0 is just better. It's hard for me to explain. One time I wrote somethign in C and I made a point of coding the loops and arrays and stuff to start from 1. It got ugly. 21:34:44 try it and see how it works for you 21:34:46 :) 21:36:49 Here are details of my system. 21:38:01 I have two levels indeed: "blocks" which are supposed to be hardware addressed and "screens" which are 1K sized. 21:39:17 I can't do 0 LOAD since 0 is used to distinguish interpreting from terminal input and from screens (QUERY vs. n LOAD) 21:40:55 But I can access screen #0 through BLOCK. 21:41:36 Though it's rather hard since 0 is used to mark memory buffer free. 21:42:15 ASau: I see 21:42:27 --- join: ree (~jwm@ns.fasthost.net) joined #forth 21:42:57 What screen #0 is useful to? Should I support it (for example, in "screens in file")? That's the question. 21:43:43 * blockhead dunnos :( 21:55:04 --- quit: jstahuman ("leaving") 22:09:23 --- quit: kc5tja ("THX QSO ES 73 DE KC5TJA/6 CL ES QRT AR SK") 22:09:54 some time I'll have to ask him what that means 22:12:21 sometihing along the lines of 22:12:35 thanks for the conversation kc5tja/6 reporting out over 22:12:59 ree: :) 22:13:21 ree: you gonna use the new 2.6? (I hope so!) 22:13:26 ree: and you better not use init :) 22:13:45 oh. thanks. must something like leetspeak or something. 22:14:04 arke: what would you use instead of init? 22:14:05 * blockhead nudges a "be" after the "must" 22:14:19 Sonarman: a customized init program 22:14:24 blockhead: hamradio 22:14:41 blockhead: no, they are abbreviations used by amateur radio operators when using morse code 22:14:47 * blockhead thanks arke. gotcha! 22:15:23 :) 22:24:34 NOT EVERY KISS BEGINS WITH KAY 22:24:42 WHAT IF YOUR MOM KISSES YOU 22:49:57 I DON'T GET IT 22:50:04 XXX-CUSE ME BUT WHAT'S A KAY 22:51:06 Sonarman: guesses that arke was "singing" along with an mp3 that happend to particulary move him with its depth and brilliance 22:51:23 not even close. 22:51:36 * blockhead waits expectently 22:51:39 :) 22:52:52 Hrm.. 22:52:57 Lol 22:52:59 blockhead: do you dare insult such genius? 22:53:26 huh? 22:53:32 I think I'm gonna write a Z7 Graphics Server 22:53:39 (which is my invention :)) 22:53:44 just to run on windows.. 22:53:51 do you dare insult the genius of that music with your sarcasm? 22:53:52 :) 22:54:23 arke: Z11R7? 22:54:54 well, not having heard the song, the full effect of the brilluiance was not able to wash over me and fullfil my artistic sensibilties. :D 22:55:34 Sonarman: no, not X based 22:55:38 Sonarman: not even close 22:55:49 then you are obviously not a human, for a human would have understood its genius without needing to hear it. 22:55:51 Sonarman: this one is humanly comprehendable and does not have 8k+ functions 23:04:24 what port(s) does X11 use? 23:07:26 --- quit: Sonarman ("leaving") 23:19:18 'night all 23:19:24 --- quit: blockhead ("Client Exiting") 23:24:18 arke, less /etc/services 23:24:51 I'm not on linux right now :) 23:25:33 more winnt\system32\drivers\etc\services if MS knows about X. 23:28:20 heh 23:28:25 neither will list X 23:28:34 X is on about 6000 23:28:46 and adds to 6000 for each additional display/server 23:28:49 X is 6000-6063 or so. 23:40:22 nut.. ssh? 23:40:23 hehe 23:43:37 ree: query? 23:44:49 ? 23:45:12 ahh 23:59:59 --- log: ended forth/04.02.13