I like Thoughtbot's dotfiles. https://github.com/thoughtbot/dotfiles
Bashstrap – For your OS X terminal
31–40 of 52 posts
Re: Bashstrap – For your OS X terminal
#32If you are interested in just the prompt, checkout https://github.com/twolfson/sexy-bash-prompt
Re: Bashstrap – For your OS X terminal
#33I remember spending so many happy hours customizing bash back in my early years with unix. Now I'm older and wiser, and I just use fish. http://fishshell.com I think that it should be especially appreciated by those who use OSX for its "it just works" approach. A couple of pro tips: * Instead of running chsh to change your default login shell just change the shell command for Terminal.app it iTerm. This means that sc…
Clicked on comments to say the same. When I discovered fish, I felt like "where have I been".
But there's one downside though: I got used (used as in muscle reflexes) to things like ls -l `where something` and they do not work anymore, fish is not backwards compatible with bash.
Re: Bashstrap – For your OS X terminal
#34The one thing I always add to my profile is "export COMMAND_MODE=unix2003". This will make some commands behave as you would expect them to under Linux instead of BSD.
Don't recall seeing that in my brief scan of the dotfiles.
Re: Bashstrap – For your OS X terminal
#35Earlier quoted context omitted.
Indeed, looks like Bashstrap is a fork of my dotfiles (without giving any credit, sadly). A lot of the commands, file structure, and even parts of the readme are a direct copy-paste.
It contains this description: Bootstrap for your terminal. A quick way to spruce up OSX terminal. It cuts out the fluff, adds in timesaving features, and provides a solid foundation for customizing your terminal style. Based on Mathias Bynens epic dotfiles - https://github.com/mathiasbynens/dotfiles* Or was that added after posting it here?
That was added after posting it here. https://news.ycombinator.com/item?id=6951288
Re: Bashstrap – For your OS X terminal
#36Earlier quoted context omitted.
I had the same feeling. I already know my username, and if there's a directory name before my prompt the "in" is implicit.
Do you know your username when you are using connected to a tmux over ssh that may or may not have another, very similar, server running inside of a screen?
Which is why you setup your shell (bash/zsh/fish) to check for the existence of $SSH_CLIENT. If it exists, you can assume you're connecting via SSH and add username and hostname to $PS1.
Re: Bashstrap – For your OS X terminal
#37I remember spending so many happy hours customizing bash back in my early years with unix. Now I'm older and wiser, and I just use fish. http://fishshell.com I think that it should be especially appreciated by those who use OSX for its "it just works" approach. A couple of pro tips: * Instead of running chsh to change your default login shell just change the shell command for Terminal.app it iTerm. This means that sc…
Fish is wonderful, but as someone who is novice to middling in skill (2 years), I found the fact that it had a different set of syntaxes to be difficult to work with. Instructions for random things to install I found all used bash syntax, which broke when used in fish.
I've since switched to zsh, and I am terribly happy with it. It has a lot of the nice advanced features that fish has, without breaking from bash syntax.
Re: Bashstrap – For your OS X terminal
#38This is just some fancied up bashrc. A (much) better alternative would be to install zsh with oh-my-zsh ( https://github.com/robbyrussell/oh-my-zsh ).
zsh is broken and breaks X times per year. It's annoying, really. I'm tired of wasting time configuring terminals time and again because the new version of XYZ package is broken. Anyone who does not enjoy spending huge amounts of time trouble-shooting on the terminal should use bash. It's the default in most distributions, it supports all major features a modern shell should.
Never ran into any problems with vanilla zsh on Arch, Debian, or OSX -- just pacman -Ss zsh || apt-get install zsh || brew install zsh. What kind of problems did you run into?
Re: Bashstrap – For your OS X terminal
#39I remember spending so many happy hours customizing bash back in my early years with unix. Now I'm older and wiser, and I just use fish. http://fishshell.com I think that it should be especially appreciated by those who use OSX for its "it just works" approach. A couple of pro tips: * Instead of running chsh to change your default login shell just change the shell command for Terminal.app it iTerm. This means that sc…
My tutorial for setting up fish on Mac OS X and Ubuntu: http://hackercodex.com/guide/install-fish-shell-mac-ubuntu/
I've never had any trouble using chsh to make fish the default shell. Bash scripts in crontabs still run under bash -- not sure why anyone would think otherwise. Plus, changing the shell command for iTerm/Terminal won't help with remote servers, so using chsh everywhere means you always get a consistent shell experience, no matter whether you're using your terminal locally or remotely.
Re: Bashstrap – For your OS X terminal
#40I remember spending so many happy hours customizing bash back in my early years with unix. Now I'm older and wiser, and I just use fish. http://fishshell.com I think that it should be especially appreciated by those who use OSX for its "it just works" approach. A couple of pro tips: * Instead of running chsh to change your default login shell just change the shell command for Terminal.app it iTerm. This means that sc…
You shouldn't have any issues changing your default shell via chsh. SHELL is, by default, set to /bin/sh by cron—you can also define this yourself.
http://www.gnu.org/software/mcron/manual/html_node/Crontab-f...