Hi Idor: This last remark below can’t possibly be true. Because I did not intend to trigger a release, ESS 24.01.0 was not initially tagged. However, after I received that email from ELPA, it was a fait accompli. So I fixed some cosmetic issues and tagged it post-haste, i.e., ELPA’s announcement is definitely pre-tagging. So I’m not sure where the disconnect is. But, again, I don’t find the package mechanism at all convenient and will have to spend some time debugging since it has never worked for me. I will put these ELPA/MELPA issues on my growing TODO list. Thanks for pointing this out!
-- Rodney Sparapani, Associate Professor of Biostatistics, He/Him/His Vice President, Wisconsin Chapter of the American Statistical Association Institute for Health and Equity, Division of Biostatistics Medical College of Wisconsin, Milwaukee Campus If this is outside of working hours, then please respond when convenient. From: Ihor Radchenko <yanta...@posteo.net> Date: Thursday, January 25, 2024 at 9:30 AM To: Sparapani, Rodney <rspar...@mcw.edu> Cc: Martin Maechler <maech...@stat.math.ethz.ch>, ess-c...@r-project.org <ess-c...@r-project.org>, Jack Kamm <jackk...@gmail.com>, emacs-orgmode@gnu.org <emacs-orgmode@gnu.org>, Liu Hui <liuhui1...@gmail.com> Subject: Re: [PATCH] Add buffer-local setting to request specific ESS process/session name (was: [PATCH] Set Python shell in Org edit buffer) Also, unlike MELPA, ELPA uses stable (tagged) releases by default. Unstable releases (latest commit) are only available on demand, via ELPA-devel (https://urldefense.com/v3/__https://elpa.gnu.org/devel/ess.html__;!!H8mHWRdzp34!98PglwLJJtQrc63k3vrtr0K0MjYZSPEf3WV0GPD_wsxbsO3bM8AYCDRI0W69ZcBg5STqpaG7_h3rF8wlAQ$<https://urldefense.com/v3/__https:/elpa.gnu.org/devel/ess.html__;!!H8mHWRdzp34!98PglwLJJtQrc63k3vrtr0K0MjYZSPEf3WV0GPD_wsxbsO3bM8AYCDRI0W69ZcBg5STqpaG7_h3rF8wlAQ$> )
