Re: [ESS] Best Practice for building R packages

2020-10-08 Thread Jeremie Juste via ESS-help
Hello, On Thursday, 8 Oct 2020 at 09:05, Dirk Eddelbuettel via ESS-help wrote: > > Emacs is natural follow-up to this but there is _so much_ I wanted to cover > there that I am effectively overwhelmed and hence inactive. So let's turn > this upsite down and maybe _just_ focus on ESS. Shall we?

Re: [ESS] Best Practice for building R packages

2020-10-08 Thread Tyler Smith via ESS-help
That sounds fun! I have pried myself away from your t4 videos this morning, but will look them over soon - they look great! Best, Tyler Dirk Eddelbuettel writes: On 8 October 2020 at 13:17, Ahmadou Dicko wrote: | I do agree with your suggestion. There is much more to ESS than I | know and

Re: [ESS] Best Practice for building R packages

2020-10-08 Thread Dirk Eddelbuettel via ESS-help
On 8 October 2020 at 13:17, Ahmadou Dicko wrote: | 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. On 8 October 2020 at 09:38, Tyler Smith via ESS-help wrote: | I would also be interested in a

Re: [ESS] Best Practice for building R packages

2020-10-08 Thread Tyler Smith via ESS-help
I only update my package once or twice a year, and haven't created a new one in a while. That said, I really like the ESS/devtools integration. I usually have to dig into the docs to remind myself about `C-c C-o C-o` to get a new roxygen template, but that's much less effort than refreshing

Re: [ESS] Best Practice for building R packages

2020-10-08 Thread Ahmadou Dicko via ESS-help
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. Indeed, it would be great to pool

Re: [ESS] Best Practice for building R packages

2020-10-08 Thread Jeremie Juste via ESS-help
Hello Kasper, Thanks for sharing. > Personally, I'm a dinosaur so I'm still editing Rd files myself. I must > say, I'm not convinced about the merits of roxygen2. I admire your discipline. For my part, I feel that I would not document my functions properly unless I constrain myself to do it on

Re: [ESS] Best Practice for building R packages

2020-10-08 Thread Jeremie Juste via ESS-help
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,

Re: [ESS] Best Practice for building R packages

2020-10-08 Thread Kasper Daniel Hansen via ESS-help
Personally, I'm a dinosaur so I'm still editing Rd files myself. I must say, I'm not convinced about the merits of roxygen2. Having said that, I think it would make a lot of sense to have robust solutions in ESS supporting roxygen2 and these may even exist somewhere. On Thu, Oct 8, 2020 at 1:57

Re: [ESS] Best Practice for building R packages

2020-10-08 Thread Dirk Eddelbuettel via ESS-help
On 8 October 2020 at 13:39, Jeremie Juste via ESS-help wrote: | Is anyone using ESS to build R packages? Could you share your workflow please? 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

[ESS] Best Practice for building R packages

2020-10-08 Thread Jeremie Juste via ESS-help
Hello, Is anyone using ESS to build R packages? Could you share your workflow please? I read the doc of ESS about using roxygen to document the functions. By the way it looks like the link to [1] roxygen is broken and that roxygen2 has taken its place. I initially thought that I could use