Comments disappear from script

[Jim Ault]

One step that might shed some light.
Open the stack.rev in a word processor, like BBEdit on Mac, and you should
be able to read all your scripting.  If the script editor window is not
writing some lines to the interface, then this could be a bug, or some sort
of corruption that occludes the comments.

Another thought is that the comments may only be the apparent change.  Some
code might not be showing either.  If you have backup versions, try using
the word processor that can compare differences in the stacks/files.  This
might show invisible chars as well as visible script changes.

Caution: when editing and saving scripts while using multiple stacks open,
saves may not work well if handlers have not fully aborted.  A few months
ago, one of the members of the list was using a technique that kept many,
many script containers open and this created a very messy situation.  He
also experienced odd behavior, crashes, and loss of code.

Hope this helps.
Jim Ault
Las Vegas

> On 12/21/05 5:59 AM, "Jerry Muelver" <jerry at hytext.com> wrote:
> 
>> I had a bunch of helpful, instructional comments at the top of  my stack
>> script. After an hour or so of coding and saving reloading, I went back to
>> review the comments, and they were gone. Is there some code-cleaning option
>> that I triggered that would strip comments out? Rev 2.6.1 on Linux (Ubuntu
>> Gnome).
> 
> Sorry, Jerry - I've never seen Rev do this before, but then again I spend
> 99.5% of my time in non-Linux environments. So if this *is* a bug, it would
> seem to be only on Linux.
> 
> One question - are you colorizing your scripts, or did you turn on
> colorization recently? The reason I ask is that Rev keeps a formatted copy
> of your scripts handy so it can show you the colorized version when you want
> to see it. So there might have been some kind of disconnect between the
> plain text version of the script (with comments) and the formatted one (no
> comments). I haven't seen this before, but it's the only thing I could think
> of...
> 
> Ken Ray