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

I've actually grown accustomed to comments not indented, so I'm writing them just as wide to fit. If they were indented, they may reach too far - and like I said yesterday, any code that needs to be scrolled horizontally when posted on UT is ugly.

IOW, I'm happy with it as it is. It may be a bug (which won't be fixed, ever - the FD3 code in XSource is from 2001), but it's no showstopper or even on any rung of the importance ladder.

Wait, wait: the bug isn't in the beautifier - it's in the rightclick menu of VFP's editor, which doesn't recognize an indented comment as comment. Now we CAN fix that, can't we? ;).