[SVN] Bundle commit 591

[Jeroen van der Ham]

On 16-04-2005 17:42, Brad Miller wrote:
> Although iTerm is not a standard application, the run in iTerm is bound
> to the same key as Python so you get a choice of how you want to run
> your script. I'd prefer that we leave the keybinding there so I don't
> have to go through the automation and command menus to find this.
> 
> We have lots of commands that use 'non standard' applications and I
> don't think we would want to unbind the keys that refer to all of them
> would we?

I may have overshot this fix a bit, because I was pissed off at not being
able to find where the generic description "run in iTerm" came from and
"find "~/Library/Application Support/TextMate/Bundles"-name *iTerm*" did
not turn up anything.
(I also sent a bug report to Allan asking for an easier way to find out
where commands are coming from).

However, I feel that the difference with other "non standard"
applications is that iTerm is not something that goes along naturally
with Python development, while e.g. TeXniscope is something you can
expect a LaTeX writer to use.

And the argument that the user gets a choice when you have the duplicate
keybindings does not hold for me. I run python pretty frequently and I
just want to use one keybinding for it and not keybinding, select
something from menu.

And you don't have to go through the menus everytime to run it, you can
set the keybinding back yourself if you need it. Perhaps we have another
issue there, because default keybindings and user configured keybindings
are stored in the same place at the moment..

Jeroen.
-- 
            <http://www.je-ju.net/~jeroen/blog/>