Hello Dirk, On Thursday, 8 Oct 2020 at 06:57, Dirk Eddelbuettel wrote:
> We all may be a little different here. > > ESS now wraps around devtools, but my practices predate devtools. So I still > build, test, install, ... on the command-line for which I use wrappers (from > my littler package, just updated yesterday) named > build.r > check.r > rcc.r # a nicer checker around rmdcheck > roxy.r # run roxygen, I use a 'cached' 6.1.1 version that does not > force recompile... > install.r # plus various install* variants for BioC, or GitHub, or > binaries... > kitten.r # using a wrapper around package.skeleton() > render.r # run rmarkdown::render() > ... Many thanks for sharing this. It is an option that suites me perfectly. > It may actually make sense for _all of use_ to maybe pool for two or three > hours and a webinar over Zoom for 'favourite ESS' tricks. I keep forgetting > how there is -- just yesterday I once again forgot C-c C-e w and looked for > the cheat sheet pdf and there are a bootload of options I never used > ... I do agree with your suggestion. There is much more to ESS than I know and it would be great if we could pool our resources to improve further. For my part `ess-describe-object-at-point` really improved by workflow as it can be customized to include any function. Best regards, -- Jeremie Juste ______________________________________________ ESS-help@r-project.org mailing list https://stat.ethz.ch/mailman/listinfo/ess-help