You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In particular, the character vector prints twice, once with no quotes and lots of space. I have posted a couple places to see if there is a quick fix, but have gotten no response as yet.
A potential workaround is to use print(myvector) instead of bare myvector when we want to show a character vector, but this might be a pain to explain, and does not matter for general use, so I would rather not do this. Hopefully a solution will be proposed somewhere.
Another possible option: use html_document for the rendering script instead of html_notebook, as this does not have the odd behavior. This will result in *.html files rather than *.nb.html, so we would have a lot of links to update. (I don't want to change the extension, even though that would be easier, as they won't be true notebook documents).
To keep the formatting the same, we can use the following block in the make-live script:
There seems to be a bug (or at least behavior unexpected to me) with Rmarkdown::render() that results in character vectors printing oddly when called on their own. You can see this at the following htmlpreview link:
https://htmlpreview.github.io/?https://github.com/AlexsLemonade/training-modules/blob/7517d4d1b1d288fe8920e337ee8f21c0d71db8fe/RNA-seq/02-gastric_cancer_tximeta.nb.html#file-names
In particular, the character vector prints twice, once with no quotes and lots of space. I have posted a couple places to see if there is a quick fix, but have gotten no response as yet.
Originally posted by @jashapiro in #441 (comment)
A potential workaround is to use
print(myvector)
instead of baremyvector
when we want to show a character vector, but this might be a pain to explain, and does not matter for general use, so I would rather not do this. Hopefully a solution will be proposed somewhere.My Stack Overflow posting
The text was updated successfully, but these errors were encountered: