automux 0.0.1

data/.gitignore

@@ -0,0 +1,5 @@
+*.gem
+.rvmrc
+.bundle
+tmp
+ignored.yml

data/Gemfile

@@ -0,0 +1,6 @@
+source 'https://rubygems.org'
+require 'bundler'
+
+group :test do
+  gem 'cucumber'
+end

data/Gemfile.lock

@@ -0,0 +1,20 @@
+GEM
+  remote: https://rubygems.org/
+  specs:
+    builder (3.2.0)
+    cucumber (1.2.3)
+      builder (>= 2.1.2)
+      diff-lcs (>= 1.1.3)
+      gherkin (~> 2.11.6)
+      multi_json (~> 1.3)
+    diff-lcs (1.2.1)
+    gherkin (2.11.6)
+      json (>= 1.7.6)
+    json (1.7.7)
+    multi_json (1.7.1)
+
+PLATFORMS
+  ruby
+
+DEPENDENCIES
+  cucumber

data/LICENSE.txt

@@ -0,0 +1,22 @@
+Copyright (c) 2013 Alex Johnson
+
+MIT License
+
+Permission is hereby granted, free of charge, to any person obtaining
+a copy of this software and associated documentation files (the
+"Software"), to deal in the Software without restriction, including
+without limitation the rights to use, copy, modify, merge, publish,
+distribute, sublicense, and/or sell copies of the Software, and to
+permit persons to whom the Software is furnished to do so, subject to
+the following conditions:
+
+The above copyright notice and this permission notice shall be
+included in all copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND,
+EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF
+MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND
+NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE
+LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION
+OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION
+WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.

data/VERSION

@@ -0,0 +1 @@
+ 0.0.1

data/automux.gemspec

@@ -0,0 +1,18 @@
+# -*- encoding: utf-8 -*-
+
+$:.push File.expand_path("../lib", __FILE__)
+
+Gem::Specification.new do |gem|
+  gem.name          = "automux"
+  gem.version       = File.read('VERSION').strip.chomp
+  gem.authors       = ["Alex Johnson"]
+  gem.email         = ["notalexjohnson@gmail.com"]
+  gem.description   = %[Automating Tmux Configuration]
+  gem.summary       = %[Automux can automate tmux sessions by reading configuration from yaml files]
+  gem.homepage      = "https://github.com/notalex/automux"
+
+  gem.files         = `git ls-files`.split($/)
+  gem.executables   = gem.files.grep(%r{^bin/}).map{ |f| File.basename(f) }
+  gem.test_files    = gem.files.grep(%r{^(test|spec|features)/})
+  gem.require_paths = ["lib"]
+end

data/bin/automux

@@ -0,0 +1,22 @@
+#! /usr/bin/env ruby
+
+lib_path = File.expand_path('../../lib', __FILE__)
+$LOAD_PATH.unshift(lib_path) unless $LOAD_PATH.include?(lib_path)
+
+require 'automux'
+
+args = ARGV.take_while { |argument| argument.match(/^\w/) }
+
+case args[0]
+when 'setup'
+  Automux::Controller::Setup.new.clone_defaults
+when 'blueprint'
+  params = { name: args[2], clone_name: args[3] }
+  Automux::Controller::Blueprints.new(params).send(args[1])
+else
+  params = {
+    blueprint_name: args[0] || 'default',
+    recipe_name:    args[1] || 'default'
+  }
+  Automux::Controller::Recipes.new(params).automate
+end

data/data/automux/blueprints/default.yml

@@ -0,0 +1,26 @@
+name: test
+root: ~/
+flags: -u2
+options:
+  status: off
+windows:
+  - name: panes
+    layout: main-vertical
+    panes:
+      - irb
+      - top
+      - ls
+  - name: vim
+    hooks:
+      pre: 
+        - echo 'Starting vim'
+    panes: vim
+  - name: custom-indexed-window
+    index: 1
+    hooks:
+      post:
+        - echo 'Running <%= name %>'
+  - name: optional-window
+    opt: '-r'
+    panes:
+      - echo 'Created optional window'

data/data/automux/recipes/default.sh.erb

@@ -0,0 +1,46 @@
+cd <%= root %>
+
+- pre_hooks.each do |hook|
+  = hook.command
+- end
+
+= start_server
+= new_session
+
+- options.each do |option|
+  = set_option(option)
+- end
+
+- windows.each do |window|
+  = new_window(window)
+  = rename_window(window) if window.name
+
+  - if window.has_panes?
+    = send_keys(window, window.change_root_command) if window.root
+
+    - window.pre_hooks.each do |hook|
+      = send_keys(window, hook.command)
+    - end
+
+    - window.panes.each do |pane|
+      = create_pane if pane.index > 0
+      = send_keys(window, pane.command)
+    - end
+
+    - window.options.each do |option|
+      = window.set_option(option)
+    - end
+
+    - window.post_hooks.each do |hook|
+      = send_keys(window, hook.command)
+    - end
+
+    = select_layout(window) if window.layout
+  - end
+- end
+
+= attach_session
+
+- post_hooks.each do |hook|
+  = hook.command
+- end

data/features/custom_recipes.feature

@@ -0,0 +1,63 @@
+Feature: User using a custom recipe
+
+  Scenario: Simple recipe with no tmux related code
+    Given I have the following recipe named "test_recipe"
+      """
+      echo using the <%= name %> blueprint
+      """
+      And I have the following blueprint named "test_sample"
+        """
+        name: test
+        windows:
+          - panes: vim
+        """
+    When I invoke Automux with the recipe "test_recipe" and the blueprint "default"
+    Then the rendered sequence of shell commands should be
+      """
+      echo using the test blueprint
+      """
+
+  Scenario: Using a recipe that skips the hooks and options features
+    Given I have the following recipe named "test_recipe"
+      """
+      cd <%= root %>
+
+      = start_server
+      = new_session
+
+      - windows.each do |window|
+        = new_window(window)
+
+        - window.panes.each do |pane|
+          = create_pane if pane.index > 0
+          = send_keys(window, pane.command)
+        - end
+      - end
+
+      = attach_session
+      """
+      And I have the following blueprint named "test_sample"
+        """
+        name: test
+        options:
+          status: off
+        windows:
+          - name: vim
+            hooks:
+              pre: echo Hello
+            index: 2
+            panes: vim
+        """
+    When I invoke Automux with the recipe "test_recipe" and the blueprint "test_sample"
+    Then the rendered sequence of shell commands should be
+      """
+      cd .
+
+      tmux start-server
+      tmux new-session -d -s test
+
+      tmux new-window -t test:2 2> /dev/null
+      tmux send-keys -t test:2 "vim" C-m
+
+      tmux attach-session -t test
+      """

data/features/error_messages.feature

@@ -0,0 +1,8 @@
+Feature: Handling various errors with relevant messages
+
+  Scenario: Trying to use a non existing blueprint
+    When I invoke Automux with the blueprint "test_sample"
+    Then the rendered sequence of shell commands should contain
+      """
+      echo No matching blueprint found
+      """

data/features/general_usage.feature

@@ -0,0 +1,180 @@
+Feature: User entering a blueprint from commandline
+As an Automux user
+I want to run Automux with a blueprint
+In order to run the shell commands matching the given blueprint
+
+  Scenario: A 4 window blueprint with some fixed indexes and subpanes
+    Given I have the following blueprint named "test_sample"
+      """
+      name: test
+      root: ~/projects
+      windows:
+        - name: editor
+          layout: main-vertical
+          panes:
+            - ls
+            - top
+            - pwd
+        - name: htop
+          panes: htop
+        - name: tester
+          index: 1
+          panes:
+            - pwd
+        - name: zero
+          index: 0
+          panes: [pwd, echo hello]
+      """
+    When I invoke Automux with the blueprint "test_sample"
+    Then the rendered sequence of shell commands should be
+      """
+      cd ~/projects
+
+      tmux start-server
+      tmux new-session -d -s test
+
+      tmux new-window -t test:2 2> /dev/null
+      tmux rename-window -t test:2 editor
+
+      tmux send-keys -t test:2 "ls" C-m
+      tmux split-window
+      tmux send-keys -t test:2 "top" C-m
+      tmux split-window
+      tmux send-keys -t test:2 "pwd" C-m
+      tmux select-layout -t test:2 main-vertical
+
+      tmux new-window -t test:3 2> /dev/null
+      tmux rename-window -t test:3 htop
+      tmux send-keys -t test:3 "htop" C-m
+
+      tmux new-window -t test:1 2> /dev/null
+      tmux rename-window -t test:1 tester
+      tmux send-keys -t test:1 "pwd" C-m
+
+      tmux new-window -t test:0 2> /dev/null
+      tmux rename-window -t test:0 zero
+      tmux send-keys -t test:0 "pwd" C-m
+      tmux split-window
+      tmux send-keys -t test:0 "echo hello" C-m
+
+      tmux attach-session -t test
+      """
+
+  Scenario: Windows with clashing index values
+    Given I have the following blueprint named "test_sample"
+      """
+      name: test
+      root: '~'
+      windows:
+        - name: editor
+          panes: vim
+          index: 1
+        - name: top
+          panes: top
+          index: 1
+      """
+    When I invoke Automux with the blueprint "test_sample"
+    Then the rendered sequence of shell commands should be
+      """
+      cd ~
+
+      tmux start-server
+      tmux new-session -d -s test
+
+      tmux new-window -t test:1 2> /dev/null
+      tmux rename-window -t test:1 editor
+      tmux send-keys -t test:1 "vim" C-m
+
+      tmux new-window -t test:0 2> /dev/null
+      tmux rename-window -t test:0 top
+      tmux send-keys -t test:0 "top" C-m
+
+      tmux attach-session -t test
+      """
+
+  Scenario: Only session name is provided
+    Given I have the following blueprint named "test_sample"
+      """
+      name: window-less
+      """
+    When I invoke Automux with the blueprint "test_sample"
+    Then the rendered sequence of shell commands should be
+      """
+      cd .
+
+      tmux start-server
+      tmux new-session -d -s window-less
+
+      tmux attach-session -t window-less
+      """
+
+  Scenario: Providing no name for a window
+    Given I have the following blueprint named "test_sample"
+      """
+      name: name-less
+      windows:
+        - panes: git pull origin master
+      """
+    When I invoke Automux with the blueprint "test_sample"
+    Then the rendered sequence of shell commands should be
+      """
+      cd .
+
+      tmux start-server
+      tmux new-session -d -s name-less
+
+      tmux new-window -t name-less:0 2> /dev/null
+      tmux send-keys -t name-less:0 "git pull origin master" C-m
+
+      tmux attach-session -t name-less
+      """
+
+  Scenario: Providing flags for tmux
+    Given I have the following blueprint named "test_sample"
+      """
+      name: flagged
+      flags: -u2
+      windows:
+        - panes: vim
+      """
+    When I invoke Automux with the blueprint "test_sample"
+    Then the rendered sequence of shell commands should be
+      """
+      cd .
+
+      tmux start-server
+      tmux -u2 new-session -d -s flagged
+
+      tmux new-window -t flagged:0 2> /dev/null
+      tmux send-keys -t flagged:0 "vim" C-m
+
+      tmux -u2 attach-session -t flagged
+      """
+
+  Scenario: Windows with separate roots
+    Given I have the following blueprint named "test_sample"
+      """
+      name: test
+      root: '~'
+      windows:
+        - panes: vim
+          root: 'projects'
+        - panes: top
+      """
+    When I invoke Automux with the blueprint "test_sample"
+    Then the rendered sequence of shell commands should be
+      """
+      cd ~
+
+      tmux start-server
+      tmux new-session -d -s test
+
+      tmux new-window -t test:0 2> /dev/null
+      tmux send-keys -t test:0 "cd projects" C-m
+      tmux send-keys -t test:0 "vim" C-m
+
+      tmux new-window -t test:1 2> /dev/null
+      tmux send-keys -t test:1 "top" C-m
+
+      tmux attach-session -t test
+      """

