Column width adjustment of wwho display

Hello all,

I've been about before, but not for a long while, so the answer for this might be idiotically obvious. For this I ask forgiveness. But here is my problem anyway.

I an on Tapestries, with a fully-up-to-date version of MushClient (5.05) and the annoying thing is a WS command has set column widths that often truncate longer sexual settings (name/idle/sex/species)

Is there something I need to run client-side to have this adjusted properly? There are alternate WWHO fornats available, but none allow for column width adjustment.

Severly frustrated,
WhiteWolf McBride
Resident WoofieMage.

Sounds like a server-side thing to me. I assume you made the client width wider? Is the data truncated, or just so long that it doesn't display properly?

I'm not sure how to adjust the display for that in MushClient, and have been told by a wizard that he doubts it can be adjusted muck-side. I ~have~ set the width of the whole display so its got lots of room (120 columns) so it seems like its set on their side...

I just copied a few lines of a WS into Notepad, so I could see the display in a set-width font. Here is what I discovered.

(name=21 char + 1 space)(sex=9 char max + 1 space)(species)

- idle time is placed 2 spaces before sex, and subtracts from the name buffer. Eg. Idle of 12m would allow only 16 spaces for a name. ('Name'=16 + space + '12m' + 2space)

- if their sexual designation is more than 9 chars, it gets truncated to 9 chars. Eg. 'Effeminate male' would be chopped to 'effeminat'.

Can I intercept the data and have MushClient adjust the columns? Or do I have to beg the wizards to tweak the column widths?

If the data isn't being sent, then there is no way you can display it, except maybe looking for specific words like that and replacing them.

Maybe there is a MUCK configuration option you can use to widen the columns. I don't know why the wizard would say it can't be adjusted if they are specifically truncating it. They are probably doing a print with widths limited so the columns don't get out of line.

Maybe you can go about it another way, for example getting people's sexual designation another way (eg. some other command), store that in a table somewhere, and then re-assemble the WHO output by discarding their column and substituting yours.