2012-12-27

Entries

Okay, gonna try to tackle getting vim to copy to the Mac's system clipboard

#

vim --version shows that I have vim 7.2.

#

This vim tip Mac OS X clipboard sharing suggests that having 7.3 lets you copy to the system clipboard

#

It's not possible to install vim via homebrew. No formula available and it tells you to use the built-in vim anyways.

#

I like my vim/tmux setup, so I'm don't really want to switch to MacVim

#

Okay, this got vim 7.3 installed for me: Compile Vim on OSX (Mountain Lion)

#

And you DO have to use Ruby 1.9.1 to get it to work.

#

Now I just need to fix the fact that /usr/bin/vim comes before /usr/local/bin/vim in my PATH.

#

But I confirmed that I can now copy to the clipboard from vim!

#

Next is getting tmux to copy to the system buffer. Just did a test and it currently doesn't work.

#

Gonna give this a try: How to Copy and Paste with Tmux on Mac OS X

#

That didn't seem to help, but I don't think I really ever copy from tmux.

#

vim is where I really need the support, especially when trying to copy from a split where I don't want line numbers and the other side of the split showing up.

#

Tim Pope provides a vim bundle for Cucumber: vim-cucumber

#

Submitted an Issue I've been having with jekyll-s3: jekyll-s3 doesn't make files world readable when using a version greater than 0.0.5

#

And there's Cucumber support for Guard: guard-cucumber

#

And pygments supports Cucumber! Huzzah!

#

Had a weird Guard issue where every time it ran it would then drop to a Pry prompt like [1] guard(main)>.

#

This closed issue Guard not running after a file change provided a solution.

#

I added interactor :off to the top of my Guardfile

#

One weird side effect of compiling and installing vim 7.3 from scratch - the delete key doesn't work in insert mode.

#

Finished Chapters 1 and 2 of The Cucumber Book. I understand the basic syntax and usage of Cucumber but still am hazy on where I should use RSpec/Unit Tests and where I should use Cucumber/BDD. Hopefully that will become clearer as I read more.

#

Regarding the issue I was havving with jekyll-s3, somebody suggested I look into bucket policies so I did.

#

With the new UI you have to go into S3, right-click on your bucket and choose Properties. Then under the Permissions section choose Add Bucket Policy.

#

I followed the link to Sample Bucket Policies and copied the one named Granting Permission to an Anonymous User.

#

I replaced bucket in "Resource":["arn:aws:s3:::bucket/*" with my own bucket name.

#

After switching to jekyll-s3 2.0.0, adding these notes and running jekyll-s3 I see that it only updated this page (since it's the only one that changed) and seems to be using the policy I put in place.

#

At work I'm on OS X 10.6 but at home I'm on OS X 10.8 (Mountain Lion) and ran into an issue while trying to compile vim.

#

sed: RE error: illegal byte sequence regarding the file /usr/local/share/vim/vim73/tools/efm_perl.pl

#

I found this issue about it, which seems to be a problem with sed in Mountain Lion - Issue 63 in vim: sed: RE error: illegal byte sequence

#

I fixed it using the suggestion to use iconv -c -t UTF-8 ./runtime/tools/efm_perl.pl > ./runtime/tools/efm_perl.pl to change that file's encoding from latin1 to UTF-8.

#

Ugh, now when I use FuzzyFinder in vim I get the following error Error detected while processing modelines: followed by E518: Unknown option: sed

#

Also got this when starting vim: E474: Invalid argument: listchars=tab:?~V?\ ,eol:

#

I decided to remove that line since I wasn't using invisible characters in vim anyways

#

I think that fixed the FuzzyFinger issue as well?

#

Comments

comments powered by Disqus