bash-it / bash-it Goto Github PK

If you have rvm enabled, it complains about not being the first thing in $PATH.
When you activate a virtualenv, this places the venv's path first, and rvm begins to complain.

I don't know what "the right thing" would be to do here.

it's not clear how to use your own rgb color values for the themes/prompt. could someone please point me in the right direction? thanks

Hi,

since i use bash-it i wonder why all these specific things are placed in bash_profile
i'm talking about:

     export JEKYLL_LOCAL_ROOT="$HOME/Sites/jekyllsite"
     export JEKYLL_REMOTE_ROOT="user@server:/path/to/jekyll/root"
     [...]

and other nginx git_host or rvm stuff. I think you know what i mean. Wouldn't it be better (and maybe more user friendly) if such things are separately placed in lib/jekyll.bash oder in plugins/jekyll.plugin.bash ?

When a new user downloads bash-it, he will see plugins or lib files and remove the ones he doesn't need. thats all. otherwise he got to edit .bash_profile and things as well. this were at least my first steps with bash-it

i think .bash_profile should contain only the basic and general things which are required to use the framework.

just my 2 cents ;)

I want to add completion for NPM and I have a script that will do it. However, there's a dependency problem. I'm using the nvm plugin to load Node.js and NPM, and my completion script needs NPM to be loaded before it runs. bash-it currently loads aliases, then completion, then plugins, like so:

for file_type in "aliases" "completion" "plugins"
do
  _load_bash_it_files $file_type
done

Is there any particular reason this is done? If plugins were loaded first, then aliases and completion scripts could depend on them. As far as I can tell, plugins get no benefit from having aliases and completion loaded first.

The install script attempts to backup ~/.bash_profile when it does not exist.

$ ~/.bash_it/install.sh 
cp: /Users/sgerrand/.bash_profile: No such file or directory
Your original .bash_profile has been backed up to .bash_profile.bak

Adding a test for the existence of that file (test -f ~/.bash_profile) or, even better, that the user can write to it (test -w ~/.bash_profile) would fix this issue.

on SCM prompt for Mercurial 'hg summary' will report branch heads, the grep for 'branch' passes two matches to awk, adding extra unwanted text to $SCM_BRANCH

issue fixed, pull request incoming.

Gem completion script makes each new terminal window take ages to load. Just deleting the symlink from enabled completions folder makes it load reasonable well.

sh install.sh

