jonallured / dotfiles Goto Github PK

I do this all the time:

cd ..; cd -; rvm current

I should make an alias.

There's a mailcap file that you were playing with, but even a Ruby script that takes stdin and writes a tmp file and then calls to system to open it might be fine.

• pull dotmatrix
• $ brew update
• $ brew upgrade git fzf heroku hub the_silver_searcher yarn
• $ brew cleanup
• $ hr pluginstall
• $ gem update --system
• $ rvm get head
• cleanup desktop
• cleanup screenshots
• cleanup downloads
• empty trash
• update alfred
• update iterm2
• read history to look for alias candidates
• commit and share dotfiles changes
• push changes on secrets
• update list of Artsy repos
• upgrade Xcode
• do system updates
• check free disk space
• verify last backup on time machine
• verify last backup on backblaze
• reboot

https://vi.stackexchange.com/questions/514/how-do-i-change-the-current-splits-width-and-height

There's a setting for this, I just have to find it!

• pull dotmatrix
• $ brew update
• $ brew upgrade git fzf heroku hub the_silver_searcher yarn
• $ brew cleanup
• $ hr pluginstall
• $ gem update --system
• cleanup desktop
• remove screenshots
• update alfred
• read history to look for alias candidates
• commit and share dotfiles changes
• push changes on secrets
• update list of Artsy repos
• upgrade Xcode
• do system updates
• verify last backup on time machine
• verify last backup on backblaze
• reboot

• pull dotmatrix
• $ brew update
• $ brew upgrade git fzf heroku hub the_silver_searcher yarn
• $ brew cleanup
• $ hr pluginstall
• $ gem update --system
• $ rvm get head
• cleanup desktop
• cleanup screenshots
• cleanup downloads
• empty trash
• update alfred
• read history to look for alias candidates
• commit and share dotfiles changes
• push changes on secrets
• update list of Artsy repos
• upgrade Xcode
• do system updates
• verify last backup on time machine
• verify last backup on backblaze
• reboot

• pull dotmatrix
• $ brew update
• $ brew upgrade git fzf heroku hub the_silver_searcher yarn
• $ brew cleanup
• $ hr pluginstall
• $ gem update --system
• $ rvm get head
• cleanup desktop
• cleanup screenshots
• cleanup downloads
• empty trash
• update alfred
• update iterm2
• read history to look for alias candidates
• commit and share dotfiles changes
• push changes on secrets
• update list of Artsy repos
• upgrade Xcode
• do system updates
• check free disk space
• verify last backup on time machine
• reboot

It would be cool for upgrade output during sharpening to be added to those issues as a paper trail of what changed and when. I’m thinking about brew and vim-plug for sure.

• $ brew upgrade git fzf heroku hub the_silver_searcher yarn
• $ brew cleanup
• $ replug
• $ gem update --system
• $ rvm get head
• cleanup desktop
• cleanup screenshots
• cleanup downloads
• empty trash
• update alfred
• update iterm2
• commit and share dotfiles changes
• push changes on secrets
• update list of Artsy repos
• do App Store.app updates
• check free disk space
• verify last backup on time machine
• reboot
• read history to look for alias candidates

• pull dotmatrix
• $ brew update
• $ brew upgrade git fzf heroku hub the_silver_searcher yarn
• $ brew cleanup
• $ hr pluginstall
• $ gem update --system
• $ rvm get head
• cleanup desktop
• cleanup screenshots
• cleanup downloads
• empty trash
• update alfred
• update iterm2
• read history to look for alias candidates
• commit and share dotfiles changes
• push changes on secrets
• update list of Artsy repos
• upgrade Xcode
• do system updates
• check free disk space
• verify last backup on time machine
• reboot

Consider making a tmux session that has general things like gotop and mutt.

• pull dotmatrix
• $ brew update
• $ brew upgrade git fzf heroku hub the_silver_searcher yarn
• $ brew cleanup
• $ hr pluginstall
• $ gem update --system
• $ rvm get head
• cleanup desktop
• cleanup screenshots
• cleanup downloads
• empty trash
• update alfred
• read history to look for alias candidates
• commit and share dotfiles changes
• push changes on secrets
• update list of Artsy repos
• upgrade Xcode
• do system updates
• verify last backup on time machine
• reboot

I just spent the evening tinkering with my tmux status line - that config should be added to this repo.

• pull dotmatrix
• $ brew update
• $ brew upgrade git fzf heroku hub the_silver_searcher yarn
• $ brew cleanup
• $ hr pluginstall
• $ gem update --system
• $ rvm get head
• cleanup desktop
• cleanup screenshots
• cleanup downloads
• empty trash
• update alfred
• read history to look for alias candidates
• commit and share dotfiles changes
• push changes on secrets
• update list of Artsy repos
• upgrade Xcode
• do system updates
• verify last backup on time machine
• verify last backup on backblaze
• reboot

While working on #54 I got this:

jon@magneto:~/code/allocation(artsy-repos)% ruby artsy_repos.rb > ~/code/team-artsy-workflow-data/data/repos.yml
Traceback (most recent call last):
	34: from artsy_repos.rb:8:in `<main>'
	33: from /Users/jon/.rvm/gems/ruby-2.5.1/gems/octokit-4.13.0/lib/octokit/client/organizations.rb:126:in `organization_repositories'
	32: from /Users/jon/.rvm/gems/ruby-2.5.1/gems/octokit-4.13.0/lib/octokit/connection.rb:88:in `paginate'
	31: from /Users/jon/.rvm/gems/ruby-2.5.1/gems/sawyer-0.8.1/lib/sawyer/relation.rb:163:in `get'
	30: from /Users/jon/.rvm/gems/ruby-2.5.1/gems/sawyer-0.8.1/lib/sawyer/relation.rb:264:in `call'
	29: from /Users/jon/.rvm/gems/ruby-2.5.1/gems/sawyer-0.8.1/lib/sawyer/agent.rb:94:in `call'
	28: from /Users/jon/.rvm/gems/ruby-2.5.1/gems/faraday-0.15.3/lib/faraday/connection.rb:138:in `get'
	27: from /Users/jon/.rvm/gems/ruby-2.5.1/gems/faraday-0.15.3/lib/faraday/connection.rb:387:in `run_request'
	26: from /Users/jon/.rvm/gems/ruby-2.5.1/gems/faraday-0.15.3/lib/faraday/rack_builder.rb:143:in `build_response'
	25: from /Users/jon/.rvm/gems/ruby-2.5.1/gems/faraday-0.15.3/lib/faraday/request/retry.rb:128:in `call'
	24: from /Users/jon/.rvm/gems/ruby-2.5.1/gems/octokit-4.13.0/lib/octokit/middleware/follow_redirects.rb:61:in `call'
	23: from /Users/jon/.rvm/gems/ruby-2.5.1/gems/octokit-4.13.0/lib/octokit/middleware/follow_redirects.rb:73:in `perform_with_redirection'
	22: from /Users/jon/.rvm/gems/ruby-2.5.1/gems/faraday-0.15.3/lib/faraday/response.rb:8:in `call'
	21: from /Users/jon/.rvm/gems/ruby-2.5.1/gems/faraday-0.15.3/lib/faraday/response.rb:8:in `call'
	20: from /Users/jon/.rvm/gems/ruby-2.5.1/gems/faraday-0.15.3/lib/faraday/adapter/net_http.rb:38:in `call'
	19: from /Users/jon/.rvm/gems/ruby-2.5.1/gems/faraday-0.15.3/lib/faraday/adapter/net_http.rb:92:in `with_net_http_connection'
	18: from /Users/jon/.rvm/gems/ruby-2.5.1/gems/faraday-0.15.3/lib/faraday/adapter/net_http.rb:43:in `block in call'
	17: from /Users/jon/.rvm/gems/ruby-2.5.1/gems/faraday-0.15.3/lib/faraday/adapter/net_http.rb:85:in `perform_request'
	16: from /Users/jon/.rvm/rubies/ruby-2.5.1/lib/ruby/2.5.0/net/http.rb:1213:in `get'
	15: from /Users/jon/.rvm/rubies/ruby-2.5.1/lib/ruby/2.5.0/net/http.rb:1455:in `request'
	14: from /Users/jon/.rvm/rubies/ruby-2.5.1/lib/ruby/2.5.0/net/http.rb:910:in `start'
	13: from /Users/jon/.rvm/rubies/ruby-2.5.1/lib/ruby/2.5.0/net/http.rb:1457:in `block in request'
	12: from /Users/jon/.rvm/rubies/ruby-2.5.1/lib/ruby/2.5.0/net/http.rb:1464:in `request'
	11: from /Users/jon/.rvm/rubies/ruby-2.5.1/lib/ruby/2.5.0/net/http.rb:1502:in `transport_request'
	10: from /Users/jon/.rvm/rubies/ruby-2.5.1/lib/ruby/2.5.0/net/http/response.rb:165:in `reading_body'
	 9: from /Users/jon/.rvm/rubies/ruby-2.5.1/lib/ruby/2.5.0/net/http.rb:1503:in `block in transport_request'
	 8: from /Users/jon/.rvm/rubies/ruby-2.5.1/lib/ruby/2.5.0/net/http.rb:1214:in `block in get'
	 7: from /Users/jon/.rvm/rubies/ruby-2.5.1/lib/ruby/2.5.0/net/http/response.rb:204:in `read_body'
	 6: from /Users/jon/.rvm/rubies/ruby-2.5.1/lib/ruby/2.5.0/net/http/response.rb:283:in `read_body_0'
	 5: from /Users/jon/.rvm/rubies/ruby-2.5.1/lib/ruby/2.5.0/net/http/response.rb:264:in `inflater'
	 4: from /Users/jon/.rvm/rubies/ruby-2.5.1/lib/ruby/2.5.0/net/http/response.rb:285:in `block in read_body_0'
	 3: from /Users/jon/.rvm/rubies/ruby-2.5.1/lib/ruby/2.5.0/net/http/response.rb:324:in `read_chunked'
	 2: from /Users/jon/.rvm/rubies/ruby-2.5.1/lib/ruby/2.5.0/net/http/response.rb:324:in `ensure in read_chunked'
	 1: from /Users/jon/.rvm/rubies/ruby-2.5.1/lib/ruby/2.5.0/net/protocol.rb:125:in `read'
/Users/jon/.rvm/rubies/ruby-2.5.1/lib/ruby/2.5.0/net/protocol.rb:189:in `rbuf_fill': end of file reached (Faraday::ConnectionFailed)

But it worked on Colossus, so I'm not sure what's going on there.

Also: the way I have this setup is stupid - I should consider another way of organizing this type of script.

• pull dotmatrix
• $ brew update
• $ brew upgrade git fzf heroku hub the_silver_searcher yarn
• $ brew cleanup
• $ hr pluginstall
• $ gem update --system
• cleanup desktop
• remove screenshots
• update alfred
• read history to look for alias candidates
• commit and share dotfiles changes
• push changes on secrets
• update list of Artsy repos
• upgrade Xcode
• do system updates
• reboot
• verify last backup on time machine
• verify last backup on back blaze

• pull dotmatrix
• $ brew upgrade git fzf heroku hub the_silver_searcher yarn
• $ brew cleanup
• $ hr pluginstall
• $ gem update --system
• $ rvm get head
• cleanup desktop
• cleanup screenshots
• cleanup downloads
• empty trash
• update alfred
• update iterm2
• commit and share dotfiles changes
• push changes on secrets
• update list of Artsy repos
• do App Store.app updates
• check free disk space
• verify last backup on time machine
• verify last backup on backblaze
• reboot
• read history to look for alias candidates

10 has been out for a long time, I've had colossus upgraded for quite a while too, so it's time to upgrade both machines to the latest.

See also: https://olivierlacan.com/posts/migrating-homebrew-postgres-to-a-new-version/

• pull dotmatrix
• $ brew update
• $ brew upgrade git fzf heroku hub the_silver_searcher yarn
• $ brew cleanup
• $ hr pluginstall
• $ gem update --system
• $ rvm get head
• cleanup desktop
• cleanup screenshots
• cleanup downloads
• empty trash
• update alfred
• update iterm2
• read history to look for alias candidates
• commit and share dotfiles changes
• push changes on secrets
• update list of Artsy repos
• upgrade Xcode
• do system updates
• check free disk space
• verify last backup on time machine
• reboot

• pull dotmatrix
• $ brew update
• $ brew upgrade git fzf heroku hub the_silver_searcher yarn
• $ brew cleanup
• $ hr pluginstall
• $ gem update --system
• $ rvm get head
• cleanup desktop
• cleanup screenshots
• cleanup downloads
• empty trash
• update alfred
• update iterm2
• read history to look for alias candidates
• commit and share dotfiles changes
• push changes on secrets
• update list of Artsy repos
• upgrade Xcode
• do system updates
• check free disk space
• verify last backup on time machine
• reboot

• pull dotmatrix
• $ brew update
• $ brew upgrade git fzf heroku hub the_silver_searcher yarn
• $ brew cleanup
• $ hr pluginstall
• $ gem update --system
• cleanup desktop
• cleanup screenshots
• cleanup downloads
• empty trash
• update alfred
• read history to look for alias candidates
• commit and share dotfiles changes
• push changes on secrets
• update list of Artsy repos
• upgrade Xcode
• do system updates
• verify last backup on time machine
• verify last backup on backblaze
• reboot

• pull dotmatrix
• $ brew update
• $ brew upgrade git fzf heroku hub the_silver_searcher yarn
• $ brew cleanup
• $ hr pluginstall
• $ gem update --system
• $ rvm get head
• cleanup desktop
• cleanup screenshots
• cleanup downloads
• empty trash
• update alfred
• update iterm2
• read history to look for alias candidates
• commit and share dotfiles changes
• push changes on secrets
• update list of Artsy repos
• upgrade Xcode
• do system updates
• check free disk space
• verify last backup on time machine
• verify last backup on backblaze
• reboot

• pull dotmatrix
• $ brew update
• $ brew upgrade git fzf heroku hub the_silver_searcher yarn
• $ brew cleanup
• $ hr pluginstall
• $ gem update --system
• $ rvm get head
• cleanup desktop
• cleanup screenshots
• cleanup downloads
• empty trash
• update alfred
• update iterm2
• read history to look for alias candidates
• commit and share dotfiles changes
• push changes on secrets
• update list of Artsy repos
• upgrade Xcode
• do system updates
• check free disk space
• verify last backup on time machine
• verify last backup on backblaze
• reboot

There are a few Artsy projects with pre-commit or pre-push hooks that get in the way of fetchup - let's disable them by adding --no-verify to that command.

It's time

https://github.com/thoughtbot/rcm

• $ brew upgrade git fzf heroku hub the_silver_searcher yarn
• $ replug
• $ gem update --system
• pull latest asdf
• cleanup desktop
• cleanup screenshots
• cleanup downloads
• empty trash
• update alfred
• update iterm2
• commit and share dotfiles changes
• push changes on secrets
• update list of Artsy repos
• do App Store.app updates
• check free disk space
• verify last backup on time machine
• reboot

• pull dotmatrix
• $ brew update
• $ brew upgrade git fzf heroku hub the_silver_searcher yarn
• $ brew cleanup
• $ hr pluginstall
• $ gem update --system
• $ rvm get head
• cleanup desktop
• cleanup screenshots
• cleanup downloads
• empty trash
• update alfred
• update iterm2
• read history to look for alias candidates
• commit and share dotfiles changes
• push changes on secrets
• update list of Artsy repos
• upgrade Xcode
• do system updates
• check free disk space
• verify last backup on time machine
• reboot

I have this ritual I do to create my "standard" tmux arrangement - I should have a tmux binding for that.

I had the idea that when working in Javascript project I tend to want to split the current file and then hit - to switch to a sibling file. Here is what I was thinking:

:spop - do a horizontal split and pop up to the containing folder
:vpop - do a vertical split and pop up to the containing folder

• pull dotmatrix
• $ brew upgrade git fzf heroku hub the_silver_searcher yarn
• $ brew cleanup
• $ hr pluginstall
• $ gem update --system
• $ rvm get head
• cleanup desktop
• cleanup screenshots
• cleanup downloads
• empty trash
• update alfred
• update iterm2
• commit and share dotfiles changes
• push changes on secrets
• update list of Artsy repos
• do App Store.app updates
• check free disk space
• verify last backup on time machine
• verify last backup on backblaze
• reboot
• read history to look for alias candidates

It just occurred to me that it should be possible to script the removal of old gemsets as projects upgrade their Ruby version.

• pull dotmatrix
• $ brew update
• $ brew upgrade git fzf heroku hub the_silver_searcher yarn
• $ brew cleanup
• $ hr pluginstall
• $ gem update --system
• $ rvm get head
• cleanup desktop
• cleanup screenshots
• cleanup downloads
• empty trash
• update alfred
• read history to look for alias candidates
• commit and share dotfiles changes
• push changes on secrets
• update list of Artsy repos
• upgrade Xcode
• do system updates
• verify last backup on time machine
• reboot

• pull dotmatrix
• $ brew update
• $ brew upgrade git fzf heroku hub the_silver_searcher yarn
• $ brew cleanup
• $ hr pluginstall
• $ gem update --system
• cleanup desktop
• remove screenshots
• update alfred
• read history to look for alias candidates
• commit and share dotfiles changes
• push changes on secrets
• update list of Artsy repos
• upgrade Xcode
• do system updates
• verify last backup on time machine
• verify last backup on backblaze
• reboot

• pull dotmatrix
• $ brew update
• $ brew upgrade git fzf heroku hub the_silver_searcher yarn
• $ brew cleanup
• $ hr pluginstall
• $ gem update --system
• $ rvm get head
• cleanup desktop
• cleanup screenshots
• cleanup downloads
• empty trash
• update alfred
• update iterm2
• read history to look for alias candidates
• commit and share dotfiles changes
• push changes on secrets
• update list of Artsy repos
• upgrade Xcode
• do system updates
• check free disk space
• verify last backup on time machine
• verify last backup on backblaze
• reboot

• pull dotmatrix
• $ brew upgrade git fzf heroku hub the_silver_searcher yarn
• $ brew cleanup
• $ hr pluginstall
• $ gem update --system
• $ rvm get head
• cleanup desktop
• cleanup screenshots
• cleanup downloads
• empty trash
• update alfred
• update iterm2
• commit and share dotfiles changes
• push changes on secrets
• update list of Artsy repos
• do App Store.app updates
• check free disk space
• verify last backup on time machine
• verify last backup on backblaze
• reboot

• pull dotmatrix
• $ brew upgrade git fzf heroku hub the_silver_searcher yarn
• $ brew cleanup
• $ hr pluginstall
• $ gem update --system
• $ rvm get head
• cleanup desktop
• cleanup screenshots
• cleanup downloads
• empty trash
• update alfred
• update iterm2
• commit and share dotfiles changes
• push changes on secrets
• update list of Artsy repos
• do App Store.app updates
• check free disk space
• verify last backup on time machine
• reboot

I often type this:

$ fetchup && git delete-merged-branches

But it would be cooler to type this:

$ fetchup && dmb

• pull dotmatrix
• $ brew upgrade git fzf heroku hub the_silver_searcher yarn
• $ brew cleanup
• $ hr pluginstall
• $ gem update --system
• $ rvm get head
• cleanup desktop
• cleanup screenshots
• cleanup downloads
• empty trash
• update alfred
• update iterm2
• commit and share dotfiles changes
• push changes on secrets
• update list of Artsy repos
• do App Store.app updates
• check free disk space
• verify last backup on time machine
• reboot
• read history to look for alias candidates

I noticed today that I don't have my shortcut to the sell Jira board on colossus - I should be syncing these things between my machines.

• pull dotmatrix
• $ brew update
• $ brew upgrade git fzf heroku hub the_silver_searcher yarn
• $ brew cleanup
• $ hr pluginstall
• $ gem update --system
• cleanup desktop
• remove screenshots
• update alfred
• read history to look for alias candidates
• commit and share dotfiles changes
• push changes on secrets
• update list of Artsy repos
• upgrade Xcode
• do system updates
• reboot
• verify last backup on time machine
• verify last backup on back blaze

Say volt done and leap

• pull dotmatrix
• $ brew update
• $ brew upgrade git fzf heroku hub the_silver_searcher yarn
• $ brew cleanup
• $ hr pluginstall
• $ gem update --system
• cleanup desktop
• cleanup screenshots
• cleanup downloads
• empty trash
• update alfred
• read history to look for alias candidates
• commit and share dotfiles changes
• push changes on secrets
• update list of Artsy repos
• upgrade Xcode
• do system updates
• verify last backup on time machine
• verify last backup on backblaze
• reboot

I'd like to do this on my laptop before trying it on my desktop in case something weird happens.

I'm putting my mutt creds in my secrets repo, but I'm now noticing that I don't have it setup to use symlinks like this repo. This means I have to manually keep these files in sync, which is dumb.

It would be something that creates a tmux session named mutt and then sends the mutt commands and arranges the panes correctly.

• pull dotmatrix
• $ brew update
• $ brew upgrade git fzf heroku hub the_silver_searcher yarn
• $ brew cleanup
• $ hr pluginstall
• $ gem update --system
• $ rvm get head
• cleanup desktop
• cleanup screenshots
• cleanup downloads
• empty trash
• update alfred
• update iterm2
• read history to look for alias candidates
• commit and share dotfiles changes
• push changes on secrets
• update list of Artsy repos
• upgrade Xcode
• do system updates
• check free disk space
• verify last backup on time machine
• verify last backup on backblaze
• reboot

I made a really nice mux file for Volt, but it's not being shared or anything. I should find a better solution for project-specific tmux config like this.

• pull dotmatrix
• $ brew upgrade git fzf heroku hub the_silver_searcher yarn
• $ brew cleanup
• $ hr pluginstall
• $ gem update --system
• $ rvm get head
• cleanup desktop
• cleanup screenshots
• cleanup downloads
• empty trash
• update alfred
• update iterm2
• commit and share dotfiles changes
• push changes on secrets
• update list of Artsy repos
• do App Store.app updates
• check free disk space
• verify last backup on time machine
• verify last backup on backblaze
• reboot
• read history to look for alias candidates