Bugzilla Bug 105

This morning I recieved an email, in japanese from my gmail account. It
recieved
OK, but when I clicked on it, scribe froze completely. CPU usage goes to 100%
and InScribe is unresponsive. I forwarded the mail again from gmail's web
interface and the second time I could recieve it no problem. I made a backup of
the scribe log file and re-opened scribe. This is what the scribe.txt file
reported during the new session:

C:\Code\Scribe\Code\ScribeApp.cpp:7936 - No option 'Folder-7'
C:\Code\Scribe\Code\ScribeApp.cpp:7936 - No option 'Folder-7'

At the moment this is completely repeatable. If I can manage to export and
clear
all of the other emails out I can send you the mail2 file. 

System is an Inspiron 6000 notebook 512mb RAM running XP MCE SP2. Running
scribe
1.89T4.

Well somehow while I was trying to export out my folders scribe deleted my
gmail
folder. I went Ctrl-A to select emails in my gmail folder and it disappeared.
My
friendly HEX editor says that my gmail folder is still alive in well in my
Mail2
file. I can copy out the portion of the mail2 file related to this bug or if
you
know how I can manually undelete a folder I can do that. I'm not heartbroken
losing this folder, gmail still has a copy of everything and most of it is
unimportant stuff. 

I have a message that does the same thing in my install. I think it's the HTML
control getting stuck while parsing CSS selectors. I changed that recently and I
may have even fixed it. I do remember tweaking it recently, although that may
have caused the issue instead of fixing it.

In any case it'd be good to get a copy of the message attached to this bug
report. If you could switch off the mail preview (Tools -> Layout -> Just
Folders and List) and then drag the offending mail to the desktop and attach it
to this bug report I can verify the problem and any fix I make.

As for the folder disappearing I'm not sure I follow what happened. You pressed
Ctrl-A with the folder selected and it was deleted just like that? No
confirmation or anything?

I've rewritten the CSS selector parser so it doesn't hang.