.bash-profile

Trying to get Amazon's EC2 command line tools to work. This is what my .bash_profile looks like. I get the error: /users/zmjones/.ec2/bin/ec2-add-keypair: /usr/bin/env: bad interpreter: Operation not permitted PATH=/usr/bin:/bin:/usr/sbin:/sbin:/opt/local/bin:$PATH PATH=/opt/local/sbin:/usr/local/bin:/usr/x11/bin:/usr/texbin:$PATH PATH=/usr/local/texlive/2011/bin/x86_64-darwin:$PATH PATH=/Library/Frameworks/EPD64.framework/Versions/Current/bin:$PATH EC2_HOME=~/.ec2 PATH=$PATH:$EC2_HOME/bin EC2_PRIVATE_KEY=`ls $EC2_HOME/pk-*.pem` EC2_CERT=`ls $EC2_HOME/cert-*.pem` JAVA_HOME=/System/Library

I have an Xcode project. I tried to integrate OcLint in it. But it says there is no OCLint.How can I download and add OCLint to my system path so that I can integrate OCLint in my xcode project. EDIT: When I have a partof OCLint script as hash oclint &> /dev/null if [ $? -eq 1 ]; then echo >&2 "oclint not found, analyzing stopped" exit 1 fi It gives oclint not found, analyzing stopped . Please give me a solution for this. You can download oclint from : http://archives.oclint.org/nightly/oclint-0.9.dev.02251e4-x86_64-darwin-14.0.0.tar.gz To integarte into your xcode project u could use this

I've ready through other threads on Stack Overflow and despite my efforts the issue doesn't seem to resolve. Since installing OS X Mavericks I'm not able to open Sublime Text 2 from the command line. I've tried following these guidelines: http://benkwok.wordpress.com/2013/11/17/setup-sublime-text-2-on-osx-mavericks-for-ruby-on-rails/ When I run this from the terminal Sublime pops up so that's good: http://benkwok.wordpress.com/2013/11/17/setup-sublime-text-2-on-osx-mavericks-for-ruby-on-rails/ I've added these lines to the bottom of my bash_profile: export PATH=/bin:/sbin:/usr/bin:/usr/local

In Fabric, when I try to use any alias' or functions from my .bash_profile file, they are not recognized. For instance my .bash_profile contains alias c='workon django-canada' , so when I type c in iTerm or Terminal, workon django-canada is executed. My fabfile.py contains def test(): local('c') But when I try fab test it throws this at me: [localhost] local: c /bin/sh: c: command not found Fatal error: local() encountered an error (return code 127) while executing 'c' Aborting. Other Fabric functions work fine. Do I have to specify my bash profile somewhere in fabric? EDIT - As it turns out,

I'm not sure what's happened but my ~/.profile is no longer loading. Can anyone see something wrong with the following? export PS1="\u@local [\w]# " export EDITOR="subl -w" export CLICOLOR=1 export LSCOLORS=GxFxCxDxBxegedabagaced alias vst="ssh -i ~/.ssh/vst root@vst" I know for a fact using that PS1 like I am attempting to do it should be doing Peter@local [~/path/to/file]# but it's not. Any ideas? Gordon Davisson Does ~/.bash_profile or ~/.bash_login exist? If so, that'll be used instead of ~/.profile . In Unix FAQ (for OS X) we can read: Bash Startup Files When a "login shell" starts up, it

I've to set up a local web development environment on my OS X 10.9 and installed Homebrew. Next step in my guide tells me to add logic to my ~/.bash_profile with the following command: echo "export PATH=\$(echo \$PATH | sed 's|/usr/local/bin||; s|/usr/local/sbin||; s|::|:|; s|^:||; s|(.*)|/usr/local/bin:/usr/local/sbin:\1|')" >> ~/.bash_profile && source ~/.bash_profile When I enter it in the terminal I get: sed: 1: "s|/usr/local/bin||; s|/ ...": \1 not defined in the RE Is it export PATH=/usr/local/bin:/usr/local/sbin:$PATH that should be written to my .bash_profile ? And why do I get that

For every project I create I have to do export GOPATH={path_to_project} every time i cd into the project dir. There has to be an easier way. Isn't there some way I can create a .bashrc or .bash_profile file for a given directory to define the GOPATH for that project? For example, I have two go projects A and B. If I have a singular GOPATH that isn't redefined when I move between projects then binaries for both projects will be stored in the same place. More importantly, binaries for third party libraries will be stored in the same place so I have no way of maintaining multiple versions of the