Advertise reprex #69
Advertise reprex #69
Comments
I like this idea too. |
@krlmlr Is this what you had in mind? Here's the output of mean(rnorm(3))
#> [1] -0.6492532 reprex::reprex_info()
#> Created on Tue Oct 10 23:00:27 2017 with the reprex package This might look a little silly -- why not just include the output? It's not easy to get knitr to format this chunk like the others if it includes no code, e.g. if I can't decide if |
Maybe put it at the top? So it's more easily skimmed past? Use ISO8601? reprex::reprex_info()
#> Created by the reprex package; 2017-10-10
mean(rnorm(3))
#> [1] -0.6492532 I think it makes sense to include by default. It only adds 3 lines, is easily deleted if you don't want it, and provides useful information. |
OK @hadley how's this? Use of Output of Created by the reprex package; 2017-10-11 mean(rnorm(3))
#> [1] 0.3626104 |
Or I could stick it at the top of the body, i.e. do exactly what you have above. Alternative output of reprex::reprex_info()
#> Created by the reprex package; 2017-10-11
mean(rnorm(3))
#> [1] -1.212095 |
I think I still prefer the second form. Maybe also include reprex's version number? |
OK here's where we ended up. reprex::reprex_info()
#> Created by the reprex package v0.1.1.9000 on 2017-10-12
mean(rnorm(3))
#> [1] -0.02475685 |
Summarizing recent ideas from Slack convo:
|
Have you considered inserting a comment
# Created on ${date} using the reprex package
at the top or the bottom of the output? Both as a quality indicator and a hint to users who don't know the package yet.The text was updated successfully, but these errors were encountered: