Arthur Chiu

Yeah there does need to be some additional work to fix issues like these. I've been meaning to do a rewrite of terminitor and break out some of the core...

The consular script are just ruby scripts with the consular DSL available to them. A simple example: ``` ruby class Foo def self.ips %w{foo bar fizz buzz} end end Foo.ips.each...

I'd suggest taking a look at the other [consular cores](https://github.com/achiu/consular-iterm/blob/master/lib/consular/iterm.rb) source. The cores are the main entry point into the execution of the commands and takes a hash that's being...

Currently consular(consular-iterm) doesn't have this ability. (In fact I didn't even know you could name your panes.) I'd be open to a pull request(on consular-iterm) with this feature or I...

@miros thanks for the catch. I think there might be a few additional places where this breaks 1.8.7 compat that I'll need to address.

one way to avoid having that extra tab is to use the `run` command instead: ``` ruby run 'irb' # current(first) tab tab 'ruby -v' # second tab tab 'whatever'...

thanks for the tip/workaround. this is probably due to the fact that terminitor is actually sending keystrokes for some of the window/tab generation behavior. Ideally, i'd like to move away...

the bounds/settings functionality isn't available with the iTerm core yet, though any patches and contributions are more than welcomed =)

yeah agreed, wish i thought of this earlier =/

If anyone is willing to submit a working pull request for version 3 support of Iterm, we'll gladly accept it. We can also lock iTerm v2 support to the current...