Hi,
I've been experiencing this for quite a while now but until now had no time to dig into the matter: With "Check Spelling as You Type" I'm experiencing abysmal typing speed problems when working on LaTeX documents. It only happens when I'm working some in already existing paragraphs, *not* when typing at the end of the document. I can actually see single letters appearing one after another in slow- motion. Very annoying! Once I turn off "Check Spelling as You Type" everything's back to normal, but it lacks a lot of convenience ... It this a known problem? Does anybody else experience these problems, too?
(I'm working on a 12" PB (1st gen., 867 mhz) maxed out with 1.12 GB RAM. It's plain text with a bit of markup so the machine *should* be up to it ...!)
Christian
Am 11.09.2006 um 15:30 schrieb Allan Odgaard:
[...] It this a known problem? Does anybody else experience these problems, too?
With one third party spell checker, yes.
Try switch to one of the spell checkers provided by the OS and see if that helps.
I forgot to mention that: It is the OS X spell checker, I'm afraid! (I've got not third party spell checker installed and never had.)
I already tried switching from ›Multilingual‹ to a single language (German in this case), but that made no difference either.
Also the size of the document doesn't seem to make a difference. I'm experiencing this with fairly short files als well as longer ones.
Christian
On 11/9/2006, at 15:41, Christian Bogen wrote:
[...] Also the size of the document doesn't seem to make a difference. I'm experiencing this with fairly short files als well as longer ones.
When you edit a line, TextMate runs the entire line through the spell checker. So the only thing which should affect the speed is the length of the current line, not the document.
Does a line with just a few word also see the problem?
Am 11.09.2006 um 15:53 schrieb Allan Odgaard:
When you edit a line, TextMate runs the entire line through the spell checker. So the only thing which should affect the speed is the length of the current line, not the document.
Does a line with just a few word also see the problem?
Indeed, it clearly seems to be a line length problem. Is there anything that can be done about that? (Apart from working without "live" spell checking ...? :)
Seems to be a TM problem, and it also happens without any syntax highlighting (ie. manually switched to "Plain Text"). If I post the same text in WriteRoom (for example) I can edit even the longest paragraphs without any noticeable delay (with spell checking).
Christian
On 11/9/2006, at 16:28, Christian Bogen wrote:
Does a line with just a few word also see the problem?
Indeed, it clearly seems to be a line length problem. Is there anything that can be done about that? (Apart from working without "live" spell checking ...? :)
Only the obvious things like hard wrapping lines to keep down the length etc.
[...] If I post the same text in WriteRoom (for example) I can edit even the longest paragraphs without any noticeable delay (with spell checking).
Basically all other text editing applications use NSTextView, which doesn’t run the text through the spell checker as often as TextMate, likely because they knew the performance of said checker couldn’t handle that on older hardware ;)
I haven’t decided yet if I want to address this issue, as it shouldn’t be a problem on current hardware, and being lazy about when to spell check what is a lot of messy code, and on that note, NSTextView didn’t get it right (last I checked), i.e. it can occasionally end with a word shown as misspelled or spelled correctly, even though it is the opposite.
Am 11.09.2006 um 16:37 schrieb Allan Odgaard:
Only the obvious things like hard wrapping lines to keep down the length etc.
... which isn't "very convenient" to say the least, especially since TM doesn't seem to have a build-in hard wrap option (unless I'm missing something). Also I find hard wrapping generally uncomfortable and undesirable for texts which are (re)edited many times.
Basically all other text editing applications use NSTextView, which doesn’t run the text through the spell checker as often as TextMate, likely because they knew the performance of said checker couldn’t handle that on older hardware ;)
Sadly right now it looks like I won't be able afford a new Mac for at least another year or so ... :(
I haven’t decided yet if I want to address this issue, as it shouldn’t be a problem on current hardware, and being lazy about when to spell check what is a lot of messy code, and on that note, NSTextView didn’t get it right (last I checked), i.e. it can occasionally end with a word shown as misspelled or spelled correctly, even though it is the opposite.
Well, if you could make this an item on your agenda, I'd be very thankful for sure.
I'd rather take the "normal" miss-checks the standard NSTextView sometimes produces than the severe speed problem I'm experiencing right now! (And, believe me, severe basically means unusable with spell checking ...)
Thanks in advance!
Christian
-
Allan Odgaard -
Christian Bogen