hnrch wrote:Thanks a lot Jon! buffer selector is fixed, but select_lines command not working on Ubuntu yet.
oats wrote:one thing that would help me be more productive using it is the middle button select.
jps wrote:The middle mouse button is already spoken for under X windows, which is why I'm no longer using it for column select.
noonat wrote:Clicking on a file in the project section of the sidebar opens it, but doesn't actually add it to a group. The file is not closeable (you have to switch to another file).
noonat wrote:Some bugs in build 20101210:
- Sublime crashes then continues to crash indefinitely, until I delete Session.sublime_session. I tried to diff and track down what's causing it, but couldn't. All the crashes seem to be one of the following four stack traces, though:
sublimator wrote:Look at the new API, it seems commands are referencing 'self.view' which implies having a command instance per view.
- Code: Select all
cmds = 
for class_ in text_command_classes:
def __init__(self, view):
self.view = view
Can you give us some info on the life cycle of commands in X? I'm interested to know the reasoning behind this change. Does each view get every command primed for it at 'some point'?
jps wrote:That's a feature, not a bug. It allows you to browse files in a project without cluttering your list of open files. To add the file to the list of open files, either double click instead of single click, or start editing.
jsp wrote:If it happens again, ... would you be up for emailing the .sublime-session file to me?
jps wrote:Yep, there's one instance of the command per-view. They get created for a particular view the first time any command is run on that view. The reasoning is simply because that's how things work within the C++ UI toolkit (aka 'hydra'), so it makes things a little simpler this way. I think that if you do need to write a stateful command (to be avoided where possible, so that the command works properly with macros), life is a bit simpler this way, compared to having only global state available.
oats wrote:Oh no! I've become addicted to using the middle button... any chance you could support an option to map the middle button to shift-click for those not using Xwin?
gpfsmurf wrote:Makes sense, but what if a particular command needs to maintain a single state for a file or a whole window, what would be the best way to achieve this?