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

Env variables doesn't expand to paths in sub process mode. #338

Closed
melund opened this issue Jul 31, 2015 · 5 comments
Closed

Env variables doesn't expand to paths in sub process mode. #338

melund opened this issue Jul 31, 2015 · 5 comments

Comments

@melund
Copy link
Member

melund commented Jul 31, 2015

Environment variables can't be used to create a path in subprocess mode:

For example on windows: cd $USERPROFILE works fine.

But cd $USERPROFILE/Documents does not. Pressing tab in the shell causes the autocompleter to expand the path.

So not a big issue in an interactive shell. But typing something like that in a file or having it in an alias doesn't work.

@michaelaye initially reported this:
#319 (comment)

klay6683@MacL2938 ~ $ aliases['cdsrc']
['cd', '$HOME/Dropbox/src']
klay6683@MacL2938 ~ $ cdsrc
cd: no such file or directory: $HOME/Dropbox/src
@scopatz
Copy link
Member

scopatz commented Jul 31, 2015

I think that we need to start having tests for some of these aliases too.

@scopatz
Copy link
Member

scopatz commented Jul 31, 2015

I remember this used to work.

@scopatz scopatz added this to the v0.2 milestone Aug 3, 2015
@scopatz scopatz modified the milestones: v0.2, v0.3 Sep 12, 2015
adqm added a commit to adqm/xonsh that referenced this issue Dec 19, 2015
adqm added a commit to adqm/xonsh that referenced this issue Dec 24, 2015
@melund
Copy link
Member Author

melund commented Apr 20, 2016

This has been fixed

@melund melund closed this as completed Apr 20, 2016
@seanfarley
Copy link
Contributor

With the latest xonsh (0.4.5) this is broken again.

@scopatz
Copy link
Member

scopatz commented Aug 23, 2016

I think it does if you put them in quotes for some reason. Of course, it should always...

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

3 participants