Sorry if this is a well-known issue, but I couldn't find anything about it...
For some reason, completions no longer seem to work in my installation of TextMate. Whether I press the escape button *or* select Completion > Next Completion (or Previous Completion) from the menu, all I gett is the system bell/beep.
Does anyone have any ideas about what could have caused this (have I pressed some Forbidden Keyboard Combo™?) or, perhaps, how I could go about figuring it out (or, preferably, even fixing it)?
I think maybe I'm onto the culprit here... I just played around, and happened to type "a" and it completed to "afternoon" (but nothing else). "b" won't complete to anything; "c" completes (only) to "continuous"; "d" to "day", "dusk" and "dawn"; "e" to "evening"; "f", "g" and "h" to nothing; "i" to "intercut"; "j", "k" to nothing; "l" to "later". Already I'm having a strong suspicion -- but "m" really nailed it: It completes to "magic hour", "morning" and "moments later". 10 points for guessing which bundles I just installed... ;-)
So -- I'm guessing that the "time auto-complete" feature of the Screenwriting bundle has somehow replaced my ordinary completion (as I get the exact same behavior when using option-escape, which is the actual keyboard shortcut for that).
I'm guessing that this is a bug in the Screenwriting bundle (or, perhaps, somewhere else) ... Should I simply uninstall the bundle? Would that even help? Where would the completion function have been (erroneously) overridden (i.e., where can I change it back)?
On Apr 5, 2007, at 0:31, Magnus Lie Hetland wrote:
I'm guessing that this is a bug in the Screenwriting bundle (or, perhaps, somewhere else) ... Should I simply uninstall the bundle? Would that even help? Where would the completion function have been (erroneously) overridden (i.e., where can I change it back)?
Sorry for the rubber-ducking here ... but simply unchecking the Screenwriting bundle in the filter list took care of the problem (i.e., the Screenwriting bundle is hogging the normal completion in the name of the time completion function, even when not in Screenwriting mode).
On Apr 4, 2007, at 6:34 PM, Magnus Lie Hetland wrote:
On Apr 5, 2007, at 0:31, Magnus Lie Hetland wrote:
I'm guessing that this is a bug in the Screenwriting bundle (or, perhaps, somewhere else) ... Should I simply uninstall the bundle? Would that even help? Where would the completion function have been (erroneously) overridden (i.e., where can I change it back)?
Sorry for the rubber-ducking here ... but simply unchecking the Screenwriting bundle in the filter list took care of the problem (i.e., the Screenwriting bundle is hogging the normal completion in the name of the time completion function, even when not in Screenwriting mode).
Ah yes, this is very bad. Oliver, please make sure all your commands include text.screenplay in their scope selector, for instance the scope selector for character auto-complete should probably be "text.screenplay character eol". In particular, the Time of Day completions preference item should have a scope selector of "text.screenplay" at least. Items with no scope selector are in effect anywhere, unless a more specific command takes over the key combo. They are not restricted to languages of the bundle they are in. So your scope selectors need to be as specific as possible.
-- Magnus Lie Hetland http://hetland.org
Haris Skiadas Department of Mathematics and Computer Science Hanover College
Oh, that is bad isn't it. It's not ignorance, just forgetfulness. I'll be more careful next time.
An update has been published at http://ollieman.net/screenbundle
--oliver
On 4/4/07, Charilaos Skiadas skiadas@hanover.edu wrote:
Ah yes, this is very bad. Oliver, please make sure all your commands include text.screenplay in their scope selector, for instance the scope selector for character auto-complete should probably be "text.screenplay character eol". In particular, the Time of Day completions preference item should have a scope selector of "text.screenplay" at least. Items with no scope selector are in effect anywhere, unless a more specific command takes over the key combo. They are not restricted to languages of the bundle they are in. So your scope selectors need to be as specific as possible.
On Apr 4, 2007, at 9:55 PM, Oliver Taylor wrote:
Oh, that is bad isn't it. It's not ignorance, just forgetfulness. I'll be more careful next time.
It's very easy to forget, thanks for the quick fix. I wonder, perhaps it would be nice if there is some indication somehow in the UI for items that don't have a scope selector set. I guess there are some items that are not supposed to have scope selectors, so the indication shouldn't be too obtrusive, but it's all too easy to forget to set it otherwise. Probably not a big deal anyway.
I wonder, if it's perhaps time for the screenwriting bundle to be added to the repository, if Oliver agrees of course.
Haris Skiadas Department of Mathematics and Computer Science Hanover College
An update has been published at http://ollieman.net/screenbundle
--oliver
On 4/4/07, Charilaos Skiadas skiadas@hanover.edu wrote:
Ah yes, this is very bad. Oliver, please make sure all your commands include text.screenplay in their scope selector, for instance the scope selector for character auto-complete should probably be "text.screenplay character eol". In particular, the Time of Day completions preference item should have a scope selector of "text.screenplay" at least. Items with no scope selector are in effect anywhere, unless a more specific command takes over the key combo. They are not restricted to languages of the bundle they are in. So your scope selectors need to be as specific as possible.
On Apr 4, 2007, at 9:35 PM, Charilaos Skiadas wrote:
I wonder, perhaps it would be nice if there is some indication somehow in the UI for items that don't have a scope selector set.
My scope validator in the Support directory could easily be modified to report global scope warnings. We could have it cross-check against a known OK-to-be-global list. The hard part would be getting developers to actually run the script...
James Edward Gray II
On 5. Apr 2007, at 05:36, James Edward Gray II wrote:
On Apr 4, 2007, at 9:35 PM, Charilaos Skiadas wrote:
I wonder, perhaps it would be nice if there is some indication somehow in the UI for items that don't have a scope selector set.
My scope validator in the Support directory could easily be modified to report global scope warnings.
That’d be great -- I started something like that in validate_bundle.rb, but I never finished it ;)
We could have it cross-check against a known OK-to-be-global list. The hard part would be getting developers to actually run the script...
I’ve been wanting to run validate_bundle.rb as a svn post-commit hook! :)
On Apr 5, 2007, at 12:08 AM, Allan Odgaard wrote:
On 5. Apr 2007, at 05:36, James Edward Gray II wrote:
On Apr 4, 2007, at 9:35 PM, Charilaos Skiadas wrote:
I wonder, perhaps it would be nice if there is some indication somehow in the UI for items that don't have a scope selector set.
My scope validator in the Support directory could easily be modified to report global scope warnings.
That’d be great -- I started something like that in validate_bundle.rb, but I never finished it ;)
The change has been made. You can now use Support/bin/ validate_bundle.rb to hunt for globally scoped automations and preferences.
James Edward Gray II
Yeah, but that would require learning to use Subversion and all your dev procedures, which I've been too lazy to do. Are there any good introductions?
On 4/4/07, Charilaos Skiadas skiadas@hanover.edu wrote:
I wonder, if it's perhaps time for the screenwriting bundle to be added to the repository, if Oliver agrees of course.
Oliver Taylor wrote:
On 4/4/07, Charilaos Skiadas wrote:
I wonder, if it's perhaps time for the screenwriting bundle to be added to the repository, if Oliver agrees of course.
Yeah, but that would require learning to use Subversion and all your dev procedures, which I've been too lazy to do. Are there any good introductions?
It's pretty easy, but one of us could commit it for you if you want.
-Jacob