cp: cannot stat //.bash_profile': No such file or directory Your original .bash_profile has been backed up to .bash_profile.bak cp: cannot stat//.bash_it/template/bash_profile.template.bash': No such file or directory
Copied the template .bash_profile into ~/.bash_profile, edit this file to customize bash-it
Do you use Jekyll? (If you don't know what Jekyll is, answer 'n') [Y/N] n
Would you like to enable all, some, or no aliases? Some of these may make bash slower to start up (especially completion). (all/some/none) all
mkdir: cannot create directory //.bash_it/aliases/enabled': No such file or directory ln: creating symbolic link//.bash_it/aliases/enabled': No such file or directory
Would you like to enable all, some, or no plugins? Some of these may make bash slower to start up (especially completion). (all/some/none) ^C

^^^ At this point I stopped. The thing is, I am the superuser, but for some reason I am logged in with sh and not bash, and my HOME directory at /root is not recognized.

As a consequence, some assumptions do not work.

The one that I think is the biggest problem is this one here:

mkdir: cannot create directory `//.bash_it/aliases/enabled': No such file or directory

It should first create the directory .bash_it and then create the directory aliases.

I tried to find an irc channel or something so I didn't have to file an issue, but couldn't find any.
Basically if I type git, it completes flow, but after the git flow nothing gets completed.

No clue what's happening and no clue how to fix it :/

Thanks for this great project!

bash: /home/micha/.bash_it/bash_it.sh: No such file or directory

Hey, just pulled your recent changes, that created the enable-plugin command, which doesn't seem to be working right.
Every plugin i try to enable with it seems to get an incorrect symlink. "?[0m" gets appended to the name of the file in the enabled directory.
Plugins i've tried with it are git, dirs, fasd, tmux, ssh

in gnome-terminal, when enabling any of the themes, the prompt is wrapped back to the start of the line

Forgive me if this has been raised and decided, but the issue searchbox did not reveal such...

I'm wondering why this toolkit focuses on wedging into .bash_profile when .bashrc seems to be generally accepted as the starting point for interactive bash sessions?

I follow what I'd gathered to be a generally accepted practice of a trivial bash_profile which exists primarily to invoke .bashrc, whose only other entries are to configure items I'd use from cron or some remote execution tool.

(in fact I carry this a bit further, having a separate .bashrc.interactive or .bashrc.local for the truly local interactive stuff).

I'm busily hacking on my own local branch to refactor for the above, but want to step back and think about how I can give back.

(background: I spend hours logged in as the daemon user for a particular application for administration. I'm hoping this toolkit can help me standardize those admin environments but my prime directive is "First, do no harm" to the app's auto-customized shell environment. I'm leaning toward an installation that requires manual sourcing for that particular environment, but elsewhere, a cleaner merge into existing startup files.)

There's a common use case for displaying a colorized character as an indication if the previous command exited cleanly or not.

I can't figure out how to re-invoke prompt change after every command, so that it would change based on previous actions.

I've recently switched over from bash to zsh and therefore won't be able to do much on this project, I just wanted to let everyone know this (I'm not sure of any other way than adding an issue, sorry).

Easy as 123(4)

1. Get http://svn.apache.org/repos/asf/subversion/trunk/tools/client-side/bash_completion
2. Rename bash_completion to svn.completion.bash
3. Move svn.completion.bash to ~/.bash_it/completion/available/svn.completion.bash
4. $ bash-it enable completion svn
   Done.

Should I fork bash-it and send pull request?

P.S.
http://www.apache.org/licenses/LICENSE-2.0

After installing bash-it, I had to restart the terminal window/tab for bash-it to become active. In my opinion, it should be mentioned in the installation instructions in the README.

Terminal application: iTerm
OS: Mac OS X 10.7.4

After a new install instead of each plugin file being linked I get a "*" symlink:

± |master ✓| → ls -lta ~/.bash_it/plugins/enabled/
total 8
lrwxr-xr-x  1 msthornton  staff   50 May  7 13:06 * -> /Users/msthornton/.bash_it/plugins/[^_]available/*

The default alias "ls=ls --color=always" breaks pipelines including the ls command.

This should be set to

ls="ls --color=auto"

Experienced this issue: http://stackoverflow.com/questions/19006770/git-rpc-failed-result-22-http-code-400

resolution of moving to https worked for me

Hello,

First, let me tell that I find this project awesome, so thank you for that.
Second, this is not a bug, this is feedback, a suggestion, a question.
Such things don't play well at all with bugtrackers that were designed to... well track bugs
But since few developers know very useful tools like https://www.uservoice.com/ , I post my feedback here.

A little thing bugs me with bash-it
It follows the bad very old idea to hide config files right under $HOME
This was fine when you had only to configure .bashrc and .emacs, but this got out of control since a long time.

That's why the $XDG_CONFIG_HOME variable was invented in the first place
http://standards.freedesktop.org/basedir-spec/basedir-spec-latest.html

I happen to use macosx, but I have precisely the same problem.
All my pet projects, most forked from github, are stored in $HOME/github
bash-it is an exception here and I found it weird.
But ok I will do an exception.
So I opened GitHub.app, will do "File -> Add local directory"
Here the standard MacosX's Open Dialog pop up
I browse to $HOME
Same problem : hidden files are not shown (because it doesn't scale well)

So I had to browse the web to find a work-around, a shortkey that displays hidden files, get the job done.

With the dialog box as the front-most window (you can click once in the dialog box to make sure it’s in front), press the command, shift, and period keys at the same time.

Ok, but now I'm pretty sure that I will forget it soon, and that most people don't know it either.

Suggestion:

improve the documentation so that people put their copy of bash-it in $XDG_CONFIG_HOME, $HOME by default

Can we add a git global ignore?

# File: git-global-ignore

# Packages #
############
# it's better to unpack these files and commit the raw source
# git has its own built in compression methods
*.7z
*.dmg
*.gz
*.iso
*.jar
*.rar
*.tar
*.zip

# Logs and databases #
######################
*.log
*.sql
*.sqlite

# OS generated files #
######################
.DS_Store?
ehthumbs.db
Icon?
Thumbs.db

# from sublime text editor
package.sublime-workspace

In .gitconfig (under ~/)

[core]
  excludesfile = /path/to/git-global-ignore

Just asking, there is no un-installer, so How do I move back?

The the enabled directory exists and is empty, you get an error like this:

bash: /home/jpschewe/.bash_it/plugins/enabled/*.bash: No such file or directory

It would be really nice to include tmux completion in the available completion scripts. There is a public domain version available at http://tmux.svn.sourceforge.net/viewvc/tmux/trunk/examples/bash_completion_tmux.sh?revision=2697&content-type=text%2Fplain

This line https://github.com/revans/bash-it/blob/master/plugins/available/xterm.plugins.bash#L3

is not working in OSX an is causing OSX terminal to output an error with each command, seems that it's not understanding \e]0;

Thanks

The following code is incorrectly aliasing shuf to gshuf:

which gshuf &> /dev/null
if [ $? -eq 1 ]
then
    alias shuf=gshuf
fi

This will only ever alias shuf to gshuf if gshuf does not exist in the PATH, which is wrong (I'm guessing a typo or something). Here's the correct code:

which gshuf &> /dev/null
if [ $? -eq 0 ]
then
    alias shuf=gshuf
fi

Hope that helps :)

Currently git status is aliased to gs. However, gs is the Ghostscript binary, which may be common enough that's it's worth removing the the alias.

https://github.com/revans/bash-it/blob/master/aliases/available/git.aliases.bash#L10

One issue, I had found with non-english locale: all commands bash-it do not work. Simple patch:

helpers.bash:83
[ -n "$(LANG=C type -a $1 2>/dev/null | grep 'is a function')" ]

loading autotest/cucumber_rails_rspec2
Autotest style autotest/cucumber_rails_rspec2 doesn't seem to exist. Aborting.

For reasons beyond my own bash-it declares some extra environment variables, one of which was AUTOFEATURE=true;

autotest will die horribly with **AUTOFEATURE=true* when **iconv* is not listed in your dependencies (Gemfile), cucumber depends on iconv for json.

What still worries me is why bash it was declaring all those environment vars

sigh closable

The wiki links to the project page, this is confusing. Also (this should be a separate issue, but while we're at it) it'd be nice for the wiki to have screenshots like oh-my-zsh's wiki!

sorry to be a doomsayer.

for starters, this file is full of function definitions that work based on pure luck alone
https://github.com/revans/bash-it/blob/master/lib/preexec.bash
defining a function with "function name ()" is broken, unportable, and not guaranteed to work across bash versions. see http://mywiki.wooledge.org/BashPitfalls#pf25

here is an example of inconsistency in function definitions https://github.com/revans/bash-it/blob/master/lib/history.bash

and this file has mixed definitions https://github.com/revans/bash-it/blob/master/lib/helpers.bash

you're writing bash-specific code; use the tools to your advantage. single-bracket test ( [ ... ] ) is fully discouraged when writing scripts with a bash shebang. use double-bracket test ( [[ ... ]] ) instead -- ESPECIALLY since you don't properly quote your substitutions and expansions ever. expansions within [[ .. ]] are not subject to word-splitting which saves you the headache of writing good code in some situations. refer to http://mywiki.wooledge.org/tests and http://mywiki.wooledge.org/WordSplitting for more information.

https://github.com/revans/bash-it/blob/master/lib/composure.sh
in this file, you defined transcribe() twice. redundant. you also define a function to echo some keywords, which you later re-use to compose other functions to execute `:' through eval. now you can get away with the misappropriated use of eval here thanks to your finite & known input but you really shouldn't be doing this at all. first, composure_keywords() shouldn't be a function. it should be an array, expanded with ''for keyword in "${composure_keywords[@]}"; do ...; done''

also i'm pretty positive you meant "composition" rather than "composure" unless erichs thought this play on words was unbelievably clever.

https://github.com/revans/bash-it/blob/master/lib/composure.sh#L18 see ''help typeset.'' (unless you're super concerned about your scripts being portable to ksh...wot)

https://github.com/revans/bash-it/blob/master/lib/composure.sh#L57
shopt -s nocaseglob case $input in (y[es]*) ...;; (n[o]) ... ;; esac

https://github.com/revans/bash-it/blob/master/lib/composure.sh#L143
greybot │ basename(1) can strip the directory and extension from a path (a/b/c.d -> c.d or c). A parameter expansion can do it cleaner and much faster: "${path##/}", "${path%.}"
** you should probably replace every occurence of the triply expensive pipe to sed with a parameter expansion.

greybot │ Use pgrep instead of ps to get PIDs. It saves you from having to parse output that wasn't meant to be parsed. However, finding a process by its name is unsafe. Please look at http://mywiki.wooledge.org/ProcessManagement
****** please note the comment "it saves you from having to parse output ----that wasn't meant to be parsed----"

uhmmmm, wtf is this https://github.com/revans/bash-it/blob/master/bash_it.sh#L13
the backticks create an expensive subshell in the first place. and in that subshell, you launch a THIRD bash instance just to ''echo $BASH'' and this whole construct is 100% equivalent to "var=$BASH" exactly like you have in the line before. even worse though, is that BASH is set by default already and you've just been wasting these cpu cycles for god knows how long. see ''declare -p BASH'' in a shell that isn't running bash-it.

okay, i will just leave it here. if you fix all of these problems, you'd have solved about 60% of the issues that will crop up over time due to the horrible syntactic constructs employed herein.

Apparently, the new color framework introduced in 1da06a4 and 879d540 end up making all the normal text entered into and displayed by the shell appear "bold" (eg. apparently using the wrong escape code, or simply not resetting colors).

Things are fine in previous revisions. (I tested 54ffcc0.)

fasd (e.g. running z Documents) fails on my OS X machine with the following error:

-bash: cd: ,002    /Users/foo/Documents/Projects/FooBarDocuments: No such file or directory
1,16226    /Users/foo/Documents/Projects/Foo Dir
2,09207    /Users/foo/Documents/Projects/..
3,645      /Users/foo/Documents/Projects/foo_framework/02_Requirements
23,2452    /Users/foo/Documents/Projects/barDocuments/01_Documentation
28,9264    /Users/foo/Documents/Projects
42,8244    /Users/foo/Documents/Projects/foo_framework
368,002    /Users/foo/Documents/Projects/FooBarDocuments

I think this is due to my account using a German locale, where the comma is used as the decimal separator.

I've seen in the fasd.plugin.bash file that AWK is used for doing the calculations, and it looks like AWK is using the comma in this case. If I execute the following command, I end up with a result of 1,5:

awk "BEGIN{ print 3/2 }"

The code in fasd uses this to populate the "database", but while parsing, it looks for a point (.) as the decimal separator and thus fails.

@erichs Is that something you can look into?

Let me know if you need more info.

I think it would be useful to be able to enable plugins / aliases / completion etc. by just creating a symbolic link in the proper directory.

That way, we won't need more work to update it after a git pull.

getting this on every time I hit return

\e]0;[email protected] /Volumes/WS/

Here is the error I get when loading bash-it for the first time:

bash: /home/jryan/.bash_it/bash_it.sh: No such file or directory

I tried chasing it down and the only thing I can find that seems out of place is a broken symlink in the bash-it folder .bash_it

Which it seems from some of the code that file should be in my home directory helping with the configuration. I'm not a bash guru far fro it actually but I can't figure this out. Maybe someone else is experiencing this as well.

Thanks

For some reason, whenever I run ANY command, I get this:

/home/neer/.z.tmp' ->/home/neer/.z'

Without fail, no matter if I run a script, a command, or a perl-one-liner, I always get this message.
Does anyone know how to fix it?

Issue occurs when you go into folder that contains .rvmrc file (rvm script file). It should load the script file first but it don't

One of the last changes broke the bash history.
The characters start flipping around and it's hard to read or edit a recently executed command.

What's the best way to cleanly disable bash-it ?

When I run the install script it runs through four options then exits. It doesn't seem to of put itself on my PATH at all though and when I run the bash-it.sh script directly i get an error. Here's what I did and the output I got:

It looks like it is trying to use some global files so I ran the install script again as admin to see if it would install correctly but no diff.

The git part of the terminal info goes away when inside a git repo that is a submodule.

If i enable bash it and make my .bashrc a link to .bash_profile whenever I try to do an SCP transfer instead of transferring the file it echos out the last directory used.

