bendyworks / buffet Goto Github PK

That looks super sweet

Solarized Dark / Monokai Dark / Cyberpunk are some suggestsions

Upgrading homebrew sometimes breaks bash completition.

This may help troubleshoot:

==> Upgrading bash-completion
==> Downloading https://homebrew.bintray.com/bottles/bash-completion-1.3_1.el_capitan.bottle.tar.gz
######################################################################## 100.0%
==> Pouring bash-completion-1.3_1.el_capitan.bottle.tar.gz
==> Caveats
Add the following lines to your ~/.bash_profile:
  if [ -f $(brew --prefix)/etc/bash_completion ]; then
    . $(brew --prefix)/etc/bash_completion
  fi

Homebrew's own bash completion script has been installed to
  /usr/local/etc/bash_completion.d

Bash completion has been installed to:
  /usr/local/etc/bash_completion.d

What if we have an ~/.buffet/local_opt_out file formatted like:

[functions]
fs
prod

[aliases]
show
hide
g

I realize we'd have to wrap literally each item in some opt-out-checking code, but maybe it's worth it?

Many bendyworkers use atom as a default; buffet should definitely install some common extensions with apm

Proposed Packages (please suggest or bikeshed)

• linter
• merge-conflicts
• markdown-folder
• script
• vim mode
• vim surround
• atom pair

this would streamline the setup process for new users; there may be another story in the future about making sure packages are not already installed

https://github.com/mathiasbynens/dotfiles/blob/master/.gitconfig

When no public key has been set up / added to github, the following error occurs:

-- installing Vim plugins...
Cloning into '/home/vagrant/.vim/bundle/Vundle.vim'...
Permission denied (publickey).
fatal: Could not read from remote repository.

Please make sure you have the correct access rights
and the repository exists.
Error detected while processing /home/vagrant/.vimrc:
line   38:
E117: Unknown function: vundle#begin
Error detected while processing /home/vagrant/.vundle:

Looks like the problem is in vundle, so there may or may not be an easy fix.

add useful functions from:
https://github.com/mathiasbynens/dotfiles/blob/master/.functions

https://github.com/mathiasbynens/dotfiles/blob/master/.macos

https://help.github.com/articles/creating-a-commit-with-multiple-authors/

Maybe we should add a .railsrc to default some of the typical Rails app generation settings.

https://thoughtbot.com/upcase/decks/7/flashcards/46

To reproduce, type git branch -d [TAB] in a repo with branches.

tslack is a script for publishing tmate links to slack. it lives in /usr/local/bin. See: https://gist.github.com/kliph/2621968298cbf48923bd0056d283b195.

https://docs.travis-ci.com/user/multi-os/

add slim syntax highlighting https://github.com/slim-template/vim-slim.

After running the deploy script for the first time, whenever I open a new terminal session, I get hundreds of errors.
Many look like this:

bash: have: command not found

Some are syntax errors in specific files. It appears they're all in files in /usr/local/etc/bash_completion.d/, e.g.:

bash: /usr/local/etc/bash_completion.d/aptitude: line 32: syntax error in conditional expression: unexpected token `('

The files in that directory that are getting syntax errors seem to be symlinked to /usr/local/Cellar/bash-completion/1.3/etc/bash_completion.d/, so they may be brew related?

Nice completions are nice

Want to buy something that does this (probably a git-command):

$ git clone git://example.com/user/foo.git && cd foo

https://github.com/sferik/t

Maybe once a day check to see if the buffet repo has updates and output notice to user to update.

We already invert the status bar briefly instead of using a visual bell, so this should be doable.

Might be a good default to set https://github.blog/2019-02-24-highlights-from-git-2-21/

https://blog.scottnonnenberg.com/better-git-configuration/
https://dev.to/gonedark/tweak-your-terminal-for-git
https://twitter.com/rakyll/status/979824709398228992

When opening a terminal on Mac grep: /proc/version: No such file or directory is printed.

that doesn't ⚡ anyone.

Examples:

• Rails projects should ignore anything invendor/, log/, tmp/
• Haskell projects should ignore anything in dist/

When in a Git repo, the command line should display the Github usernames of the pair (if one is set). This will require editing the current pair script, which should be added to this repo.

I get the warning

grep: warning: GREP_OPTIONS is deprecated; please use an alias or script

I know, I know, we're a vim shop. But with people using Atom ( #43 ), perhaps we should have an emacs as well? Even some people who aren't @kliph like Org mode!

This is mine at the moment. It's had modifications from too many bendyworkers to be viable though.

Perhaps someone (such as @kliph 😉 😉 ) wants to czar this?

Appears to be coming from https://github.com/bendyworks/buffet/blob/master/dotfiles/bashrc#L88-L90 . probably an easy fix to wrap in an "If I'm a mac" check of some sort

It might be nice to have a YASnippet-style snippet system.

Consider:

• snipMate
• snippetsEmu
• neocomplcache
• UltiSnips
• xptemplate

Big list here: http://vim.wikia.com/wiki/Snippet_Plugin_Comparison

Update to use the configuration that's been working well for @spinningtopsofdoom and @kliph.

Some tools automatically modify dotfiles to get included in your path. These modifications should either be made to *.local files or upstreamed to buffet if they are common enough. It would be good if when opening a new tab/window there was a warning if buffet source is dirty.

Seeing

:~

as the prompt after installing buffet on an Ubuntu 16.04 server.

Example: homebrew installs autocompletion files for git, which is aliased in .bashrc to g. Autocompletion of git arguments succeeds when typing git in the terminal, but fails when using the alias g.

Here's one possible solution.

While working on a client project with an odd rubocop configuration (was inside a gem), having .rubocop.yml in my user directory prevented rubocop from executing.

Like Atom, only install Vim plugins if the user wants.

When working with bare Git repositories, there's a script that keeps attempting to run a command that is not successful while in a folder that contains a bare Git repo. I'm not really sure which one it is.

Here's how you can reproduce:

mkdir bears.git
cd bears.git
git init --bare

Immediately after executing git init --bare, each command attempted while in the repo will show fatal: This operation must be run in a work tree. This happens in Debian 8, though I suspect it may happen on other distributions.