[ESS] [OT] Best Practices Emacs / ESS Mini-Webinars

[Stephen Bond]

Hi Dirk,

I have been struggling with trying to follow the steps in 
https://r-pkgs.org/ and the best thing would be to have a similar
online book showing the steps with ESS. the Hadley book is chained to
RStudio and they assume everybody uses RStudio, so many examples do not
work as expected when run inside ESS/emacs. there is also some
completely undocumented menus like (Select package for evaluation) not
mentioned on the official ESS page: 
https://ess.r-project.org/Manual/ess.html
I am willing to help and donate time if you can start with such an
online book.
Cheers, really happy this may be happening.
S.

On Mon, 2020-12-28 at 08:08 -0600, Dirk Eddelbuettel via ESS-help
wrote:
> A few weeks ago a few of riffed about all the "known unknown" in
> using ESS
> and that teaching each other a few tricks would be cool.  We really
> should do
> this. To kick it off, maybe we should spawn a quick one-off mailing
> list (I
> have used groups.io before) or Slack instance (if someone wants to
> spawn one)
> to discuss.
> 
> From the top of my head I can think of possible topics such as
> 
>  - installing ESS (possibly special mention to the bundles by VG for
> Windows
>    and macOS, or KH for social science, or ...) -- no difficulty
> installing 
> 
>  - basic editing, highlighting etc maybe up to easily running
> multiple
>    buffers and renaming them
> 
>  - other relevant Emacs tricks ?
> 
>  - ESS and RMarkdown happily co-existing and examples / demos
> 
>  - package building with ESS (I tend to do it outside myself)
> 
>  - debugging with ESS
>  
>  - other Emacs voodoo like tramp use with ESS ?
> 
>  - object browsers
> 
>  - your most favourite trick here!
> 
>  - your second most favourite trick here too!
> 
> I have found that 'one topic' in a few slides and very few minutes
> works so
> we could easily split this across different interest and skills and
> environments used and whatever other factor.  Not everybody will know
> all
> topics to gaps are normal -- let's fill them.
> 
> Dirk
>