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

Dots in fig.path and cache.path should be allowed #346

Closed
achetverikov opened this issue Jul 18, 2012 · 3 comments
Closed

Dots in fig.path and cache.path should be allowed #346

achetverikov opened this issue Jul 18, 2012 · 3 comments
Labels
bug Bugs
Milestone

Comments

@achetverikov
Copy link

Currently, dots in paths are replaced with underscore, which makes relative paths impossible. It is quite inconvenient as one cannot keep cache outside of the source folders. I usually make backup copies of source, uploading everything in a source folder to server, but I don't want to backup the cache. The absolute paths are possible option, but I don't see why relative paths should be prohibited.

@ramnathv
Copy link
Contributor

I believe this change is the one responsible. Should be relatively straightforward to fix.

@yihui
Copy link
Owner

yihui commented Jul 18, 2012

No, I'm all for relative paths, and I really want to prohibit absolute paths instead.

This is a bug introduced by #321. Sorry I did not take paths like ../ into account when fixing that problem. But I do not think cache.path should be affected.

yihui added a commit that referenced this issue Jul 18, 2012
@yihui yihui closed this as completed in 8c31d20 Jul 18, 2012
yihui added a commit that referenced this issue Jul 18, 2012
yihui added a commit that referenced this issue Jul 18, 2012
@github-actions
Copy link

This old thread has been automatically locked. If you think you have found something related to this, please open a new issue by following the issue guide (https://yihui.org/issue/), and link to this old issue if necessary.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Nov 10, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
bug Bugs
Projects
None yet
Development

No branches or pull requests

3 participants