00:00:00 --- log: started retro/10.11.07 07:17:24 roarde: fixed; thanks 08:11:54 * crc is now looking into adding cover art to epub books 08:21:04 --- part: foucist left #retro 09:31:31 I backported with| and :with to 10.7.3-wip, and also the use of 'formatted' to enable/disable processing of escape sequences by 'puts' 11:12:29 --- join: roarde (~roarde@pdpc/supporter/active/sixforty) joined #retro 12:22:23 I added a quotes' vocabulary to 10.7.3-wip; this adds most of the combinators from 11.0 to the next 10.7.x release 13:46:34 What about a visible cursor when running in a browser? 13:46:58 that may be doable; I'll look into it 13:47:25 done much work on your own retro.jsf? 13:47:42 retro.jsf? 13:47:53 highlight file for joe 13:48:01 not lately :( 13:48:24 I'm working on it. Very useful project for learning retro. 13:48:38 I'm trying to figure out how to have joe show trailing whitespaces and tabs currently 13:49:17 I'll be switching back to vi, but will complete a highlight file for joe before starting on vim's. 13:49:59 At least I'll take it as far as I can go. How can I send you the result? 13:51:31 sire 13:51:38 s/i/u/ 13:51:52 there is an old vim syntax file at http://retroforth.org/get/apps/files/retroforth.vim 13:51:55 ? 13:52:06 sure 13:52:16 crc @ retroforth.org 13:52:48 sorry; still getting used to this cheap keyboard :( 13:52:57 ah. wasn't sure how you were about short attachments 13:53:56 so a new vim highlight file would be retro.vim instead of retroforth.vim, no? 13:54:04 yes 13:55:00 and if I find oodles of time, bring retroforth.vim up to 9.99 (yeah, uh . . . right) 13:55:48 it could be useful as a starting point. or maybe not. I've not used vim for any length of time in several years. 13:55:58 what do you want to happen with tabs and trailing whitespaces? 13:56:33 highlight them in some manner. in nano, I highlight tabs in blue, and trailing whitespace in green. this makes it easy to see and eliminate both. 13:57:12 what about eliminating them automatically? You now have macros :) 13:57:45 Could be done silently or prompted. 13:58:11 Do you like the highlighting you have in nano? 14:00:45 I could copy nano's highlighting to joe if I could see what you're using. 14:03:44 the nano highlighting is ok, I mostly highlight a few key words, and strings/numbers 14:04:18 you're suggesting it wouldn't be much of a guide? 14:04:22 macros could work, but it's still nice to confirm that they are gone 14:04:31 right 14:05:10 my nanorc is here: https://gist.github.com/607988 14:05:42 I'll look 14:08:38 whats .erx? 14:09:21 for unreleased code; embedding retro code into html templates 14:21:16 Going forward, is it Words.txt or Glossary.txt? 14:21:40 . . . or a player to be named later? :) 14:22:09 probably Words.txt 14:28:54 crc: is that your config for nano 14:29:22 erider: yes 15:19:29 crc: do you have a config for ed ;) 15:20:11 actually, I'm considering ed 15:20:24 or mebbe port edlin over 15:20:59 roarde: its not bad for ssh editing :) 15:21:41 erider: I decline to use ed except in rare circumstances 15:24:15 crc: why, yeah I know its a little crude but if that is all you have to use over ssh from your phone 15:25:01 erider: why would I need to edit files from my phone? 15:26:15 crc: I am talking about me :0 well I am on the go 15:26:50 I *can* use vi or nano on my phone or ipod touch if necessary 15:27:52 crc: I can too but it works flaky so I just use ed and its not bad 15:29:16 I do very little with ssh on on my phone; mostly just resetting the servers and checking logs 15:32:00 crc: yeah I can see that but when I am not at home I use my phone to test things so I have a need to be able to edit 15:33:09 erider: does your phone understand vt_ or ansi colors? 15:34:59 what would you config in ed, anyway? 15:49:24 roarde: its a iphone so yes but there are some other issues that keep me from using vi 15:51:28 right, but without color or font control, there's no point to feeding a syntax script to ed 16:02:09 really 16:03:15 I don't know I am not going to pretend that I do know, I just started using ed a little while back and its doing what I need it to do 17:00:53 Glossary.txt is renamed Words.txt in the stable-wip snapshot now 17:57:52 crc: hey can you explain something 17:58:15 what? 17:59:24 crc: you have "variableName: function(foo){ var bar = foo; }" how does variableName: work 17:59:56 what language? 18:00:14 javascript 18:00:57 I've not seen that syntax before 18:01:25 its in your BrowserDetect.js 18:01:33 I didn't write that code :) 18:01:55 presumably it'd be similar to: 18:02:10 variableName = function(foo) { var bar = foo; } 18:02:19 ah ok 18:02:21 which assigns variableName to a function 18:02:32 crc: you didn't write that code? 18:02:37 nope 18:02:58 really, I thought you wrote the js retro 18:03:03 http://www.quirksmode.org/js/detect.html 18:03:18 I wrote the js vm, but not browserDetect.js 18:05:32 crc: cool 18:05:41 stack comment for xt->d includes the character "d". I take it that "a" wouldn't do here. 18:06:15 d is an indicator of an address corresponding to a dictionary header 18:07:06 I should add that to the guide on reading stack comments 18:08:21 figured so, had to know. Using white/blue for comments, boldwhite/blue for stack comments, so I have to tell the difference. 18:08:54 * crc added this to the Reading_Stack_Comments.rst in stable-wip 18:10:32 only characters not on the list would be space, |, - afaict 18:10:55 list=table 18:11:40 - denotes before/after division, | for conditional returns (e.g., n- | n-n = takes n, returns nothing, or returns n, depending on some condition) 18:19:25 which version used C: and R: in association with stack comments? 18:19:45 10.5 or 10.6 IIRC 18:20:01 I'd like to look at a sample, so any version with it will do. Ah - thanks. 18:20:48 10.5 has C: and R: in image/source/core.retro 18:21:01 It's discontinued in favor of Compile: in Words.txt? 18:21:11 or might it come up again? 18:21:22 it'll likely come up again 18:21:32 k 18:32:43 crc: does the BrowserDetect work and how are you using it? 18:33:31 erider: it does work; I use it to adjust the simulated terminal size under firefox to account for variation in font rendering 18:34:50 if you look at the index.html, you can see how I'm using it 18:37:40 crc: ah I see that 18:37:52 TERM_WIDTH 18:41:02 yes 18:42:03 firefox renders fonts differently than opera and safari. I had to reduce the width to get the scrollbar to show up properly 18:43:20 crc: I think its neat because I have never seen that syntax before 19:01:35 nite, folks 19:01:41 --- quit: roarde (Quit: Leaving.) 22:11:53 --- join: foucist (~foucist@ps14150.dreamhost.com) joined #retro 22:11:53 --- mode: ChanServ set +v foucist 23:59:59 --- log: ended retro/10.11.07