* This option adds a lot of noise to test output
* Extra noise often means scrolling
* The profile includes red, which makes me think tests fail
* Profiling isn't useful when running one or a few tests
* I'm usually not in the mindset of profile tests, so I ignore it
* "to the $HISTFILE incrementally (as soon as they are entered), rather than
waiting until the shell exits"
* replace any duplicate in the history, not just the previous duplicate: allows
for a cleaner history
* `.zhistory` is more idiomatic than `.zsh_history`
Often mistyping things like `gi tst` causes `gi` alias to trigger the install of
the `tst` gem. This is quite annoying and too close to `git` command which we
run much more often than `gem install`. With bundler we should almost never run
`gem install`.
Default setting is `.,w,b,u,t,i`:
* `.`: scan the current buffer ('wrapscan' is ignored)
* `w`: scan buffers from other windows
* `b`: scan other loaded buffers that are in the buffer list
* `u`: scan the unloaded buffers that are in the buffer list
* `t`: tag completion
* `i`: scan current and included files
The default setting is more likely to find a useful match, and modern
machines can search many open and unloaded buffers without pausing.
This frequently catches false positives for aliases, particularly for
subcommands. It also takes just as long to look at the autocorrect
prompt and select "y" as it does to just retype the command yourself.
While trying out the approach outlined in Croaky's latest [blog post], I
realized that running `rcup` would not also pull updates from my local
extensions. If you clone your extensions as `dotfiles-local`, this
update will pick them up.
Non-existent directories are ignored by rcup, so it won't cause issues
if you don't have `dotfiles-local`.
[blog post]: http://robots.thoughtbot.com/manage-team-and-personal-dotfiles-together-with-rcm
* easier when everything is just one file
* most (if not all) interactive shells are login shells and we likely want those
settings for interactive shells
* remove duplicates with zlogin
* order by functions first, then bindings, then exports
* lowercase `setopt` arguments for consistency with `setopt` output
Previously, the after-up hook would only do a `:BundleInstall` when
installing vundle for the first time. This is inconsistent with the
pre-rcm process, and also less convenient.
The rcm suite is designed to replace the `./install.sh` script found in
this and many other dotfiles repos across GitHub. By using rcm users can
combine multiple dotfiles repos, tag dotfiles, have host-specific
dotfiles, and other powerful features.
This commit removes `install.sh`, updates the README, adds a post-up
hook that vundles the vim bundles, and adds a `rcrc` configuration that
ignores `README.md` and `LICENSE` and sets the dotfiles directory to
just `dotfiles`.
Using the `commit.template` setting, read in a commit message template
for each commit. This template is commented out so the commit message
author doesn't need to delete it.
The template serves as a reminder on how to write a better commit
message. The bullets are taken from Caleb's blog post[1]. There is no
_problem_ per se -- we are writing good messages these days -- but it's
handy to be reminded of things to think about. For example, people often
forget to note whether there are any side effects.
This message does not show on `git commit --amend`, only normal `git
commit`.
[1] http://bit.ly/13HWyiy
It is a common practice to store environment variables in a .env file in
development. This file is read by tools such as foreman and dotenv. This
file can contain sensitive information such as secret keys and should
always be excluded from version control
* Automatically :write before commands such as `:next` or `:!`
* Saves keystrokes by eliminating writes before running tests, etc
* See `:help 'autowrite'` for more information
It gets very annoying to manually force CtrlP to re-index every time I
add a new file. Since ag is so fast, we can turn off caching when it
powers CtrlP without any noticeable impact on search speed.
Newer versions of vim (such as 7.3.923) syntax highlight Rackup and JSON
files correctly. In the interest of keeping the dotfiles slim and our
machines up-to-date, I think the solution is to remove these from
dotfiles and install a newer version of vim in thoughtbot/laptop:
https://github.com/thoughtbot/laptop/pull/118
* Syntax highlight `Appraisals` as Ruby. Used especially for our open
source libraries.
* Syntax highlight rackup (`config.ru`) files as Ruby. Used in all our
Ruby web apps. Rails apps are rarely touched but some of the Sinatra
and Middleman apps are occasionally edited.
* Syntax highlight JSON files as JavaScript. Used in our Trail Map.
