-
-
Notifications
You must be signed in to change notification settings - Fork 7
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
Directions / Assignment Chunks #6
Comments
I think this is wanting to add another flag to processing? I'm not sure we can easily embed code chunks in directions...
Readability wise, this doesn't work out nicely. |
I'm not sure what that example is showing. I don't see the need to have one chunk inside of another. |
The starting issue is a bit sparse. Did you mean something along the lines of:
going to:
e.g. there is no discrimination between tag placement? |
Written in lab00-main.Rmd:
Becomes in lab00-assign.Rmd:
|
So, we can use this to determine the asis chunk: asis.*?,.*?directions[[:space:]]?=[[:space:]]?[tT]?[rR]?[uU]?[eE]? And we can force remove in the ,?[[:space:]]?directions[[:space:]]?=[[:space:]]?[tT]?[rR]?[uU]?[eE]? |
As of now, can I include R code only in *-assign.Rmd but not in *-sol.Rmd? |
If a code chunk is marked by:
These two keywords are hard-wired at the moment: |
@coatless Thanks, but sorry I don't get it here. What I want to do is
which only returns the plain text "1+1". I want it to generate R code only in |
@inmybrain unfortunately, no. The |
@coatless Thanks for the clarification. Is there any possibility to include such an option? |
@inmybrain not until the weekend. My mind is on a paper deadline. |
@coatless Oh I didn't mean to rush you at all. Please take your time and consider including the option when you have time. Wish you finish your paper by the due date. |
Currently cannot be used for both
r
andasis
engines.The text was updated successfully, but these errors were encountered: