Re: configuration persistence?

I just checked my ini file and command file and it turns out I do most of
my configuring in my command file.  I had thought I had set it up so that
you could do things in the ini file as well, but maybe I didn't.  I'd have
to go look at the code and trace commandchar through it.

You can read in files with the "readfile" property in your ini file.
That will read a command file in upon Lyntin startup.  The first
non-whitespace character in that file will become the new commandchar.

/will


On Thu, 15 Apr 2004, Paul Jimenez wrote:
>
> Yeah, I'd found the 'commandchar' variable, but setting it
> in my .ini file doesn't work.  When I try it, then start
> up lyntin, I get:
>
> #config
> lyntin: Commandline:
> lyntin:    commandchar      /
> lyntin:    datadir          /home/pj/.lyntin/data/
> lyntin:    moduledir        /home/pj/.lyntin/modules
> lyntin:    readfile         (None)
> lyntin:    snoopdefault     1
> lyntin:    ui               text
> lyntin: Global:
> lyntin:    ansicolor        on (bool)
> lyntin:    commandchar      '#' (char)
> lyntin:    datadir          '/home/pj/.lyntin/data/' (string)
> lyntin:    debugmode        off (bool)
> lyntin:    mudecho          on (bool)
> lyntin:    promptdetection  off (bool)
> lyntin:    repeathistory    on (bool)
>
> Note the double definition of 'commandchar'. My ini file looks like:
>
> [Lyntin]
> datadir:   /home/pj/.lyntin/data
> moduledir: /home/pj/.lyntin/modules
> commandchar: /
>
> Is there a way to specify a file to be /read on startup?
> Then I could just put '#config commandchar /' in that file.
>
>   --pj
>
>
> On Thursday, Apr 15, 2004, will guaraldi writes:
> >
> >There's no way to write out the configuration information.  Just add it to
> >your ini file by hand.  The config property for the command character is
> >"commandchar".  You can tell by starting up Lyntin and typing
> >"#config"--this will list all the ocnfig properties that are currently
> >present and what their current values are.
> >
> >Then you can type "#config commandchar" and it'll give you a bit more
> >description.
> >
> >There's more help in "#help config".
> >
> >Hope that helps--
> >/will
> >
> >
> >On Thu, 15 Apr 2004, Paul Jimenez wrote:
> >>
> >> I'm probably missing something, but I can't figure out how
> >> to write out my existing configuration to a .ini file, and
> >> I also can't figure out what the variable name in the config
> >> file is to set my commandchar.  Thanks for any help!
> >>
> >>   --pj
> >
> >
> >-------------------------------------------------------
> >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
> >_______________________________________________
> >Lyntin-devl mailing list
> >[email protected]
> >https://lists.sourceforge.net/lists/listinfo/lyntin-devl
> >
>
>
> -------------------------------------------------------
> 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
> _______________________________________________
> Lyntin-devl mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/lyntin-devl
>

-- 
whatever it is, you can find it at http://www.bluesock.org/~willg/
except Will--you can only see him in real life.


-------------------------------------------------------
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