jps wrote:The behavior when opening files from the command line has changed a little when used in conjunction with virtual desktops (Linux) or Spaces (OS X). Previously, if a window wasn't open on the current desktop, one would be created. Now, files passed on the command line will be opened in the last used window irrespective of the desktop it's on - this is especially important on Lion, where full screen applications get allocated a Space of their own. You can force a new window to be created on the current desktop via the '-n' parameter.
iamntz wrote:Watch what's happening when i hit up/down arrow http://screencast.com/t/bn935nYXg
iamntz wrote:Basically the texts scroll up when i press up/down arrows, even if there is not enough text to scroll. Make sense?
sublimator wrote:There's seems to be issues with the add_on_change settings callback. If you call again with the same key it just appends the callback.
jbrooksuk wrote:Also, I've been experiencing a lot of slow downs while only editing files, no plugins are being accessed during this time.
as long as there are no issues calling clear() extra times, we could get in the habit of clearing before adding during dev...jps wrote:it's not ideal wrt module reloading.
I'd think you would just add all callbacks under a key for your plugin. I can't think of a huge use case where you'd be clearing/adding multiple different callbacks in the middle of your plugin. even so, you could just prefix with plugin and clear a list on reloadsublimator wrote:If you use more than one callback you'd use a different key wouldn't you?
jps wrote:There are a pair of new API functions on the Settings object, add_on_change(key, callback) and clear_on_change(key). on_change callbacks are run when any of the settings has changed, either due to the underlying file being reloaded, or set() has been called.