00:00:00 --- log: started forth/08.10.09 03:19:05 --- nick: Malfermi1aKodo -> Malfermitakodo 06:04:08 --- quit: nighty__ (Remote closed the connection) 07:05:50 --- quit: nighty^ ("Disappears in a puff of smoke") 07:06:20 --- join: nighty^ (n=nighty@x122091.ppp.asahi-net.or.jp) joined #forth 08:13:01 --- join: uiu (n=ian@HSI-KBW-085-216-030-033.hsi.kabelbw.de) joined #forth 08:27:50 --- join: pierre- (n=pierre@89.179.92.9) joined #forth 08:32:30 --- quit: Quartus__ (Read error: 110 (Connection timed out)) 09:08:48 sould I lean factor? 09:08:58 What for? 09:09:35 write script for daily use 09:09:47 What prevents doing it in Forth? 09:10:35 dont know :( 09:10:47 Better learn how to do it in Forth. 09:11:09 hoho,it seem a big libs 09:11:16 When you find easy way, you'll understand, that it doesn't differ in any way. 09:11:28 You don't even need huge libs for that. 09:11:59 Actually, writing your own bindings for Factor and for Forth hardly differs much. 09:12:29 reading TF,it made me faint,Im leaning new thing 09:12:36 oh 09:14:01 Thx U for your words :) 09:15:32 I have one-liner script in my ~/bin to simplify starting of Forth-written scripts: 09:15:54 exec gforth init.fs "$@" 09:15:57 Hm. 09:16:00 That's a bug. 09:16:14 It should be ${1:+"$@"} 09:16:20 Obviously. 09:17:23 ha! 09:18:02 And, of course, I set GFORTHPATH appropriatly, 09:18:10 this is done from .profile 09:18:20 well 09:18:50 how many years U use forth? 09:19:38 I think, 5 or 6. 09:20:00 WOW 09:20:46 Take good advice, save your time. 09:21:14 If you're going to continue using Forth, just start writing useful programs in it right now. 09:21:36 Unfortunatly, nothing teaches you except experience. 09:21:42 Especially in Forth. 09:22:00 take that to my nots 09:22:07 notes 09:22:20 And you ought to write programs useful to _you_ personally. 09:23:02 Otherwise you're losing time on shell, perl, and other crap. 09:24:13 well,do that shell should do in Forth? 09:25:15 Yes. 09:25:49 Try writing you scripts, which you'd write in shell or perl, in Forth. 09:25:54 Its hard,but made me think and learn :) 09:28:30 exec gforth init.fs ${1:+"$@"} 09:28:37 right? 09:30:09 Yes. 09:30:22 gogonkt@andLinux:~$ ./forth 09:30:23 *the terminal*:0: File I/O exception 09:30:23 Backtrace: 09:30:23 $B7A2F868 throw 09:30:23 $B7A2E1E8 required 09:30:24 $1 09:30:27 buggy 09:30:49 Do you have that "init.fs" file? 09:31:02 where it it? 09:31:18 Somewhere in your GFORTHPATH. 09:31:31 Read info how gforth starts. 09:31:42 you write that? 09:31:49 Yes. 09:31:54 all right 09:32:49 E.g. export GFORTHPATH=${HOME}/forth:`gforth -e "fpath .path bye" | sed "s/ $//;s/ /:/g"` 09:32:58 Hm. 09:33:04 I should rewrite it in Forth. 09:37:20 init.fs for mine word? 09:38:27 Yes. 09:40:48 yes,in my ~/ 09:41:01 yes,in my ~/init.fs 09:43:03 done :D 10:05:13 --- join: josef_pauli (n=jp@frotz.zork.net) joined #forth 10:16:07 --- join: JasonWoof (n=jason@c-65-96-160-164.hsd1.ma.comcast.net) joined #forth 10:16:07 --- mode: ChanServ set +o JasonWoof 10:16:31 --- join: Quartus` (n=Quartus`@74.198.12.3) joined #forth 10:16:54 Pauli? 10:17:00 Will we see Bohr here? 10:17:27 Always Pauli and Bohr. Everyone forgets about Rutherford. 10:17:39 Nah. 10:17:48 Rutherford did less. :p 10:20:26 :) 10:20:45 ASau: some one had registered jp before I arrived; I came for help with gforth's general files words 10:30:18 --- join: forther (n=forther@207.47.34.100.static.nextweb.net) joined #forth 10:32:07 * josef_pauli greets forther : may be you have experience with gforth's general files wordset 10:35:03 * josef_pauli stumbles at gforth's file-fu: create-file, flush-file, write-file, close-file & such; 10:35:07 using linux' follow: tail -f 10:35:09 ... after: ls >> 10:35:12 ... tail shows concatenation 10:35:14 gforth's write-file seems not to alert tail of its concatenation 10:35:17 ( even though I can read the file) 10:35:19 ... some times querying file-position awakens tail to write-file's work 10:35:22 ... 0 0 test-file resize-file ( almost) always gets tail's attention 10:36:43 do you have \n -s in your gforth output? 10:46:39 I type: s" some text" test-file write-file 10:46:39 ... I recognise /n as newline; I might use it instead of file-emitting 10 & 13 10:46:39 ... which I did not try, except after initial failure 10:46:39 please ?what is-s 10:49:38 multipple \n 11:07:20 * josef_pauli files -s ( thx) 11:07:43 now to try -- during next break 11:10:20 see newline 11:10:24 newline type 11:10:40 This works across posix-canonical border. 11:11:19 Use "flush-file" to flush buffers. 11:11:48 * josef_pauli notes downrightly struck slash before n 11:13:34 tail: "Print the last 10 lines of each FILE to standard output." 11:13:34 ... how ever many lines, may be only completed lines 11:13:34 * josef_pauli hopes for a simple leap forward 11:13:34 ... thankful & hopeful I 11:14:10 ASau: I had tried flush-file, but I didn't see tail following 11:14:46 I've lost the track then. 11:14:53 Retransmit. 11:15:00 Hrm. 11:15:05 Elaborate. %] 11:27:14 --- quit: Malfermitakodo (Read error: 104 (Connection reset by peer)) 11:27:26 --- join: Malfermitakodo (n=kansu@xdsl-78-34-130-153.netcologne.de) joined #forth 11:47:21 ASau: $JOB has most of my attention 11:47:24 I had tried using "tail -f " to record my use of: 11:47:24 s" some text" test-file write-file 11:47:24 ... even though "less test-file" showed the text I'd written 11:47:24 ... tail were not following 11:47:24 re-reading "man tail": I conclude that tail follows only completed lines 11:47:26 ... and that including "\n" to a string's end will let write-file alert tail 11:49:39 Use "write-line". 11:49:45 Then. 11:49:53 ? 11:53:25 --- quit: mark4 ("Leaving") 11:55:26 * josef_pauli will try write-line, thanks 11:55:28 www.complang.tuwien.ac.at/forth/gforth/Docs-html/General-files.html#General%20files <-- may be there's a page like this with more commentary 12:05:19 --- quit: pierre- (Read error: 110 (Connection timed out)) 12:07:57 --- join: mark4 (n=mark4@wsip-68-14-227-113.ph.ph.cox.net) joined #forth 12:22:56 josef_pauli: most of words there are described in the standard. 12:23:28 josef_pauli: since the draft is publicly available, that's not needed. 12:23:55 josef_pauli: upcoming standard is going to be MIT or BSD licensed, AFAIR. 12:31:21 http://www.bellevuelinux.org/mitlicense.html <-- permits privitization of value-added opensource 12:34:24 AND THAT IS GOOD. 12:37:25 value connotes benefit 13:10:43 --- join: forther_ (n=forther@207.47.34.100.static.nextweb.net) joined #forth 13:11:21 asau they are going to license the set of words that the standrd defines? therefor if your app uses ANY words defined in the standard YOU have to apply their license to your code? 13:11:53 i call bs on that one lol 13:18:28 --- quit: forther (Read error: 110 (Connection timed out)) 14:46:12 --- quit: qFox (Read error: 104 (Connection reset by peer)) 15:44:39 --- join: tathi (n=josh@pdpc/supporter/bronze/tathi) joined #forth 15:44:39 --- mode: ChanServ set +o tathi 15:47:55 http://www.taygeta.com/forth/dpans11.htm <-- optional file-handling words with commentary 15:55:33 yup 15:56:15 Did you solve your problem, then? 16:13:16 --- join: maht_ (n=maht__@85-189-31-174.proweb.managedbroadband.co.uk) joined #forth 16:16:17 --- part: forther_ left #forth 16:19:50 --- quit: maht (Read error: 110 (Connection timed out)) 16:23:52 tathi: to the extent that I can reliably write & read files, yes 16:23:52 ... I wanted, though, to drive irssi with a text-file 16:23:52 "irssi -c irc.freenode.net < test-file" would not start 16:23:52 ( in a channel on slashnet.org) 16:23:52 23:59 <%Screwtape> jp: irssi might contain code that (deliberately) explodes if stdin is not a terminal. 16:23:55 00:03 <%Screwtape> In fact, that code might just be ncurses (or slang, or whatever irssi uses) 16:23:58 ... boo-hoo 16:24:01 but I can reliably write & read files 16:24:04 ... a chat-bot might not come so cheaply interfaced as I'd hoped; but may be soon some thing other 16:26:17 Ah. 16:26:24 IRC is pretty easy to do. 16:26:35 Have you seen Marcel Hendrix's minimal IRC client in Forth? 16:27:31 links? 16:28:32 don't remember: googling... 16:29:13 Isn't that client still in occasional development? 16:29:44 I dunno if he's doing anything new with it. 16:30:05 He pops in here with it occasionally, though I don't think I've seen him for a while. 16:30:08 http://home.iae.nl/users/mhx/pipes%26socks.html 16:30:10 probably here 16:30:34 He may have posted the code to c.l.f. also, I'm not sure. 16:34:42 --- quit: xjrn (Read error: 104 (Connection reset by peer)) 16:41:44 --- quit: maht_ (Read error: 110 (Connection timed out)) 16:42:03 tathi: me follows link, and forsees a very many arguably simple steps... but thanks tathi for path-finding 16:45:14 or you could look at the isforth irc bot lol 16:45:48 --- join: maht (n=maht__@85-189-31-174.proweb.managedbroadband.co.uk) joined #forth 16:48:48 http://www.wlug.org.nz/Forth <-- mark4 : "The next example is a utility word from the IRC bot in ISForth." -- steps, thanks 16:54:25 behind wanting ez-access to irssi ( on account of its ez-access to ssh), I wanted a game-bot that would 16:54:28 ... create & maintain a game-space 16:54:31 ... register players 16:54:33 ... interpret players chat as play 16:54:47 ... report on game 16:54:47 s/players/players'/ 16:58:15 mark4: oops, forgot about isforth. :) 16:58:40 wait, have you put up a new site for isforth yet? 16:59:42 oh, orangetide has it 17:01:07 irc is very easy 17:01:11 I did it in perl from scratch 17:01:55 i have a friend who will host it and HIS machine is actually hosted by forth inc lol 17:02:28 but ive not worked on a new site yet, was thinking of learning php and making a decent site for it.... 17:04:20 josef_pauli: you want a chat room that is a game? or just private /msg with the bot? 17:13:04 JasonWoof: the bot might keep separate spaces in different rooms, or multiple games in a single room -- it would be the bot keeping score; chat's just an interface to the game 17:20:41 josef_pauli: have you seen #idlerpg ? 17:21:12 heh 17:22:43 http://idlerpg.numist.net/newdlebot/ 17:39:53 JasonWoof: years ago, when I had more-reliable access to internet, I rose to a single-digit rank 17:40:20 ... I want, though, a game that would reward "play" 17:50:07 hehe 17:56:11 * josef_pauli applies his laser-like focus to the game-end for a while ( manyana, may be back -- again, thanks) 18:08:51 --- quit: tathi ("leaving") 19:16:51 mhx's irc client? whait... 19:25:29 I had download it at http://home.planet.nl/~josv/msources.html 19:26:28 itools2 at mhx site is more new I think 19:39:03 http://home.iae.nl/users/mhx/pipes%26socks.html 21:06:43 --- join: nighty__ (n=nighty@210.188.173.246) joined #forth 21:36:15 --- quit: Quartus` (Read error: 110 (Connection timed out)) 21:39:50 --- join: LOOP-HOG (n=jasondam@97-115-74-118.ptld.qwest.net) joined #forth 21:40:36 hi 21:42:32 anybody home? 21:42:40 yo 21:42:58 I am in a weird mood 21:43:30 what is going on with you? 21:44:16 eating a late dinner 21:45:03 I already ate 21:45:12 I am about ready to write a proposal for a website project 21:45:17 the thing is, this lady is nuts 21:45:44 What do you think about the economy? 21:53:34 --- quit: JasonWoof ("fiddling with bootables") 22:07:10 oh, the economy can't be doing too bad if we all still sitting on our butts infront of a computer and we still have food to eat. 22:07:11 lol 22:07:16 --- quit: LOOP-HOG () 22:33:07 --- join: ygrek (i=user@gateway/tor/x-ae77d2a8d0f85a48) joined #forth 22:44:57 --- join: pierre- (n=pierre@89.179.92.9) joined #forth 23:21:30 --- quit: ygrek (Remote closed the connection) 23:24:41 --- quit: ASau (Read error: 113 (No route to host)) 23:26:34 haha 23:26:44 ate lunch 23:36:44 --- join: ygrek (i=user@gateway/tor/x-cf0bf1c521fc5a60) joined #forth 23:59:04 --- quit: Malfermitakodo (Read error: 60 (Operation timed out)) 23:59:59 --- log: ended forth/08.10.09