The opening code example is given as:

$ echo 'foo\nbar\nfoo' | sort | uniq -c | sort -nr
2 foo
1 bar
$ echo 'foo\nbar\nfoo' | sort | uniq -c | sort -nr |

but should be:

$ echo -e 'foo\nbar\nfoo' | sort | uniq -c | sort -nr
2 foo
1 bar
$ echo -e 'foo\nbar\nfoo' | sort | uniq -c | sort -nr |

-e switch is required for interpolating escaped \n. Without it, the example

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/

I really appreciate the work that you've put into engineering it so that we can create animated plots in R, but I would really appreciate if you could document examples (in the form of vignettes), and describe in more details the terms and metaphors used. I've been trying to use the gganimate package but I have been facing some problems with understanding what some of the terms / metaphors used in

@simonbyrne noticed that the Gallery/Tutorial is slow to load. we should think about breaking it up into sub-pages, or using SVG instead of SVGJS, or ...

Many of the issues filed for this package are unsurprisingly font related.

To help alleviate or even prevent these issues, the package needs:

• better documentation on fonts
• platform-specific helpers for installation & triage
• robust platform detection (down to version & patch level) to ensure the right font names are used on the right platform since legacy operating systems like Windo

The documentation of the nudge options does not specify the units of these values. It would help new users to clarify this.

They are probably in the same units as the data values for these axes? But they might’ve been relative units for the plotted axis (e.g. 0.5 would nudge the position by half of the axis length), or even absolute units for the plot (like the units for many of the other opti

Under "Keeps factor by default levels now", the second chart shows 100% thing1. It seems like it should show 100% thing2, just like the chart immediately above. That's what is in the data.

When paginating a faceted plot that has an odd number of plots, so the last page's plots do not fill that page - I find that the ggplot title that is centered over the page, becomes centered over the remaining plots on the last page.

Code:

n_pages <- ceiling(length(levels(diamonds$cut)) * length(levels(diamonds$clarity)) / 3)

# Draw each page
for (i in seq_len(n_pages)) {
  p

Hello,
I have tried to find guidance on what s_shape is actually doing in geom_encircle() it is used in a number of the examples but not (as far as I can find) described anywhere?

Cheers

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

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 +

A major advantage of moving to the package structure is that we can use pkgdown to create a slick website to replace the README. In addition to documenting the package functions, each major section of the README can be an individual vignette/article.

Hi
The package is great. Just starting using it. But got a hard time trying to figure out how to link my table using "%<+%"
Suggestion: Include a comment saying that either the data has a "label" column to link with the tip label in the tree, or that it will use the first column by default.
Nicely done!

Carlos Alberto

A nice & potentially useful package, but w/o more detailed description of the parameters and their ranges, one is left to guess what they might be, and then iterate to find something that works.

p_x, p_y, s_x, s_y, s_height, s_width, ... ? What is the frame of reference for *_x., *_y positions? What is the relation of *_height, *_width to this?

Should be in README or CONTRIBUTING and cover:

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

Hi, thanks for the work on this very useful package!

This might be a dumb thought, but I was wondering if it would be possible to incorporate jitter'ed points (probably through geom_jitter) as an option. I'm not sure if it would be better to calculate the density before or after jittering, too.

Thanks again!