Everytime you change something you learn something new...

, | Tweet this

It's true. Take for example this morning when I upgraded sendmail innocently on my server only to discover a bunch of things suddenly stopped working. Some of the things were things I didn't even know people were using.

Hours of tailing the maillog and poking around the sendmail site, I discovered all kinds of exciting stuff about configuring sendmail for smtp authentication that I didn't know about.

Every time I upgrade Apache, I learn all kinds of new things as well. The only thing I wished, is that it wasn't quite so trial-by-fire. Of course, for that to be the case, I would have to know everything and there's a whole lot of stuff out there that I'd rather learn posteriori rather than a priori. Otherwise, I'd just spend all my time studying things I would never have time to use.

A Deader Pan

, | Tweet this

My brother sent me this. I responded with this.

Then my brother sent me this url which allows me to make my own comics without blatantly manipulating the querystring.

So I created this.

Will the bashful Rainbow Sprites win back their pot of gold from the grasp of the evil Ice Cream Man? You decide!

Substitutes make life nicer

, | Tweet this

They really do. Case in point, take this conversation on the Necro guild line:

   Chats (last 15 of 102 available):
 
   Nabiki [19-L]: ive never played that
   Nabiki [19-L]: better get my booty to raylorn
   Rapocco [33-P]: is there an info file?
   Flamerus [13-V]: k but i need a min xplainin vamps to a friend
   Shadowhawke [Lady]: the instructions are there, it's fun!
   Saidin [Marq-V]: bah boot
   [->GUILD

One substitute command later and I now see this:

   Chats (last 15 of 102 available):
 
   Nabiki [19-L]: ive never played that
   Nabiki [19-L]: better get my booty to raylorn
   Rapocco [33-P]: is there an info file?
   two-year-old [13-V]: k but i need a min xplainin vamps to a friend
   Shadowhawke [Lady]: the instructions are there, it's fun!
   Saidin [Marq-V]: bah boot
   [->GUILD

Lyntin status: 2/17/2003

, | Tweet this

I've finished all the programming for Lyntin 3.2. I plan to release it next weekend. Between then and now if you want to grab the latest in CVS and test it out and report bugs, that'd help a great deal!

Things that Lyntin 3.2 will have:

  • new scheduler system with the ability to schedule commands to kick off at a given time
  • redid the #import stuff so it's now #load and #unload
  • refactoring of the thread manager, the datagrep buffer, the ticker (now uses the brand new scheduler), and session shutdown
  • fixed the EOR issue, #textin, #config
  • added the #grep command and removed #datagrep and #datagreplines
  • implemented the #bell command and added bell functionality to the textui

There's some neat stuff in here and some minor optimizations and fixes to documentation as well. It'll be a good release.

please....

, | Tweet this

Please make it stop snowing... please! I'm a programmer--I'm not built for this sort of thing.

Lyntin 3.1.1 released with super kung-fu #config fix

, | Tweet this

(Mark made me do it.)

It was the nicest, most informative bug report I have ever gotten. I felt obliged to release a fixed version since I've known about the bug for a month and wasn't ready to release 3.2 yet.

The only difference between Lyntin 3.1 and 3.1.1 is the fixed #config command when you don't have any readfiles or moduledirs set at the command line. Well, that and I adjusted the information in #version as well so we don't go calling two different releases of Lyntin by the same version number.

Going to California...

, | Tweet this

I'm going to California for a few days and I'm going to spend the time hanging with old friends, eating, drinking, long nights of narcisstic debauchery, and wild crazy intellectual conversations with friends like Jack and Jim just like old times.

I think it's also going to rain on Saturday. We shall see....

product vs. production

, | Tweet this

I saw a reference to this on Oblomovka.

Both are somewhat funky. I'm not sure how I feel about it but I think that Paul Ford is not correctly separating the action from the final product. I diagree with the idea that Ellen Ullman's fixation and involvement with the creation of those code blocks as part of the cohesive whole of her story necessarily contradicts her first quote. I think for her, interestingly like many artist types I know, the product is rarely interesting--to the point where they might just throw it out. It's the act of production that's so addictive.

Anyhow, Getting Close to the Machine sounds like an interesting book.

Lyntin status: 2/6/2003

, | Tweet this

I'm in some kind of Lyntin development kick again. I implemented all the changes I talked about in yesterday's email:

  • removed #import and added #load and #unload
  • fixed addCommand so that it removes a command first (and its help file)
  • changed the order of how modules get imported

Then on top of that, I wrote a testing module and started building tests for various functionality. It's not a great module, but it definitely gives me the ability to programmatically regression test large portions of Lyntin's functionality. The issue now is that I have a lot of tests to write, run, and then verify. It's somewhat time consuming. I don't plan on releasing 3.2 until I get a significant number of tests done and verified.

Additionally, I worked out how I want to handle the config stuff. I still have to write it out and fill in the details. I want to release 3.2 and get some other things cleaned up before I start on the config stuff.

So while the lyntin-devl list is deathly quiet, there's definitely stuff happening.

Brief Lyntin break (or was it?)

, | Tweet this

Last week I took a break from Lyntin development and I'm probably not going to do much this coming week either. Having said that, I made some minor changes last week including:

  • moved the databuffer to the session class, ditched datagrep and datagreplines commands, and added a grep command (with context flag)
  • removed the threadmanager
  • gave some good thought to the config system

Then Josh implemented his default argument code for the argparser which is extremely cool though I'm not entirely sure we should be storing those kinds of things in the variable manager.