@mrman208 I'm interested to get your input on how you use bash-it with multiple Jekyll sites. From what I can tell, the aliases and plugins are designed to work with one site, that points to $JEKYLL_LOCAL_ROOT.

Personally, I use Jekyll for several projects and I'm curious if others would be interested in modifying this.

Hi, after upgrading to Mountain Lion I've noticed that opening Terminal became considerably slower. Is there anything I can do to make it more snappier again?

README.md lists the help screens available, but 'bash-it help completions' throws the following error:

oops! completions is not a valid option!

even tried 'bash-it help completion general' to show completions for the 'general' completion, but throws same error.

When I'm typing "myip", I'm getting (I've replaced the actual ip address with 123.123.123.123):

Your public IP is: [\e[1;32m] 123.123.123.123 [\e[00m]

instead of the colored ip.

Whenever my prompt loads it's duplicating the display of the last command like:

Last login: Mon Mar  5 08:50:56 on ttys003
\e]0;[email protected] ~ 
farneman[~]
≠ » cd .bash_it
\e]0;cd .bash_it {~} ([email protected])\e]0;[email protected] ~/.bash_it 

The "farneman[~] ≠ »" part is my prompt.

I'm using iTerm2 on an iMac running OS X 10.6. The problem occurs no matter what theme being used. I've tried install bash_it with none of the plugins, completion or aliases installed and the issue persists. I'm using the exact same setup on an older G5 PowerMac running OS X 10.5 and the problem doesn't occur on that machine.

Any idea what may be causing this?