The Rails bundle uses ⌃p for its params snippet, which drives me insane... everywhere else ⌃p means "up one line". When I change it to a tab trigger (and type "para"), the change won't stick. If I move to another bundle item and back, the activation type is back to "Key Equivalent". If I change it to "Tab Trigger" again, "para" shows up, but again the change doesn't stay.
The only way I've found to work around this is remove the params snippet.
On Nov 8, 2006, at 1:58 PM, Grant Hollingworth wrote:
The Rails bundle uses ⌃p for its params snippet, which drives me insane... everywhere else ⌃p means "up one line". When I change it to a tab trigger (and type "para"), the change won't stick. If I move to another bundle item and back, the activation type is back to "Key Equivalent". If I change it to "Tab Trigger" again, "para" shows up, but again the change doesn't stay.
Setting a tab trigger as an activation does not remove the key equivalent activation. You can have a snippet/command be triggered both via a tab trigger AND via a key equivalent. To remove the key equivalent select that setting, and then click where the key equivalent is. You'll see a little x in the right corner. Click on it and it will remove the key equivalent.
Haris
* Charilaos Skiadas skiadas@hanover.edu [2006-11-08 12:52]:
Setting a tab trigger as an activation does not remove the key equivalent activation. You can have a snippet/command be triggered both via a tab trigger AND via a key equivalent. To remove the key equivalent select that setting, and then click where the key equivalent is. You'll see a little x in the right corner. Click on it and it will remove the key equivalent.
Thanks. Maybe that little x should always be visible. And since both activation types can be in use at once, maybe they should be visible at the same time.
On Nov 8, 2006, at 2:19 PM, Grant Hollingworth wrote:
Thanks. Maybe that little x should always be visible. And since both activation types can be in use at once, maybe they should be visible at the same time.
I don't think that's a bad idea. I use double triggers fairly often on commands that behave differently depending on whether a word is selected or not and it would be nice not to have to always check to see if one or the other is set.
Brett
-
Brett Terpstra -
Charilaos Skiadas -
Grant Hollingworth