Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Cannot access hidden directories on linux in xonsh #726

Closed
caedmon-kitty opened this issue Apr 10, 2023 · 1 comment
Closed

Cannot access hidden directories on linux in xonsh #726

caedmon-kitty opened this issue Apr 10, 2023 · 1 comment

Comments

@caedmon-kitty
Copy link

coconut version 2.2.0
xonsh version 0.13.4
coconut installed using pip - pip install -U coconut

Attempts to reference directories beginning with a '.' character (linux hidden directories) results in an error.
⇨ cd .local
cd: no such file or directory: .l

⇨ cp .xonshrc.now .xonshrc
cp: missing destination file operand after '.xonshrc.now'
Try 'cp --help' for more information.

xontrib unload coconut does not solve the problem.
xonsh --no-rc does not solve the problem
xontrib unload coconut does not solve the problem.
The only fix is to comment out the call to CoconutXontribLoader() in coconut/integrations.py

As a work around is it possible to not auto load coconut on xonsh startup but be able to xontrib load is if needed?

@evhub evhub added the bug label Apr 11, 2023
@evhub evhub added this to the v3.0.0 milestone Apr 11, 2023
evhub added a commit that referenced this issue Apr 11, 2023
@evhub
Copy link
Owner

evhub commented Apr 11, 2023

Fixed on coconut-develop>=3.0.0-a_dev22 (pip uninstall coconut and pip install -U coconut-develop>=3.0.0-a_dev22 to get the fix). xontrib unload coconut should also be working on coconut-develop as of #724.

As a work around is it possible to not auto load coconut on xonsh startup but be able to xontrib load is if needed?

This is how it used to work, but for some reason on the newest major version of xonsh doing it that way doesn't seem to work anymore and I'm not sure why. Feel free to open another issue for this.

@evhub evhub closed this as completed Apr 11, 2023
@evhub evhub added the resolved label Apr 16, 2023
@evhub evhub mentioned this issue May 1, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants