configs

This message has 1 attachment(s)

Those are actually the wrong way around (probably my fault for explaining badly) - config() gives the right names, but in the help (help @config tiny, and help @config chan, I think) the names are shown incorrectly.

Actually... I wrote this from doing...

think iter(config(),ljust(%i0,26) config(%i0),%b,%r)

and describing the results.

config() does actually generate wrong names.

On 1/20/07, Penndev <pennmush-bugs@pennmush.org> wrote:
>
> #7176: configs
>
> ---------------------------------------------------+------------------------
>   Reporter:  "Chuc McGuire" <nemosolid@gmail.com>  |       Owner:  devteam
>       Type:  incoming                              |      Status:  new
>   Priority:  minor                                 |   Milestone:
> Resolution:                                        |    Keywords:
> Visibility:  Public                                |
>
> ---------------------------------------------------+------------------------
> Comment (by Talvo):
>
> Those are actually the wrong way around (probably my fault for explaining
> badly) - config() gives the right names, but in the help (help @config
> tiny, and help @config chan, I think) the names are shown incorrectly.
>
> --
> Ticket URL: <http://dev.pennmush.org/ticket/7176#comment:2>
> Penndev <http://www.pennmush.org/dev/>
> PennMUSH Development
>

Replying to Chuc McGuire:

Hrm, strange. config() reports both of those fine (as max_player_chans and tiny_trim_fun) on my test game (1.8.1p9). Can't connect to M*U*S*H atm to try it there, though, it seems to be down. It's only the help-files where I see a problem for those two.

I just tried this piece of code, and it was more than just those 2 that came up as errors.

I am using Penn 1.8.2p1, and the following came up as errors:

• sql_username
• sql_password
• sql_database
• max_global_fns
• log_wipe_passwd

However, 'max_player_chans' and 'tiny_trim_fun' were indeed spelt correctly and produced no error.

And yes, SQL is defined on my game.

The SQL and log_wipe data is filtered out for security reasons and it is unlikely this will be changed.

The max_global_fns option returns an error because it is not in a category. Since there seems to be no serious security concerns regarding it, I'll place it in the limits category.

There's a comment in mush.cnf that says you should @shutdown/reboot immediately after changing max_global_fns, and it looks like it only allocates enough memory on restart for however many @functions the option is set to - so increasing it in-game and adding more than the original setting's worth of @functions would probably crash the MUSH?

WRT the config options ray mentioned.. Maybe it would be better if config() didn't list options which you can't see the values of from inside the MUSH/which aren't in a category (I think those two facts are one and the same)?

It may be worth considering a change in the config() code to have it exclude those options that can't be viewed with it in any case. This is something for some point in the future.

config() no longer lists items with an empty group. Also fixed a buglet where there was an extra space at the end of the returned list.