Joined September 2013
·

Anton DeVore

Software Developer 1 at Marchex
·
Seattle, WA
·
·

Posted to Update remote branch list over 1 year ago

If the remote branches don't exist anymore, won't a simple 'git pull' prune the remote branch list?

This assumes you have all branches checked out. "git branch -r --merged" will give you all remote branches that are merged in to whatever your current branch is. Also, depending on your branching strategy and how you deal with bugs or hotfixes, you may want to filter on how long it's been since the branch was touched.

Why the "grep -v dev"?

Posted to Writing Great Documentation over 1 year ago

Comments should be sparse but I like to use them if the code/business logic might not be intuitive. You might ask why isn't it more intuitive and some times it just can't be done or maybe the style of the language makes it less intuitive. I don't know where I saw this but, "well written code is like a good joke, it doesn't need an explanation"

Posted to Scala Code Coverage over 1 year ago

Excellent

Posted to Spell check in VIM over 1 year ago

Have you figured out how to put it into your .vimrc?

Posted to Vim repeat subsitution over 1 year ago

:%s/foo/bar // start from the top of the file and do them all
:%s/foo/bar/c // start from the top of the file and confirm you want to do it

Where are the logs stored? What do they look like? Do you find them useful?

To note, Ctrl+w t brings you to the top left screen. You can do Ctrl+w K and Ctrl+w H from any screen with any number of screens. Behaves interestingly when you have both vertical and horizontal screens. If you have more than 2 vertical screens and you hit Ctrl+w H, it will rotate the screen you're on with any screens to the left of that in a queue sort of way. Example, you have screens A B C, you hit Ctrl+w H on screen C, you end up with C A B.

How would you do it in Linux?

Posted to Vim auto-indent (4 spaces) over 1 year ago

I encourage anyone modifying their vimrc to understand why they are setting something. As for me I haven't yet determine what smartindent does and I've grabbed these settings from various other people's vimrcs.

set autoindent " always set autoindenting on

set copyindent " copy the previous indentation on autoindenting

set expandtab " expand tabs by default (overloadable per file type)

set shiftround " use multiple of shiftwidth when indenting with '<' and '>'

set shiftwidth=2 " number of spaces to use for autoindenting

set smartindent

set smarttab " insert tabs on the start of a line according to shiftwidth, not tabstop

set softtabstop=2 " when hitting <BS>, pretend like a tab is removed, even if spaces

set tabstop=2 " tabs are n spaces

I think you meant to say camelCase notation not cameCase when describing naming response fields. I like the tip though :)

Achievements
31 Karma
0 Total ProTip Views