Yes, -M will handle chopping text at tab stops, but isn't necessarily what you want unless you don't care about seeing all of your text. I think it's better to use enough tabs to guarantee the text is aligned properly without truncating text, which is what I mentioned. Now, depending on the network, the max nick length may be low enough to not be a problem. But on other networks, one tab may not work.

Below is an explanation of what I was talking about regarding use of multiple tabs.

//aline @test 1234 $chr(9) $chr(9) $+ 1234

See where the second set of numbers are. Now, use a number that is too long in the beginning...

//aline @test 12345678901234567890 $chr(9) $+ 1234

Notice that it does not tab to the next tab stop, but instead just adds a couple spaces. It will not align that way.

Now, try it with two $chr(9)'s...

//aline @test 12345678901234567890 $chr(9) $chr(9) $+ 1234

It now aligns properly.


Notes:
* The $+ is just to remove the space following the tab so the number appears at the tab stop instead of one space later.

* I'm testing this on 6.35 as I don't have 7.19 installed at work. It is possible that it may have been changed since then.

Last edited by Riamus2; 06/10/11 05:03 PM.

Invision Support
#Invision on irc.irchighway.net