On Sat, May 22, 2021 at 5:49 AM David Bremner wrote:
>
> Felipe Contreras writes:
>
> > Ruby is a gc language, we shouldn't be doing workaround to free memory when
> > Ruby is perfectly
> > capable of doing so.
> >
> > The problem is that talloc wants to be smart, and Ruby and talloc both
> > f
On Thu 2021-05-27 20:11:13 +0300, Tomi Ollila wrote:
> On Thu, May 27 2021, Daniel Kahn Gillmor wrote:
>> +Keymaps are no longer fset, which means they need to be referred to in
>> +define-key directly (without quotes). If your ~/.emacs has a
>
> In our docs it would be better to refer ~/.emacs.d/
On Thu, May 27 2021, Daniel Kahn Gillmor wrote:
> See list discussion in thread starting with
> id:87h7ip2baq@fifthhorseman.net for more details.
>
> Signed-off-by: Daniel Kahn Gillmor
> ---
> NEWS | 7 +++
> 1 file changed, 7 insertions(+)
>
> diff --git a/NEWS b/NEWS
> index c0ae6afe..
See list discussion in thread starting with
id:87h7ip2baq@fifthhorseman.net for more details.
Signed-off-by: Daniel Kahn Gillmor
---
NEWS | 7 +++
1 file changed, 7 insertions(+)
diff --git a/NEWS b/NEWS
index c0ae6afe..c3ca1085 100644
--- a/NEWS
+++ b/NEWS
@@ -101,6 +101,13 @@ Removed,
Daniel Kahn Gillmor writes:
> If we don't want to go through the full hassle of deprecation and delay
> before final removal, it seems like a mention in NEWS is at least
> worthwhile.
>
Since the change is released, it's a bit late to uh, not release it ;).
No objection to adding to NEWS retroac
On Wed 2021-05-26 23:34:47 -0400, Kyle Meyer wrote:
> Daniel Kahn Gillmor writes:
>
>> I worry that this is due to one of the two following commits but my
>> elisp-foo is weak enough that i don't know what the right next steps are:
>
> It's due to the second commit, 05a436f7 (emacs: don't fset keym
