Hello
TM is really on of the best text editors, however, there is two issues unresolved for (the) years (of SL) now.
Issue one is TextMate's spelling behaviour, i.e., the automatic detection of the language of a written paragraph, see here:
http://lists.macromates.com/textmate/2009-November/029964.html
TM does not detect the language I am typing in, perhaps because it uses a non-Apple document window. Anyway, always changing the system language to get correct spell check on the fly (as suggested in the thread) could hardly be a working solution. In addition, quite often I write source documents in various languages, e.g. English and German, and that makes a "one language per document" unusable.
There has also been an issue with an advanced print dialogue (but I cannot remember the posting). It is quite nice that TM adds headers and footers, however, TM does not print coloured syntax, and leaving a margin of about 1cm makes the printout unusable for punching and filing. In addition, 11pt Monaco is quite good on my screen but printing in that font size is rather a waste of space on the page. Of course, I know, that one may produce a html (nicely coloured, indeed), open that one in, say, Firefox, and print the html page.
Anyway, I was wondering if there is any progress on these two points, first, to get the apple multilingual spell check working, second, to provide TM with a print preference to set things like font, colours, and margins.
Any thoughts?
Regards *S*
Hi Sascha,
her is my workaround:
On 15 May 2011, at 11:53, Sascha Vieweg wrote:
TM does not detect the language I am typing in, perhaps because it uses a non-Apple document window. Anyway, always changing the system language to get correct spell check on the fly (as suggested in the thread) could hardly be a working solution. In addition, quite often I write source documents in various languages, e.g. English and German, and that makes a "one language per document" unusable.
I'm using the TMTOOLS plugin
site: http://www.eva.mpg.de/~bibiko/downloads/textmate/index.html (at the bottom)
Then I have two bundle commands:
name: Set spell checking language to German input: none output: none command: "$TMTOOLS" set spellCheckerLanguage '{to=de_DE;}' key equivalent: CTRL+3
and
name: Set spell checking language to English input: none output: none command: "$TMTOOLS" set spellCheckerLanguage '{to=en_GB;}' key equivalent: CTRL+4
One can also bind both commands to one key shortcut, and make usage of the TMTOOLS command "$TMTOOLS" get currentSpellCheckerLanguage to toggle the languages.
There has also been an issue with an advanced print dialogue (but I cannot remember the posting). It is quite nice that TM adds headers and footers, however, TM does not print coloured syntax, and leaving a margin of about 1cm makes the printout unusable for punching and filing. In addition, 11pt Monaco is quite good on my screen but printing in that font size is rather a waste of space on the page. Of course, I know, that one may produce a html (nicely coloured, indeed), open that one in, say, Firefox, and print the html page.
Here I'm using the TextMate bundle command "Create HTML from Document" to get an HTML document and write a tiny script for setting fonts, sizes etc.; then display it in the Web Preview and press ⌘P for printing.
Cheers, --Hans
On 15.05.11 13:51, Hans-Jörg Bibiko wrote:
Hi Sascha,
her is my workaround:
On 15 May 2011, at 11:53, Sascha Vieweg wrote:
TM does not detect the language I am typing in, perhaps because it
uses a non-Apple document window. Anyway, always changing the system language to get correct spell check on the fly (as suggested in the thread) could hardly be a working solution. In addition, quite often I write source documents in various languages, e.g. English and German, and that makes a "one language per document" unusable.
I'm using the TMTOOLS plugin
site: http://www.eva.mpg.de/~bibiko/downloads/textmate/index.html (at
the bottom)
Then I have two bundle commands:
name: Set spell checking language to German input: none output: none command: "$TMTOOLS" set spellCheckerLanguage '{to=de_DE;}' key equivalent: CTRL+3
and
name: Set spell checking language to English input: none output: none command: "$TMTOOLS" set spellCheckerLanguage '{to=en_GB;}' key equivalent: CTRL+4
One can also bind both commands to one key shortcut, and make usage
of the TMTOOLS command
"$TMTOOLS" get currentSpellCheckerLanguage to toggle the languages.
There has also been an issue with an advanced print dialogue (but I
cannot remember the posting). It is quite nice that TM adds headers and footers, however, TM does not print coloured syntax, and leaving a margin of about 1cm makes the printout unusable for punching and filing. In addition, 11pt Monaco is quite good on my screen but printing in that font size is rather a waste of space on the page. Of course, I know, that one may produce a html (nicely coloured, indeed), open that one in, say, Firefox, and print the html page.
Here I'm using the TextMate bundle command "Create HTML from
Document" to get an HTML document and write a tiny script for setting fonts, sizes etc.; then display it in the Web Preview and press ?P for printing.
Thanks for the help and the hints concerning TMTOOLS. For some months I have been using these workarounds. Yet, I still find it cumbersome and ineffective to set up specific scripts for these two basic things, spelling and printing. I was wondering whether there is current work in progress on the incorporation of Apple's native spelling mechanisms and a better printing layout/setup? As far as I understood, this question translates into 'Is there work in progress to use OS-Xs native text window (such as the one found in TextEdit.app) in a future version of TM?' Thanks for your hints and advices.
Bests *S*
On 14 Nov 2011, at 14:17, saschaview@gmail.com wrote:
[…] I was wondering whether there is current work in progress on the incorporation of Apple's native spelling mechanisms and a better printing layout/setup?
There is not, the public alpha will infact bring us back to the 1.0 days with no printing at all (other than via the HTML output).
When I will get around to improving this, time will tell.
As for spelling, it already uses Apple’s API for spelling, why this gives a worse experience than Apple’s own NSTextView-based applications is something I need to look into, but again, time will tell when I get around to it.
On Nov 15, 2011, at 3:08 AM, Allan Odgaard wrote:
On 14 Nov 2011, at 14:17, saschaview@gmail.com wrote:
[…] I was wondering whether there is current work in progress on the incorporation of Apple's native spelling mechanisms and a better printing layout/setup?
There is not, the public alpha will infact bring us back to the 1.0 days with no printing at all (other than via the HTML output).
Good. Printing is dead last on the list of things I want from TextMate. Or any other program. Jerry
When I will get around to improving this, time will tell.
As for spelling, it already uses Apple’s API for spelling, why this gives a worse experience than Apple’s own NSTextView-based applications is something I need to look into, but again, time will tell when I get around to it.
On Nov 15, 2011, at 6:47 PM, Jerry wrote:
Good. Printing is dead last on the list of things I want from TextMate. Or any other program.
Ha ha! I know. Printing? In 2011?
On 15.11.11 11:08, Allan Odgaard wrote:
On 14 Nov 2011, at 14:17, saschaview@gmail.com wrote:
[…] I was wondering whether there is current work in progress on the incorporation of Apple's native spelling mechanisms and a better printing layout/setup?
There is not, the public alpha will infact bring us back to the 1.0 days with no printing at all (other than via the HTML output).
When I will get around to improving this, time will tell.
As for spelling, it already uses Apple’s API for spelling, why this gives a worse experience than Apple’s own NSTextView-based applications is something I need to look into, but again, time will tell when I get around to it.
Dear Allan
I do not want to be impatient. However, 3.5 months later still no fix for correct Apple spell checking mechanisms in TM. Since I use TM daily for writing LaTeX documents in both, English and German, multi-lingual spell checking is essential for me to render TM useful. With all respect to your work on TM, may I request a more urgent inspection and fix of the still-not-working spell checking facilities in TM?
Thank you!
Best regards *S*
I do not want to be impatient. However, 3.5 months later still no fix for correct Apple spell checking mechanisms in TM. Since I use TM daily for writing LaTeX documents in both, English and German, multi-lingual spell checking is essential for me to render TM useful. With all respect to your work on TM, may I request a more urgent inspection and fix of the still-not-working spell checking facilities in TM?
Well, I could say the same towards Apple. They had broken the multi-language spelling check in Leopard, then fixed it in Snow Leopard (1.5 year after I had submitted them bug reports), just to break it again in Lion. The automatic spelling does not work at all in Lion, changing spelling language to specific language has no effect on the text that is already there in Cocoa NSTextView, the underlined errors remain, even the words are perfectly fine for the selected language.
So I wouldn't blame Allan for that but rather Apple for this bogus implementation. Seems like guys at Cupertino were so sure about quality so skipped QA testing :( AFAIK TM1 spelling was working fine, because it was not based on Cocoa views, but it was somehow done on lower level.
Cheers,
On 02.03.12 12:04, Adam Strzelecki wrote:
I do not want to be impatient. However, 3.5 months later still no fix for correct Apple spell checking mechanisms in TM. Since I use TM daily for writing LaTeX documents in both, English and German, multi-lingual spell checking is essential for me to render TM useful. With all respect to your work on TM, may I request a more urgent inspection and fix of the still-not-working spell checking facilities in TM?
Well, I could say the same towards Apple. They had broken the multi-language spelling check in Leopard, then fixed it in Snow Leopard (1.5 year after I had submitted them bug reports), just to break it again in Lion. The automatic spelling does not work at all in Lion, changing spelling language to specific language has no effect on the text that is already there in Cocoa NSTextView, the underlined errors remain, even the words are perfectly fine for the selected language.
So I wouldn't blame Allan for that but rather Apple for this bogus implementation. Seems like guys at Cupertino were so sure about quality so skipped QA testing :( AFAIK TM1 spelling was working fine, because it was not based on Cocoa views, but it was somehow done on lower level.
Cheers,
Thanks, Adam
To make it clear: My intention was not to "blame" something on somebody, rather it was a more strongly formulated wish ;-)
I see, Lion would downgrade everything again (heaven help if Mountain Lion will "fix" things again). May give cocoAspell another trial.
Bests, *S*
To make it clear: My intention was not to "blame" something on somebody, rather it was a more strongly formulated wish ;-) I see, Lion would downgrade everything again (heaven help if Mountain Lion will "fix" things again). May give cocoAspell another trial.
Since I was recently writing some Markdown and docu using TM2, I had decided to bump this thread. I blamed Apple for their bogus implementation of built-in spell checking, I still do. However somehow I find TM1 with that borked built-in spell checker pretty well, thile TM2 not so well.
Currently TM2 misbehaves (comparing to TM1): (1) document is not spell checked once loaded or when spell checking is being enabled (existing errors aren't marked) (2) spell checking isn't invalidated and restarted when changing the language (errors from previous language stay marked)
However spell checking when typing working fine. Only problem that errors that are already in the file will be never highligted whatever I do.
So, is polishing the spell check of TM2 in plans?
Cheers,
Since I was recently writing some Markdown and docu using TM2, I had decided to bump this thread. I blamed Apple for their bogus implementation of built-in spell checking, I still do. However somehow I find TM1 with that borked built-in spell checker pretty well, thile TM2 not so well.
Currently TM2 misbehaves (comparing to TM1): (1) document is not spell checked once loaded or when spell checking is being enabled (existing errors aren't marked)
I have spellChecking = 1 in my .tm_properties file, and this works very well for LaTeX projects. In particular, it shows errors that are already there when I load files, and highlights any new errors that I type.
Using the spelling settings in the menus doesn't seem to work very well though - and this is probably one of those "we recommend you put settings in .tm_properties files for the moment, as some things don't stick if you use the menus".
If you need to use different languages for different directories, there is a spellingLanguage setting too (language codes are here: http://pastie.textmate.org/private/xmwqhbzi8o9hdbhgcplw)
David.
I have spellChecking = 1 in my .tm_properties file, and this works very well for LaTeX projects. In particular, it shows errors that are already there when I load files, and highlights any new errors that I type.
Indeed. But I was enabling spell checking via menu, and there was no effect on already loaded document.
However following your suggestions, when spell checking was already enabled in tm_properties, the errors were marked correctly upon load.
Using the spelling settings in the menus doesn't seem to work very well though - and this is probably one of those "we recommend you put settings in .tm_properties files for the moment, as some things don't stick if you use the menus".
Hmmm... it seems that I would need to fiddle with tm_properties then, as changing the language when TM is running is broken. At least when I have several files in multiple languages.
Cheers,
Hmmm... it seems that I would need to fiddle with tm_properties then, as changing the language when TM is running is broken. At least when I have several files in multiple languages.
If you're writing in a markup language with a commenting environment, you might be able to add to the grammar (creating scopes for different languages) and then set the languages for those scopes in the tm_properties file.
-
Adam Strzelecki -
Allan Odgaard -
David Howden -
Hans-Jörg Bibiko -
Jerry -
Rob McBroom -
Sascha Vieweg -
saschaview＠gmail.com