-
Notifications
You must be signed in to change notification settings - Fork 78
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
(Pandoc?) warning about nonempty title element #156
Comments
I do not immediately know what's going on here. However it looks like the rmarkdown fix happened after the last CRAN release. If you install rmarkdown from GitHub, does that resolve it? |
Ok. Thanks. I also tried the devel version of rmarkdown and it did not help. |
Is this specific to reprex or does it happen whenever you render |
It seems specific to reprex. |
No in fact it also happens when I render to |
Maybe the issue should be moved to |
So it's the Can you also test with both |
Yes, for |
For |
Same for |
If I set |
On a related note, with |
Yeah I know that fix to the SO venue problem is not really done. #143 is my reminder. Will you tell me more about your system over there? Because I can't replicate the problem but sounds like you can! |
Sure. Maybe this helps? I wonder whether #133 is related to this issue (pandoc warning). sessioninfo::session_info(c("reprex"))
#> ─ Session info ──────────────────────────────────────────────────────────
#> setting value
#> version R version 3.4.3 (2017-11-30)
#> os macOS Sierra 10.12.1
#> system x86_64, darwin15.6.0
#> ui X11
#> language (EN)
#> collate en_US.UTF-8
#> tz Europe/Zurich
#> date 2018-01-12
#>
#> ─ Packages ──────────────────────────────────────────────────────────────
#> package * version date source
#> assertthat 0.2.0 2017-04-11 CRAN (R 3.4.0)
#> backports 1.1.2 2017-12-13 CRAN (R 3.4.3)
#> base64enc 0.1-3 2015-07-28 CRAN (R 3.4.0)
#> callr 1.0.0.9000 2018-01-12 Github (r-lib/callr@550fa6b)
#> clipr 0.4.0 2017-11-03 CRAN (R 3.4.2)
#> crayon 1.3.4 2017-09-16 CRAN (R 3.4.1)
#> debugme 1.1.0 2017-10-22 CRAN (R 3.4.2)
#> digest 0.6.13 2017-12-14 CRAN (R 3.4.3)
#> evaluate 0.10.1 2017-06-24 CRAN (R 3.4.1)
#> highr 0.6 2016-05-09 CRAN (R 3.4.0)
#> htmltools 0.3.6 2017-04-28 CRAN (R 3.4.0)
#> jsonlite 1.5 2017-06-01 CRAN (R 3.4.0)
#> knitr 1.18 2017-12-27 CRAN (R 3.4.3)
#> magrittr 1.5 2014-11-22 CRAN (R 3.4.0)
#> markdown 0.8 2017-04-20 CRAN (R 3.4.0)
#> mime 0.5 2016-07-07 CRAN (R 3.4.0)
#> processx 2.0.0.1 2017-07-30 CRAN (R 3.4.1)
#> R6 2.2.2 2017-06-17 CRAN (R 3.4.0)
#> Rcpp 0.12.14 2017-11-23 CRAN (R 3.4.3)
#> reprex 0.1.1.9000 2018-01-12 Github (tidyverse/reprex@9b07b0e)
#> rlang 0.1.6 2017-12-21 CRAN (R 3.4.3)
#> rmarkdown 1.8 2017-11-17 CRAN (R 3.4.2)
#> rprojroot 1.3-2 2018-01-03 CRAN (R 3.4.3)
#> stringi 1.1.6 2017-11-17 CRAN (R 3.4.2)
#> stringr 1.2.0 2017-02-18 CRAN (R 3.4.0)
#> whisker 0.3-2 2013-04-28 CRAN (R 3.4.0)
#> withr 2.1.1 2017-12-19 CRAN (R 3.4.3)
#> yaml 2.1.16 2017-12-12 CRAN (R 3.4.3) Created on 2018-01-12 by the reprex package (v0.1.1.9000). |
I'm getting a similar effect on 0.1.1.9000 after updating my other packages (not sure which one caused it, sorry). |
@lorenzwalthert @alistaire47 Please let me know if, once you update, this is NOT fixed. I was able to reproduce it by upgrading Pandoc myself and this suppresses the warning for me locally and on AppVeyor. |
Yep, the update (plus an R restart) fixes it! |
Yup, now it works without warnings. Thanks @jennybc 😊 |
I get a strange (probably pandoc related) warning with the dev and CRAN version of
reprex
.Created on 2018-01-07 by the reprex package (v0.1.1.9000).
I updated pandoc from 2.0.4 to 2.0.6 but it did not help. There seem to be similar warnings in other contexts (rstudio/rmarkdown#1200 and remotely related ramnathv/htmlwidgets#289). From the former issue, I thought I might be able to resolve the problem by using the development version of
rmarkdown
, which also did not help. Any ideas what's wrong here?Session info
The text was updated successfully, but these errors were encountered: