![]() ![]() And, when the offending code is on its own, it behaves. I'm sorry - I realize there isn't a lot to go on here, but this is a chunk in the middle of several thousand lines of code - all of which run fine. The function in the offending chunk involves generating a table with gt. ![]() The preceding chunks (Chunk1 - ChunkN-1) all run exactly as expected - no weird behaviors. ![]() If I put the offending chunk in an Rmarkdown file by itself, it behaves as it should, and does not display T1 and T2. This is true even if I use results = 'hide'. Then I have a chunk which is basically of the form: Īccording to the structure, nothing should get displayed, but when I knit the Rmarkdown file, both T1 and T2 appear. Here is the skeleton of the problem Chunk 1 Weave.I have a weird situation - and I apologize in advance, but this issue doesn't lend itself to a reproducible example. You can also set or change the default chunk options for a document either before weave using the set_chunk_defaults function. to set the default out_width of all figures you can use:. You can set the default chunk options (and weave arguments) for a document using weave_options key in YAML Header Configuration.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |