Hi all,
I have the key F12 bound to the action "showGuessPanel:" in Cocoa, which is then re-implemented by TextMate. However, the correction list is always empty in TextMate when it is full of best guesses in Cocoa apps.
Test case: - set up a Cocoa keybinding in ~/Library/KeyBindings/ DefaultKeyBinding.dict (F12 is unicode UF70F) to "showGuessPanel:" - restart TextMate - open a new plain text document (with online spell checking enabled) - type "apparentley " (including the end space to indicate end of word) - press F12 (or the keybinding you previously bound)
The guess list is empty, whereas if you do this in a Cocoa app such as TextEdit, the spelling pane would contain the ranked best guesses for the correct spelling of the word.
I would actually be happier if there was an action that inserted the "best guess" without requiring feedback, but I'm not aware if such an action exists. Is there perhaps a way to macro this within TextMate?
On 11 Jan 2007, at 11:49, Sam Halliday wrote:
Test case:
huh? This randomly started working for me... but I found another problem with it. Do as before, get the correction and click "Replace". Instead of replacing the word, it *inserts* the corrected word, so you end up with both copies. There is something strange going on and it's probably best I bind this key to nothing when in TextMate.
If anyone has any ideas on binding a key to replacing a word with the best guess spelling, then please let me know about it. (and not using the shell spell checkers as they are not linked in with the system dictionary).
Maybe option + F2 is what you're looking for. It selects the current word and allows you to replace it with the correctly spelled word. dirk
On 11-jan-2007, at 13:05, Sam Halliday wrote:
huh? This randomly started working for me... but I found another problem with it. Do as before, get the correction and click "Replace". Instead of replacing the word, it *inserts* the corrected word, so you end up with both copies. There is something strange going on and it's probably best I bind this key to nothing when in TextMate.
If anyone has any ideas on binding a key to replacing a word with the best guess spelling, then please let me know about it. (and not using the shell spell checkers as they are not linked in with the system dictionary).
-- Sam
Hi,
On 11 Jan 2007, at 12:30, Dirk van Oosterbosch, IR labs wrote:
Maybe option + F2 is what you're looking for.
Option-F2 just makes a "not found" noise when I use it.
Incidentally, I found out that TextMate has "showGuessPanel:" bound to "command and :" so you can use that instead of my keybinding when trying the test cases... it still seemingly randomly works or doesn't! Is it working for other people? Please try a few times.
- restart TextMate - open new text file - type "apparentley " - press command-: - the list is sometimes there, sometimes blank
is anyone else observing this?
-- Sam
On 11. Jan 2007, at 13:39, Sam Halliday wrote:
On 11 Jan 2007, at 12:30, Dirk van Oosterbosch, IR labs wrote:
Maybe option + F2 is what you're looking for.
Option-F2 just makes a "not found" noise when I use it.
A not found noise? It should open the context menu which is also available by control-clicking or right-clicking the word.
If you are on a laptop, you may need to use fn-option-F2.
Incidentally, I found out that TextMate has "showGuessPanel:" bound to "command and :"
This key binding should be pretty standard.
so you can use that instead of my keybinding when trying the test cases... it still seemingly randomly works or doesn't! Is it working for other people? Please try a few times.
I have it just open the panel. I just tested a Cocoa field, and it seems that it both opens the panel, and jumps to the first (or next) misspelled word (what is also normally achieved using ⌘;)
If you open the panel after having used ⌘; it will be pre-populated with suggestions for the misspelled word -- that might be what makes you view it as random.
It might be good to make it consistent with cocoa fields, though IMO ⌥F2 is an easier alternative -- having a key to replace with best guess, without bringing up any UI, is planned.