-
-
Notifications
You must be signed in to change notification settings - Fork 878
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
Feature request: child.path #141
Comments
Currently paths of child documents are assumed to be relative to the path of parent documents, so we probably do not need an extra argument to set the path. For example, <<set-child, child=a.Rnw;b/c.Rnw>>=
@ This will include two child documents |
The point would be that you would not have to type
and only correct it one place in my main Rnw file. |
Then you will have to write |
You can set |
I don't manage to use this option.
Then this does not work:
But this obviously works:
|
I see two problems:
The first one is easy to fix: The second one is the dot here: |
A solution thanks to http://stackoverflow.com/a/36728257/1100107:
|
@yihui , |
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. |
When doing larger R project I might have a project structure like this:
I can put pictures in figures with
fig.path
and cache is sorted intocache.dir
. It would be natural to also have achild.dir
where knitr automatically looks for children.The text was updated successfully, but these errors were encountered: