jonallured / dotfiles Goto Github PK
View Code? Open in Web Editor NEWHere be my dotfiles
Here be my dotfiles
It's time
Say volt done and leap
$ brew upgrade git fzf heroku hub the_silver_searcher yarn
$ brew cleanup
$ hr pluginstall
$ gem update --system
$ rvm get head
$ brew update
$ brew upgrade git fzf heroku hub the_silver_searcher yarn
$ brew cleanup
$ hr pluginstall
$ gem update --system
$ rvm get head
It would be something that creates a tmux session named mutt and then sends the mutt commands and arranges the panes correctly.
$ brew update
$ brew upgrade git fzf heroku hub the_silver_searcher yarn
$ brew cleanup
$ hr pluginstall
$ gem update --system
$ rvm get head
$ brew update
$ brew upgrade git fzf heroku hub the_silver_searcher yarn
$ brew cleanup
$ hr pluginstall
$ gem update --system
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/
$ brew update
$ brew upgrade git fzf heroku hub the_silver_searcher yarn
$ brew cleanup
$ hr pluginstall
$ gem update --system
$ rvm get head
I do this all the time:
cd ..; cd -; rvm current
I should make an alias.
$ brew update
$ brew upgrade git fzf heroku hub the_silver_searcher yarn
$ brew cleanup
$ hr pluginstall
$ gem update --system
$ rvm get head
$ brew update
$ brew upgrade git fzf heroku hub the_silver_searcher yarn
$ brew cleanup
$ hr pluginstall
$ gem update --system
$ rvm get head
Consider making a tmux session that has general things like gotop
and mutt
.
$ brew update
$ brew upgrade git fzf heroku hub the_silver_searcher yarn
$ brew cleanup
$ hr pluginstall
$ gem update --system
$ rvm get head
$ brew update
$ brew upgrade git fzf heroku hub the_silver_searcher yarn
$ brew cleanup
$ hr pluginstall
$ gem update --system
I'd like to do this on my laptop before trying it on my desktop in case something weird happens.
$ brew update
$ brew upgrade git fzf heroku hub the_silver_searcher yarn
$ brew cleanup
$ hr pluginstall
$ gem update --system
$ rvm get head
$ brew update
$ brew upgrade git fzf heroku hub the_silver_searcher yarn
$ brew cleanup
$ hr pluginstall
$ gem update --system
$ brew update
$ brew upgrade git fzf heroku hub the_silver_searcher yarn
$ brew cleanup
$ hr pluginstall
$ gem update --system
$ rvm get head
There's a setting for this, I just have to find it!
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.
$ brew upgrade git fzf heroku hub the_silver_searcher yarn
$ brew cleanup
$ hr pluginstall
$ gem update --system
$ rvm get head
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.
I just spent the evening tinkering with my tmux status line - that config should be added to this repo.
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.
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.
$ brew update
$ brew upgrade git fzf heroku hub the_silver_searcher yarn
$ brew cleanup
$ hr pluginstall
$ gem update --system
$ rvm get head
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.
$ brew update
$ brew upgrade git fzf heroku hub the_silver_searcher yarn
$ brew cleanup
$ hr pluginstall
$ gem update --system
$ rvm get head
$ brew upgrade git fzf heroku hub the_silver_searcher yarn
$ brew cleanup
$ hr pluginstall
$ gem update --system
$ rvm get head
I often type this:
$ fetchup && git delete-merged-branches
But it would be cooler to type this:
$ fetchup && dmb
$ brew upgrade git fzf heroku hub the_silver_searcher yarn
$ brew cleanup
$ hr pluginstall
$ gem update --system
$ rvm get head
$ brew update
$ brew upgrade git fzf heroku hub the_silver_searcher yarn
$ brew cleanup
$ hr pluginstall
$ gem update --system
$ rvm get head
$ brew update
$ brew upgrade git fzf heroku hub the_silver_searcher yarn
$ brew cleanup
$ hr pluginstall
$ gem update --system
$ rvm get head
It just occurred to me that it should be possible to script the removal of old gemsets as projects upgrade their Ruby version.
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.
$ brew update
$ brew upgrade git fzf heroku hub the_silver_searcher yarn
$ brew cleanup
$ hr pluginstall
$ gem update --system
$ rvm get head
$ brew update
$ brew upgrade git fzf heroku hub the_silver_searcher yarn
$ brew cleanup
$ hr pluginstall
$ gem update --system
$ brew update
$ brew upgrade git fzf heroku hub the_silver_searcher yarn
$ brew cleanup
$ hr pluginstall
$ gem update --system
$ brew upgrade git fzf heroku hub the_silver_searcher yarn
$ brew cleanup
$ replug
$ gem update --system
$ rvm get head
$ brew update
$ brew upgrade git fzf heroku hub the_silver_searcher yarn
$ brew cleanup
$ hr pluginstall
$ gem update --system
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.
$ brew update
$ brew upgrade git fzf heroku hub the_silver_searcher yarn
$ brew cleanup
$ hr pluginstall
$ gem update --system
$ rvm get head
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
$ brew upgrade git fzf heroku hub the_silver_searcher yarn
$ replug
$ gem update --system
$ brew upgrade git fzf heroku hub the_silver_searcher yarn
$ brew cleanup
$ hr pluginstall
$ gem update --system
$ rvm get head
$ brew upgrade git fzf heroku hub the_silver_searcher yarn
$ brew cleanup
$ hr pluginstall
$ gem update --system
$ rvm get head
I have this ritual I do to create my "standard" tmux arrangement - I should have a tmux binding for that.
A declarative, efficient, and flexible JavaScript library for building user interfaces.
๐ Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
An Open Source Machine Learning Framework for Everyone
The Web framework for perfectionists with deadlines.
A PHP framework for web artisans
Bring data to life with SVG, Canvas and HTML. ๐๐๐
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
Some thing interesting about web. New door for the world.
A server is a program made to process requests and deliver data to clients.
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
Some thing interesting about visualization, use data art
Some thing interesting about game, make everyone happy.
We are working to build community through open source technology. NB: members must have two-factor auth.
Open source projects and samples from Microsoft.
Google โค๏ธ Open Source for everyone.
Alibaba Open Source for everyone
Data-Driven Documents codes.
China tencent open source team.