Activate vox before other xontribs
When vox was activated after apipenv, then opening a new shell in a folder with a Pipfile resulted in calls to vox before the xontrib had been loaded. This resulted in improper error messages about missing the vox program and meant the Pipenv was not auto-loading in that folder. By moving activation of vox before these other xontribs, those xontribs can make use of vox internally
This commit is contained in:
@@ -128,11 +128,6 @@ aliases['cleanup'] = _cleanup
|
||||
#
|
||||
###
|
||||
|
||||
# Does virtualenv support
|
||||
xontrib load vox
|
||||
# Faster coreutils
|
||||
xontrib load coreutils
|
||||
|
||||
# Allows identifying JSON as if it was Python by adding some new builtins to the language
|
||||
import builtins
|
||||
builtins.true = True
|
||||
|
||||
@@ -11,6 +11,11 @@ from sys import platform
|
||||
# set -x == trace on; $XONSH_TRACE_SUBPROC = True
|
||||
# $? == _.rtn
|
||||
|
||||
|
||||
# Does virtualenv support
|
||||
xontrib load vox
|
||||
# Faster coreutils
|
||||
xontrib load coreutils
|
||||
xontrib load direnv
|
||||
xontrib load coreutils
|
||||
xontrib load xonsh-apipenv
|
||||
|
||||
Reference in New Issue
Block a user