This is not an issue, but a recommendation.

I would like to suggest that in the docs available in the Rmarkdown book you include two examples in chapter 15 (parameterized reports):

• passing parameters as raw markdown text for the parameterized reports.
• setting the title using a parameter

This information is available in other parts of the book,

Many times when I search for some R plotly documentation, I come across a page with a broken shiny app, which essentially renders that page useless. I usually ignored it, but I realize now that it would have been much more productive to make note and report it! So I'll start now :)

The app here doesn't exist: https://plot.ly/r/shinyapp-linked-click/

There is some incompatible linking between our docs and the dplyr docs so that either it works with the current dplyr or the v1 version. I unlinked to work in both, but once v1 is released we will eventually want to add the links back and just have them not work if people have not updated the tidyverse.

Currently, it seems like all rticles outputs rest upon rmarkdown::pdf_document() format.

However, would there be any way we could replace it with bookdown::pdf_document2() so that users can cross-reference sections? Furthermore, given that bookdown::pdf_document2() is inclusive of the basic rmarkdown::pdf_document(), what would be any expected conflict other than benefits?

I was atte

This should reduce the number of duplicated documentation snippets and replace @inheritParams tags.

Summary:

Right now there is a wiki page:

https://github.com/stan-dev/rstan/wiki/RStan-Mojave-Mac-OS-X-Prerequisite-Installation-Instructions

about a particular aspect of Mac OS X installation. Can we roll that into the basic install instructions?

https://github.com/stan-dev/rstan/wiki/RStan-Getting-Started

Otherwise, I fear people won't find it. Right now, there's a bunch of

Custom citations do not format according to provided cls as they do with typical rmarkdown/ bookdown documents. Not sure if this is an issue with pagedown but further investigation is needed.

Similar to RcppCore/RcppArmadillo#250, the implementation of the sample() functions in Rcpp need to be updated for R 3.6.x.

So, likely this will need a patch that mirrors what is available in Base R. c.f. Implementation changes.

• Rejection sampling routine
• [Implementation of R_unif_rand() in existi

I followed the advice in https://pagedown.rbind.io/#the-css-overriding-mechanism but my font would not change. Having played around a bit with the settings and the CSS I realised that I needed to add

/* font location goes here:*/
@import 'https://fonts.googleapis.com/css?family=Comic+Neue';

Before the body to made the font available.

The whole of the CSS for custom font now

The application authentification is not available.

The benefits of this authentification would be increased limit rate (https://developer.twitter.com/en/docs/basics/rate-limits)

The process to use application-only auth is explained here ([https://developer.twitter.com/en/docs/basics/authentication/overview/application-only](http

This can also demonstrate how they can be used with the new shiny vis_expect function from visdat.

#108 could have been prevented if knit_print tests captured this breaking change.

Adding test examples checking for knit_print output should provide reasonably detailed tests for brief_entries(), detailed_entries() and bibliography_entries() outputs.

It is not clear from the documentation what the intended usage is for outputs from stan_lm or stan_lm where you do not have hierarchies to pass to gather_draws() or spread_draws().

For example, fitting a very simple model with stan_lm():

library(tidyverse)
library(rstan)
library(rstanarm)
library(tidybayes)

test_stanlm <- stan_lm(mpg ~ cyl + disp + hp + drat + wt + vs +

The manual at https://rstudio.github.io/DT does not appear to have any index or table of contents. Unless an individual page (eg. https://rstudio.github.io/DT/002-rowdetails.html is explicitly linked to from another explanation, there's no way to know that it exists.

I figured out that I could look in the gh-pages branch for a page that might include documentation of filters and that's t

This is a suggested code or documentation change, improvement to the code, or feature request

The package is great works in most conditions (many thanks for this) but also makes lazy that I don't want to wrangle misread pdf pages. Hence, I'd like to request below.

Provide a parameter/method to specify the number of columns; start and end co-ordinates of each column so that table is extracted

It might be nice to have these functions:

• image_height

• image_width

• Maybe other things usually returned by image_info.

I always use magick::image_info(image_object)$height hence my wanting a shortcut. 😇

🎩 ✨ 🐇

It would be great if there was an option to preserve the original order of variables in plot_histogram(). Currently, variables within each page of the output seem to be ordered alphabetically but the pages themselves follow the original order.

I noticed that there is no information on what column space actually means when using pdf_data().

The only reference I found so far is that its meaning might be unclear: https://discuss.ropensci.org/t/pdftools-2-0-powerful-pdf-text-extraction-tools/1520/4

Should be in README or CONTRIBUTING and cover:

• Adding unit tests under current vdiffr framework
• Style (I think just reference advanced R here?)

The env_vars parameter requires a character vector. This is not reflected in the documentation for the parameter. See PR #335 I didn't look everywhere or regenerate the man files but if you agree I can do that if you want.