Don't use this!

It was great while it lasted(?) but xonda is no longer necessary.
Starting with conda>=4.7.* there is built-in xonsh support.

To enable conda activate, run conda init xonsh and it will tack on the necessary configuration code to your xonshrc file and then conda activate and conda deactivate should work as you expect.

Please also make sure to remove any lines akin to xontrib load xonda -- loading two separate conda activate methods at once can only lead to bad things.

You can remove xonda entirely by running xpip uninstall xonda or conda unininstall xonda depending on your initial installation method.

Thanks for using xonda! I'll leave this up for any folks who haven't yet upgraded conda, but I highly recommend upgrading conda.

xonda

This is a thin wrapper around conda for use with xonsh

It provides tab completion for most features and also will tab-complete activate/select calls for environments.

Prerequisites

Xonda requires that conda is already installed and importable from xonsh (i.e., import conda works). In practice, this probably means that you need to have installed xonsh from conda (or at least within your current conda environment).

You also should have the conda bin/ directory prefixed to your $PATH.

Recent versions of conda suggest to not add the base conda bin/ directory to your path -- for now, please ignore this suggestion and do prefix it to your $PATH or xonda will not work as expected.

Installation

Just do a

pip install xonda

or

conda install xonda -c conda-forge 

or you can clone the repo and do

pip install .  

Note that xonda only works if it's installed in your base conda environment, so remember to conda activate base (in bash if necessary) first.

Configuration

To automatically load xonda at startup, put

xontrib load xonda 

in your .xonshrc

Usage

Xonda will automatically alias itself as conda, so you should not see any differences.

If xonda is installed and activated via xontrib load xonda then which conda should return the alias name "conda" only, instead of the path to the actual conda executable

Right

$ which conda
conda

Wrong (or at least, not activated)

$ which conda
/home/user/miniconda3/bin/conda

Basic commands

Everything should work the way conda always does. So just use it as you usually do.

conda install -c conda-forge xonsh 

conda remove python=2.7 

Environment activation

xonda provides TAB-completion for conda environments, so you don't have to keep double-checking. Also, no more source activate nonsense. To see a list of available environments, type

conda activate <TAB> 

To deactivate, simply type

conda deactivate 

Isn't that simpler?

If you are already within an environment and activate a separate environment, xonda will do you the favor of first deactivating the currently active environment.