Can’t wait to try the Vintage mode!
Dev Build 2096
Does the ignored_packages setting work on the fly? Is a restart necessary? What about packages that create locks on files inside the package dir?
It’s applied on the fly, yeah - internally, it works just as if the files were deleted. Plugins will be unloaded, but unless they clean up after themselves (via defining an unload_handler() function), then all their effects won’t be undone until the next restart.
I am loving this so much! – Would love to see 0 (zero -> go to beginning of line), :0 (beginning of document) (end of document)
[quote=“iamntz”]
Are you on Lion? If yes, this os has a… feature that prevent repeat keystrokes.[/quote]
I believe it only does this for characters that have common accents, such as e, a, or n.
Also, if this bugs the crap out of you like it did me: hints.macworld.com/article.php?s … 1122558299
I love the vi feature, I’ve only been using it for a few hours and its helped me in my workflow already. it greatly increases the possibilities for multiple select and macro creation (specifically the f for find since it works on every line of multi-select! before you just had End to line cursor up in different spots on each line…).
jps, I love the new vi mode, since I do switch between vim, sublime and VS in my day-to-day work
Innovations/features like this are my reason to buy/pay for Sublime.
It’s commonly used on the C++ side to display lists of things in the menus, for example:
class UrlListCommand(sublime_plugin.WindowCommand):
urls = ...]
def run(self, index):
if index < len(urls):
open_url(index)
def is_visible()
return index < len(urls)
def description(self, index):
if index < len(urls):
return "Open URL: " + urls[index]
You can then create menu items that call this command with various indices, as done for the open_recent_file command in the main menu.
Another otherwise undocumented feature is 2096 is the ability to bind to wildcard characters. If you setup a key binding to “”, then that’ll match any character, and forward the matched character onto the command via the “character” argument. For example:
{ "keys": "r", "<character>"], "command": "replace_character" }
This is used by Vintage to implement, ‘r’, ‘f’, ‘t’, etc.
If you specify an argument called “character” in the binding, then it’ll get overwritten by the actual typed character. Other arguments are unaffected.
Next build will be out today.
For some reason it seems like my User Key Bindings aren’t loading. If I remove the Default (OSX).sublime-keymap file from Packages/User, the console prints:
found 5 files for base name Default.sublime-keymap
If I put it back, it still prints the same thing. If I fill it with mal-formed JSON, it doesn’t give me an error message on save, even though the default Default (OSX).sublime-keymap will give me such an error.
Thougts?
Thanks!
Build 2097 is out now, addressing the issue where platform specific key bindings weren’t read from the user package.
Wow…i love this!!! You have to keep vintage part of sublime (you might want to make the cursor more visable in visual mode like screencast.com/t/j2Uk1Z5kDrO)
If I could figure out Build on save I would buy sublime today.
[quote=“iamntz”]
Are you on Lion? If yes, this os has a… feature that prevent repeat keystrokes.[/quote]
Thank you. This was indeed the issue. This new Lion function can fortunately be disabled using
defaults write -g ApplePressAndHoldEnabled -bool false
I like that / is mapped and opens the find menu, can we have : mapped to goto line number?
Many thanks
also f then a letter works great but it’s missing ; which is the next occurrence of the letter, if that could be added it would be great