>>>Now apply beautify or whatever and introduce some whitespace before the *!*:
>>>
>>>

>>>   *!*	* test
>>>   *!*		* test
>>>   *!*			* test
>>>   *!*	* test

>>>And now try to uncomment from the rightclick menu. It won't (just tried again, wishing I was wrong), and that's why my beautifier won't indent comments, AFAI'm concerned.
>>
>>Ahh, that's the difference is beautify (or leading spaces). I rarely, if ever use it, I just write gorgeous code right from the start. <bg>
>>
>>Beautify is part of the XSOURCE code, so I guess it could be fixed if it's that important.
>
>I thought it wasn't, because I couldn't find it. Now you made me look again and it seems to be one of the two or three that I didn't unzip before.
>
>...too bad, can't change a thing, no se habla C++. Here's what it says in beautify.prg:
>
>* Main entry point for Beautify.APP. The purpose of Beautify.app is
>* to wrap FD3.FLL in a private data session so that its table
>* manipulation routines don't disturb the user's environment.

So it is. Don't see why you couldn't "pre-process" the source file yourself to remove or change the leading spaces before you let beautify have a go. Or "post-process" it after beautify has had it's way.