Stefan Fleck

Not a solution, but if you are on linux you can just have a terminal open with `tail -f logfile.log`. That's pretty close to real-time logging, though not to the...

colt is just a thin wrapper around crayon. So instead of `crayon::red()` you would use `colt::clt_chr_accent()`. `colt::clt_chr_accent()` then applies whatever function is defined in the currently active colt theme (in...

@dpeterson71 colt does not support by-package color themes, but its easy to disable colors for all packages that use colt (well, right now there is only one on CRAN, but...

It occurs only when *several* new columns would be added to the table due to pasting: ``` rhandsontable( iris, readOnly = FALSE, useTypes = FALSE, colHeaders = NULL ) ```...

Here is a reproducible shiny app example. Just try the procedure outlined above and the app will crash with `Warning: Error in genColHeaders: Change no recognized:afterChange` ``` library(rhandsontable) library(shiny) shinyApp(...

Nope no progress on this one :(

Oh thanks I did not realize that, thanks. To turn this issue in a feature request then; Is there no way around that? It's IMHO not 100% elegant to have...

I am not sure. I like the style sphinx uses where it combines the public fields with the constructor documentation (arguably all public fields should be exposed in the constructor...

It's implicit. The arguments to the constructor are what end up as public fields. I guess it's a rather simplisitc example, but I would imagine that this is the most...

Fair enough. It would still be great to get rid of the warnings somehow. Maybe something like `@describeIn myclass$initialize` or similar could be supported at some point?