[ESS] Advice on setting up ESS to edit and knit Rmarkdown files
||one|@hry @end|ng |rom gm@||@com
Wed Sep 22 15:15:42 CEST 2021
We'd love to do a release but ESS is not in a good place right now.
Recent versions of Emacs interrupt background commands (essential to
completion and contextual help like eldoc) when the user starts
typing, which causes hard to solve problems.
The dev branch is mostly working but not 100% correctly. Unfortunately
none of us seem to have the time to work on ESS at the moment.
That said, while Martin, Vitalie and I notice issues here and there,
we haven't had serious bug reports in a while, despite the dev branch
being used by many Melpa users. So maybe releasing in the current
state is better than nothing.
On 9/22/21, Dirk Eddelbuettel via ESS-help <ess-help using r-project.org> wrote:
> On 20 September 2021 at 13:59, Sparapani, Rodney via ESS-help wrote:
> | Generally, this stuff should just work out-of-the-box.
> | And we are not a company like RStudio so this FOSS setup works for us as
> | developers and hopefully it still serves the users well.
> But legal structure has nothing to with 'calling a release'. Which is done
> authors (who should know the code better than users) saying "yep what we
> at HEAD right now is good" and then cut a tarball. That is a _marker_.
> Which some less-informed people like me can take (and then ship downstream
> Debian, and with that Ubuntu etc).
> Without a marker, no shipment. Less ideal to me and others.
> So pretty-please if someone would: could a release one of these moons. It
> does not have to be frequent or regularly schedule or anything. But maybe
> more often than once every few years? Maybe when you sync with upstream
> Emacs (assuming you do now)?
> https://dirk.eddelbuettel.com | @eddelbuettel | edd using debian.org
> ESS-help using r-project.org mailing list
More information about the ESS-help