-
Notifications
You must be signed in to change notification settings - Fork 44
Should highlight_outputs
be TRUE or FALSE by default?
#41
Comments
I'd vote for FALSE, personally |
I am also voting for FALSE, partly because I add the date to my YAML programmatically, and right now the highlighting is breaking the YAML parsing in |
I agree, but can you explain how it is breaking it, or provide a reprex? |
Sure, if the code below is in the yaml header
This will get css for highlighting added during knitting, and then pandoc will choke on it. I can make a reprex tomorrow if needed. |
test_doc.docx
When you knit this from a And this is what the output docx looks like: SessionInfo: R version 3.5.1 (2018-07-02) Matrix products: default locale: attached base packages: loaded via a namespace (and not attached): |
Thanks! Can you attach the docx? I have a fix on a branch to fix the |
Attached above. |
I've switched |
The
highlight_outputs
argument inredoc()
colors parts of the output document that are generated by code. The purpose of this is to signal to collaborators what parts of the document aren't super helpful to edit by hand. However, I'm not sure that I like the way that it looks - it looks odd when interacting with code highlighting and doesn't look right with images. Also, it could confuse collaborators - part of redoc's design philosophy is to minimize cognitive overhead for those editing on the Word side.Should I change the default for
highlight_outputs
to FALSE? Or is there some other approach?I note there may be some ways to lock parts of the word document from editing in the future, but only for chunk-type outputs, not inline text. It will be some time before I get to this, though, if ever.
The text was updated successfully, but these errors were encountered: