ok, I just don't get it: *sometimes* when pressing the ctrl-shift-a key I get the neato little popup with all the svn-related commands (which is what I want) and *sometimes* I get the status popup (which is usually *not* what I want).
I just can't seem to figure out the system behind it - or more importantly how to make it *always* present the popup.
any ideas?
best regards,
tom -- Tom Lazar http://tomster.org
On Apr 28, 2005, at 3:06, Tom Lazar wrote:
ok, I just don't get it: *sometimes* when pressing the ctrl-shift-a key I get the neato little popup with all the svn-related commands (which is what I want) and *sometimes* I get the status popup (which is usually *not* what I want).
What's the status popup?
With my setup the only thing on ctrl-shift-A is the sub-version stuff [1].
However, currently the text view must have focus for commands to work. So if e.g. you give focus to the project drawer, the commands won't work.
Another thing could be that the status popup you speak of is a command with a scope, hence would be used each time you're in a document where the scope matches.
[1] If you're using zsh, you can get a dump of all A-key bindings using: cd <bundle-directory> for file in *.tmbundle/*/*.plist; do printf "%s " $file; pl <$file|grep keyE; done|grep -i 'a"'
I think what he means is that instead of the svn commands menu, you get the result of the svn status command back (which is the first one in that list). I too have experienced those things, but I wrote it off as trying to do it too fast and accidently pushing the spacebar or something, but there might be more behind it then..
Jeroen.
On Apr 28, 2005, at 9:20, Jeroen van der Ham wrote:
I think what he means is that instead of the svn commands menu, you get the result of the svn status command back (which is the first one in that list). I too have experienced those things, but I wrote it off as trying to do it too fast and accidently pushing the spacebar or something, but there might be more behind it then..
Ah, okay -- that's then the problem about not having focus on the text view.
Basically the active text view overloads key event handling and is responsible for showing the menu when there are several items with the same key equivalent. If there is no active text view, it falls back to the default behavior (which is limited to only having one item per key binding, as can be seen in the menu).
I have now improved this for (upcoming) beta 8, so as long as the project window is key, it will show the proper menu.
On Apr 28, 2005, at 9:54 AM, Allan Odgaard wrote:
Ah, okay -- that's then the problem about not having focus on the text view.
hm, I should have elaborated more. it's precisely the fact that in *some* cases it would *not* bring up the command-popup but the output of the status-command *eventhough I made sure I in fact have the focus on the text view* (by clicking onto it prior to issueing the command)
and of course, at the moment i can't reproduce it anymore ;-) murphy's law, i guess...
next time it comes up i'll conduct a more thorough investigation and report back,
tom
-- Tom Lazar, http://tomster.org
-
Allan Odgaard -
Jeroen van der Ham -
Tom Lazar