data/features/managing_blueprints.feature

@@ -0,0 +1,66 @@
+Feature: Creating, Cloning, Editing and Deleting Blueprints
+
+  Scenario: Editing a blueprint
+    Given I have the following blueprint named "test_sample"
+      """
+      name: created-using-cuke
+      windows:
+        - panes: ls
+      """
+    When I invoke Automux to "edit" the blueprint "test_sample"
+    Then the rendered sequence of shell commands should be
+      """
+      $EDITOR $HOME/.automux/blueprints/test_sample.yml
+      """
+
+  Scenario: Creating a new blueprint
+    When I invoke Automux to "create" the blueprint "test_sample"
+    Then the rendered sequence of shell commands should be
+      """
+      cp $HOME/.automux/blueprints/default.yml $HOME/.automux/blueprints/test_sample.yml
+      $EDITOR $HOME/.automux/blueprints/test_sample.yml
+      """
+
+  Scenario: Copying a blueprint
+    When I call Automux to "copy" the blueprint "default" as "test_sample"
+    Then the rendered sequence of shell commands should be
+      """
+      cp $HOME/.automux/blueprints/default.yml $HOME/.automux/blueprints/test_sample.yml
+      echo default.yml copied
+      """
+
+  Scenario: Using an alias to copy blueprint
+    When I call Automux to "cp" the blueprint "default" as "test_sample"
+    Then the rendered sequence of shell commands should be
+      """
+      cp $HOME/.automux/blueprints/default.yml $HOME/.automux/blueprints/test_sample.yml
+      echo default.yml copied
+      """
+
+  Scenario: Deleting a blueprint
+    Given I have the following blueprint named "test_sample"
+      """
+      name: created-using-cuke
+      windows:
+        - panes: ls
+      """
+    When I invoke Automux to "delete" the blueprint "test_sample"
+    Then the rendered sequence of shell commands should be
+      """
+      rm $HOME/.automux/blueprints/test_sample.yml
+      echo test_sample.yml deleted
+      """
+
+  Scenario: Deleting blueprint using the alias
+    Given I have the following blueprint named "test_sample"
+      """
+      name: created-using-cuke
+      windows:
+        - panes: ls
+      """
+    When I invoke Automux to "rm" the blueprint "test_sample"
+    Then the rendered sequence of shell commands should be
+      """
+      rm $HOME/.automux/blueprints/test_sample.yml
+      echo test_sample.yml deleted
+      """