Skip to content
This repository has been archived by the owner on Dec 22, 2023. It is now read-only.

Consular does not cd to directory #99

Open
allesklar opened this issue Jul 3, 2013 · 2 comments
Open

Consular does not cd to directory #99

allesklar opened this issue Jul 3, 2013 · 2 comments

Comments

@allesklar
Copy link

I think this is an odd bug. My laptop might be too fast. I have been very happy with the consular gem until now and it all works fine. For each project I usually have it open 5 tabs for server, guard, console, db, and other tasks.

I just purchased the MBP 15" with 500GB SSD drive and 16GB of Ram. Now consular goes through its opening routine in about 10% the time it used to take on my MBP 17" with 4GB RAM and a regular hard disk. A 90% speed improvement.

The issue though is that many of the tabs won't function properly because they did not switch to the targeted Rails app directory. It looks as if it's going too fast and it does not have time to do so.

This happens both when using the before run routine or trying to cd to the right directory within a block for each tab.

@eric-hu
Copy link

eric-hu commented Aug 30, 2013

@allesklar I have similar hardware, but I don't have your issue. Can you give an example of a consular script that fails?

@ptrikutam
Copy link

Hi @eric-hu,

I have this issue too. It happens for this script:

before { run 'cd ~/Development/clients/client' } 
run 'shotgun -p 5000'
pane do
  run "rvm gemset use client; git status"
  pane "rvm gemset use client; grunt watch"
end

I'm using iTerm 1.0.0.20140629, consular 1.0.3, and consular-iterm 1.0.2

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants