00:00:00 --- log: started retro/10.10.30 05:55:18 good morning 07:34:28 crc morning 07:34:45 crc: you still using google chrome 07:34:47 I'm working on documentation again 07:34:58 erider: chrome at work, opera at home 07:35:28 crc: no more firefox for you? :) 07:36:54 only for a couple of sites 07:37:53 crc: so you are rewriting docs? 07:38:21 yes. the last major update was a year ago; it's well overdue 07:38:56 lol yes I would say so 07:39:09 q 07:39:16 ask away :) 07:39:34 sorry wrong window I was typing in ed 07:39:39 ok 07:40:30 i had planned to work on the docs last night, but got distracted with a block editor (http://gist.github.com/654790) 07:41:46 yeah I saw that yesterday cool stuff you are doing with retro and scoping 07:43:18 crc: pretty soon I guess you will be working on closures in retro :) 07:44:06 maybe; I've not needed full closures yet 07:44:57 crc: has the scoping been useful well never mind I guess it is obvious that it has :) 07:45:58 * erider wonders what the future of browsers are and if he should get into javascript 07:51:08 js is worth learning 07:53:09 yiyus: I switched +times to iter and -times to iterd, thanks for the suggestion 07:57:12 maybe, hey are you off today crc? 08:08:00 yes 10:57:50 --- join: roarde (~roarde@pdpc/supporter/active/sixforty) joined #retro 11:27:11 --- quit: roarde (Ping timeout: 255 seconds) 11:29:40 --- join: roarde (~roarde@pdpc/supporter/active/sixforty) joined #retro 11:37:28 http://gist.github.com/655290 11:43:15 this is the current state of the documentation rewrite. 11:44:22 what's a good source for rst2html.py? 11:44:53 it's part of docutils. see http://docutils.sourceforge.net/ 11:46:46 an older (0.5) docutils is pre-packaged; I'll try it 11:56:27 I use 0.5 on my mac; it works ok 12:07:41 --- join: JohnnyL (excellent_@ool-18b87a54.dyn.optonline.net) joined #retro 12:07:47 are you leaving out metadata such as "title" to make it more readable as .txt, or have I once again gotten a mis-configured package? 12:07:58 Anyone know if it's possible to put a 360k floppy drive into a modern pc? 12:08:14 roarde: the metadata should be there IIRC 12:08:31 oh 12:08:38 JohnnyL: I'd doubt it 12:08:40 forth is what you guys speak here? 12:09:11 I'm trying to remember what the floppy floppy connector to the control card looked like 12:09:29 it had that twist in it, no? 12:09:34 yup 12:09:53 twist isn't necessary if you have only one drive 12:11:29 I'd assume that bus timings and such would cause problems with trying to actually use one in a fairly recent system 12:12:35 hm, i bet there is a floppy controller in pci format somewhere. 12:12:52 I know CatWeasel can do it, but you have to make mods to your 'recent' floppy drive. 12:13:06 that and it's $99 12:13:18 since I don't have a job, i'm trying to take the cheap route. 12:13:32 you might do better to modify an old usb floppy drive. some of the early ones had fairly standard floppy controllers inside 12:14:01 what's on those floppies? Might be easier to d/l the original files. 12:14:28 well, I wanted to use the floppies burnt on a new system to use on a retro pc 12:15:39 if it has a hd, sending the data by serial may work 12:16:55 writing will be more problematic than reading 12:16:57 not a bad idea. although I envisioned the retro machine far from the original pc. Because I already have a retro amiga here. 12:34:03 crc: What I'm getting is Title, Author, Version at top of page; looking for Title in title bar, not getting it 12:42:45 --- quit: JohnnyL () 12:55:47 crc: .. title:: Welcome to Retro 12:56:14 Is metadata, thus different from :Title: 13:40:37 ahh, I never bothered with the .. metadata; I mostly use ReST for editing ebooks; not html and have a set of scripts that build the metadata for the ebooks from the :Title: and similar elements 13:44:03 rst2html.py will accept metadata in command line options, if you want to leave it out of the rst source 13:44:34 have to lie down for a while 13:44:38 --- quit: roarde (Quit: Leaving.) 14:30:43 crc: are you still writing the language concept? 14:31:25 yes 14:34:42 it has more flow control stuff coming, and I haven't even touched on the dictionary model or word classes yet 14:34:48 or macros 14:36:25 * crc will be back in 1 - 2 hours; I have to run an errand for my wife 16:59:59 --- join: roarde (~roarde@pdpc/supporter/active/sixforty) joined #retro 17:24:25 back now 17:24:46 roarde: I added a title metadata to the file 17:25:48 won't interfere with present or future scripts? 17:25:55 no 17:31:43 I also added the rest of the major conditionals to the table 17:35:55 I'll have to learn to use git. Content tracking is still a new item for me. 17:46:57 I mostly use fossil now, but haven't taken time to setup anything like github's gist service using fossil as a backend yet 17:47:40 I'll have to package fossil. Not in OS repo, and I prefer installation from package. 17:48:14 Actually looking forward to it; it'll be way easier than the deb-originated crap I've been trying to package. 17:49:37 Is there a machine you work from that doesn't have some flavor of vi? 17:50:29 I'm looking for a way to script macros for nano. 17:50:35 I use an AIX box with a really crappy, ancient vi 17:50:45 I don't know of any macro support in nano 17:51:00 Right. But won't nano run a shell command? 17:51:29 In other words, you don't use vi or whatever -- the script does. 17:53:20 Oops, I assumed. Apparently, can't do shell command. 17:53:58 Hopefully, I'm telling you what you already know, but you must pick another editor. 17:54:10 I know that's not fun to do. 17:58:51 agreed; it's just a pain to learn a new one. inertia sucks. as do nine years of finger memory/reflexes on key bindings. 17:59:16 good reason to choose carefully 18:00:13 and to make it a real pain, your choices are fewer as you need something often already on the system, or at least very highly portable 18:00:21 preferably any editor I move to will support osx, linux, netbsd, and aix, and allow me to emulate at least some of nano's key bindings. I dislike editing in a modal environment for general things, and emacs is too heavy. 18:01:00 crc: try the command "jpico" 18:01:46 that looks promising 18:02:38 I'm not actually a joe fan, just trying to think of what's powerful and near to what you prefer. 18:09:02 --- quit: roarde (Ping timeout: 255 seconds) 18:35:26 --- join: roarde (~roarde@pdpc/supporter/active/sixforty) joined #retro 18:36:00 * crc is working on a syntax highlighter for retro for use with jpico 18:36:29 :) I take it you're glad to find jpico 18:36:37 yes 18:36:55 once I get this finished, it should work ok in place of nano 18:37:02 I've gotta mount an external antenna for wifi so I can quit getting cut off. 18:37:53 --- join: foucist (~foucist@ps14150.dreamhost.com) joined #retro 18:37:53 --- mode: ChanServ set +v foucist 18:42:18 --- quit: foucist (Client Quit) 18:48:17 I'm going back to NetBSD. 18:48:34 I'll build it with pcc and custom configure. 18:49:10 In the meantime, I'm going to drop all the stuff I'm doing with/for current distro and start in on retro. 19:03:43 crc (or anyone): It's extremely likely that retro will be what I stay with, and I'm willing to dig in . . . 19:03:55 cool 19:04:05 but in that light, is there another forth I should start with in order to learn retro? 19:04:34 that is, learn forth first, then retro, or go straight to retro? 19:05:04 not really. outside of the core stack primitives, too many other things in retro differ from the more mainstream forths 19:26:53 --- quit: roarde (Ping timeout: 255 seconds) 19:30:40 --- join: roarde (~roarde@pdpc/supporter/active/sixforty) joined #retro 19:32:06 http://gist.github.com/656037 is an initial syntax highlighter for joe/jpico; works well enough to cover strings, comments, constants, and a couple of the primitives 19:33:08 I may try jstar for a while and catch up with vi in the long term. 19:42:23 has "Glossary.txt" changed to "Wordlist.txt"? 19:42:39 only in the repo; not in the actual release 19:43:00 considering it for later releases? 19:43:07 possibly 19:44:20 "glossary" may be denoted as "stuff you may wish defined", i.e., more than just "words" 19:44:48 true 19:45:02 "wordlist" is better; "dictionary" would be best, but of course you can't do that 19:51:32 I can change the filename for 10.7.3 and beyond. I have no real loyalties to any of the filenames :) 19:54:58 just something to consider. I'm following retro rather than rolling my own mainly because you make better choices than I do :P 20:55:36 just about midnight, so I'm going to try to get some sleep. I posted a general summary of the last week's coding to corpse; though I forgot to cover the new "each" combinators; I'll do a post on them tomorrow or monday. 20:55:41 goodnight everyone 20:55:51 nite, crc 21:41:06 Glossary.txt? Wordlist.txt? Perhaps just "words.txt". Its being a text file should both distinguish references to it from the words command, and the name.ext should identify what it is for those who know forth but maybe not retro. 21:57:15 or "Words.txt" to distinguish it further and lessen the likelihood of a typo having ill effects 22:01:42 --- quit: roarde (Ping timeout: 255 seconds) 23:16:19 --- join: roarde (~roarde@pdpc/supporter/active/sixforty) joined #retro 23:59:59 --- log: ended retro/10.10.30