For some reason textmate likes to beep at me when Im editing some files. Not just once or twice, but every keypress. It beeps a whole lot when I open that particular file as well. I cant work out why, the file isnt read only, and it wasnt beeping so much yesterday.
At any rate, is there some way I cant turn the beep off? If there is some kind of error then textmate should provide better feedback than a beep. There is nothing in the help file when I search for 'beep' or 'audio'.
At any rate, is there some way I cant turn the beep off? If there is some kind of error then textmate should provide better feedback than a beep. There is nothing in the help file when I search for 'beep' or 'audio'.
I changed to another tab, and there was a whole lot of beeping for a moment. Editing in the other tab worked fine, and when I returned to the 'noisey' tab it was silent - bliss.
A few minutes later the beeping returned, and changing tabs didnt help this time.
On 17/08/2005, at 22.00, Jon Hart wrote:
For some reason textmate likes to beep at me when Im editing some files. Not just once or twice, but every keypress.
Open Console.app -- the beep (almost) always means that TM wrote an error message there.
It beeps a whole lot when I open that particular file as well.
I'm 99% sure that something is wrong with the language grammar you use. Most likely that it can't find an included grammar.
What language is this? Which version of TextMate? Are you using bundles from the svn repository?
I'm 99% sure that something is wrong with the language grammar you use. Most likely that it can't find an included grammar.
What language is this? Which version of TextMate? Are you using bundles from the svn repository?
Ive got a simple coldfusion syntax setup, and in v15 I had attempted to do nested comments with a self including pattern. It didnt beep before, so I guess that the upgrade to v16 made that an error. I removed the self reference and now it works.
It was strange that it was only happening in one specific file, but the 'test' button in the language editor pushed a whole lot of errors into the console.
Still dont like all the beeping :)
On 17/08/2005, at 22.52, Jon Hart wrote:
[...] so I guess that the upgrade to v16 made that an error [...]
It was strange that it was only happening in one specific file [...]
Generally bad things in the grammars are reported when they are seen, i.e. during parsing. So whether or not your grammar change caused a problem (and lead to a beep) would rely on the file content.
-
Allan Odgaard -
Jon Hart