Thank Uwe, I also had some discussions on Twitter with various people
about this.
Thanks to Brodie Gaslam (@BrodieG) via Twitter, a solution seems to be
to set the global option `cli.unicode` to `FALSE` for checking, as
this is coming from the cli pkg.
Hence for my purposes in examples I am using
On 17.01.2019 00:41, Gavin Simpson wrote:
Dear List,
The latest version of tibble 2.0.1 is printing output (on Linux at
least) that contains a UTF-8 ellipsis … instead of the previous three
periods ...
Please ask the tibble maintainer what this is about.
In my opinion this should be changed
Dear List,
The latest version of tibble 2.0.1 is printing output (on Linux at
least) that contains a UTF-8 ellipsis … instead of the previous three
periods ...
This is causing some differences between the reference materials for
my pkg examples that I generate locally on Linux and the output
gene
