Re: Re: linesep char

I don't use any other mud clients and haven't for years.  So someone else
will have to build a matrix.  I think it'd get messy depending on what we
were tracking since in a given family of mud clients there's some serious
theme-and-variations going on.

I sort of like the compatibility module idea, but I think that's something
that should wait for 5.0.  I'm pretty sure we can't shoe-horn that into
4.1 without some serious architectural changes.  That's a first-blush
guess though.

Even so, it might be a good idea to toss some items in the FAQ along these
lines:

   Q: How can I make Lyntin act more like TinyFugue?
   A: You should do the following:

      1. install module xyz
      2. set the following items in your ini file:
         commandsep: %;
         ...


In regards to your config question, it turns out it's a goof on my part.
The commandchar needs to be a string, but when we're reading stuff in we
read it in as a list by default.  So we just need to convert it back to a
string.

There's a couple of lines in engine.py that look like this:

    for mem in ["datadir", "ui"]:
      if type(config.options[mem]) is list:
        config.options[mem] = config.options[mem][0]

If you add "commandchar" to the list in the first line, then that'll fix
the problem.  I'll add it and commit the changes now.  I'll go through the
other core config options and make sure they work correctly as well.

Sorry bout that.

/will


On Mon, 19 Apr 2004, Paul Jimenez wrote:
>
> On Monday, Apr 19, 2004, will guaraldi writes:
> >
> >Oh--oops.  I didn't mean to be a jerk or anything.  I'm just saying
> >I've got too much to do, this has been on the wishlist for a long time
> >and I haven't done it yet--it's the sort of thing that has fallen by
> >the wayside.
>
> No wories, no offense taken :)  That's the way open source works... if
> everyone scratches their own itches, eventually everything gets taken
> care of.  The current behavior bugs me because I'm not used to having to
> escape ;'s in the course of normal output, so I'm more than willing to
> put in the effort to fix it.
>
> >Mmm...  configuring the escape character as well gets a bit messy.
> >I've had both camps yell at me for this.  One camp wants to be able to
> >configure things like whatever client they used before.  The other camp
> >wants Lyntin to be smaller and less bloated and they don't really care
> >about configuration.
>
> So maybe some kind of compatibility matrix is in order?  I've only ever
> used emacs and tf as mudclients... Hrm.  Maybe the real Right Thing
> (which probably has to wait until 5.0) is to make it all modular, so you
> just choose the right set of modules to do your filtering and you can
> get whatever behaviour you want.  Oh, and that's something else for 5.x
> - a way to configure which modules get loaded instead of blindly loading
> everything in your modules dir. (though I guess _* modules work this way
> now)
>
> >I would say hold off on configuring the escape character--that's a big
> >project which involves more than just a patch.  I'd just fix the
> >SEMI_REGEXP so that it's configurable with the default being to use ;
> >as the command separator.
> >
> >The command char is configurable--I would look at that and see if you
> >can't do something similar.
>
> Hrm, yah, this looks like a can of worms; I may just hold out for the
> 5.x redesign.
>
> Speaking of 'configurable'... did you ever get a chance to figure out
> what you can and can't set from the .ini file vs. having to use the
> readfile?


-------------------------------------------------------
This SF.Net email is sponsored by: IBM Linux Tutorials
Free Linux tutorial presented by Daniel Robbins, President and CEO of
GenToo technologies. Learn everything from fundamentals to system
administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click