:e. # list current directory
:bd # leave a directory listing
:put + # paste from clipoard, this works
"+p # paste while in normal mode from clipboard
u # undo in normal mode
ctrl+r # redo in normal mode
puphpet-ubuntu-ubuntu1404-x64_vm $ VAGRANT_LOG=debug vagrant up --provider vmware_fusion | |
INFO global: Vagrant version: 1.7.4 | |
INFO global: Ruby version: 2.0.0 | |
INFO global: RubyGems version: 2.0.14 | |
INFO global: VAGRANT_LOG="debug" | |
INFO global: VAGRANT_OLD_ENV_GEM_HOME="/Users/dave/.rvm/gems/ruby-2.0.0-p598" | |
INFO global: VAGRANT_OLD_ENV_IRBRC="/Users/dave/.rvm/rubies/ruby-2.0.0-p598/.irbrc" | |
INFO global: VAGRANT_OLD_ENV__system_type="Darwin" | |
INFO global: VAGRANT_OLD_ENV___CF_USER_TEXT_ENCODING="0x1F5:0x0:0x0" | |
INFO global: VAGRANT_OLD_ENV_RUBY_VERSION="ruby-2.0.0-p598" |
Command-T documentation says it should be built using the Ruby version you intend to use in Vim/MacVim (System is recommended).
I could get the Homebrew installed version of Vim setup with my Ruby 1.9.3 along with Command-T in 1.9.3, but couldn't make it work for MacVim. So, if I tried to used Command-T in MacVim I got the Caught deadly signal SEGV error
.
Originally I tried to install MacVim using Homebrew, but then in MacVim :ruby puts RUBY_VERSION will show 1.8.7 even though the brew install was done with my RVM's Ruby set to 1.9.3
I decided after asking on stackoverflow and learning about how to see mvim --version
and vim --version
and the Linking:
to try a non brew install using the [build guide for MacVim](https://github.com/b4wi
###Basic setup outline (This may be wrong but it roughly contains everything you've been doing. Check the references for more info.)
class Die | |
def roll_die | |
rand(1..6) | |
end | |
end | |
class CrapsGame | |
attr_accessor :point, :dice_roll | |
def pass |
class Die | |
def roll_die | |
rand(1..6) | |
end | |
end | |
class CrapsShooter | |
attr_accessor :point, :dice_roll, :game_over | |
def crap_out? |
set :application, 'deployrails.yo' | |
set :repo_url, 'http://repo.workalicio.us/deployrails1103.git' | |
set :deploy_to, '/home/vagrant/deployrails' | |
set :scm, :git | |
set :deploy_via, :copy | |
set :branch, 'master' | |
set :format, :pretty | |
set :log_level, :debug |
Update 03-03-2015
I've moved over to a new MacBookPro running 10.10.2. I think I'm going to leave POW off this machine. I've been trying to use more Vagrant VMs in general, but the Localhost is so fast for just getting something in the browser, especially when testing things out on the front end in the browser. One thing I'm noticing about the 2nd approach is that the build with a vhost works great, but just getting the .git setup was a little tricky. I had to make the main directory, the build directory and git init
in each. Then, I added the remotes from the working (development) repository for the source and the staging server repo for the build. Looks like I might install Passenger on this new machine so that I can use a vhost for the source files. Otherwise I need to use the http://0.0.0.0:4567/
or http://localhost:4567/
which isn't a bad thing vs installing Passenger?
Udpate 03-03-2015
Wow, just installed Phusion Passenger in about 15min using the g
work-ubuntu-fpm-pool $ VAGRANT_LOG=debug vagrant up --provider vmware_fusion | |
INFO global: Vagrant version: 1.8.4 | |
INFO global: Ruby version: 2.2.3 | |
INFO global: RubyGems version: 2.4.5.1 | |
INFO global: VAGRANT_LOG="debug" | |
INFO global: VAGRANT_OLD_ENV_SHLVL="1" | |
INFO global: VAGRANT_OLD_ENV_LOGNAME="dave" | |
INFO global: VAGRANT_OLD_ENV_SHELL="/bin/bash" | |
INFO global: VAGRANT_OLD_ENV_TERM="xterm-256color" | |
INFO global: VAGRANT_OLD_ENV_SSH_AUTH_SOCK="/private/tmp/com.apple.launchd.DyF4qytHET/Listeners" |