eval `rbenvWrap init -`Source your .tcshrc (or logout and login again) and you're done (assuming you've also installed rbenv). You don't need to worry about the wrapper anymore, all of your rbenv commands will work just like they do on bash. Example:
tcsh% echo $RBENV_VERSION RBENV_VERSION: Undefined variable tcsh% rbenv versions * system (set by /home/dave/.rbenv/version) 2.1.2 tcsh% ruby -v ruby 1.9.3p484 (2013-11-22 revision 43786) [x86_64-linux] tcsh% rbenv shell 2.1.2 tcsh% rbenv versions system * 2.1.2 (set by RBENV_VERSION environment variable) tcsh% echo $RBENV_VERSION 2.1.2
tcsh% rbenv sh<tab> shell shims tcsh% rbenv shell <tab> 2.1.2 system --unset tcsh% rbenv shell -<tab> tcsh% rbenv shell --unset
eval `rbenvWrap init - csh`You can see how long it takes in both cases by timing the commands:
% time rbenvWrap init - > /dev/null % time rbenvWrap init - csh > /dev/nullFor serious power-users you could also take the full complete command that 'rbenvWrap init -' generates and put it in your .tcshrc and then not generate it each time, but this also means that future changes to rbenv completion will not get updated on your system.
Back to Solutions.