From: Philip Kaludercic <philipk@posteo.net>
To: Eli Zaretskii <eliz@gnu.org>
Cc: emacs-devel@gnu.org
Subject: Re: Suggestions for "Emacs development updates" at Emacs Conf
Date: Fri, 18 Oct 2024 10:21:52 +0000 [thread overview]
Message-ID: <87y12liudb.fsf@posteo.net> (raw)
In-Reply-To: <86frotopx8.fsf@gnu.org> (Eli Zaretskii's message of "Fri, 18 Oct 2024 10:01:23 +0300")
Eli Zaretskii <eliz@gnu.org> writes:
>> From: Philip Kaludercic <philipk@posteo.net>
>> Date: Sun, 13 Oct 2024 10:20:06 +0000
>>
>> Sacha Chua has asked me to present this years "Emacs development update"
>> at Emacs Conf [0], specifically focusing on Emacs 30. I think we have a
>> good overview of the most interesting features from Emacs 30 on Emacs
>> Wiki [1], or is there anything else we should mention?
>>
>> I wanted to ask if someone could summarise me the status of the the
>> incremental GC branch? From what I understand (as I didn't have the
>> time to follow the thread), that is the biggest upcoming feature.
>>
>> [0] https://emacsconf.org/2024/
>> [1] https://www.emacswiki.org/emacs/EmacsThirtyHighlights
>
> It isn't clear to me whether your presentation should focus on Emacs
> 30 or Emacs 31 or something else. The igc branch may be ready in time
> for Emacs 31, but even that is not sure at this time; it certainly
> won't be in Emacs 30.
The idea was to focus on Emacs 30; I was just wondering if there was
already something that would be worth mentioning from Emacs 31.
> IMO, it's too early to talk about what will be in Emacs 31. Even if
> you want to describe a small number of major new features, there's not
> yet enough stuff in NEWS for that. Better support for DND on Windows
> and color fonts on MS-Windows is probably good news for users of
> Windows, but that's Windows-only news.
>
> If the subject is interesting future developments in Emacs, then igc
> is by far the most interesting one. But I don't have any suggestions
> for any others.
OK, then I'll probably just talk about Emacs 30.
> For Emacs 30, just go by Antinews in the two manuals: they are
> supposed to mention the more important changes.
1+
> HTH, and thanks in advance.
--
Philip Kaludercic on siskin
prev parent reply other threads:[~2024-10-18 10:21 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-13 10:20 Suggestions for "Emacs development updates" at Emacs Conf Philip Kaludercic
2024-10-18 7:01 ` Eli Zaretskii
2024-10-18 7:48 ` Stefan Kangas
2024-10-18 10:21 ` Philip Kaludercic [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87y12liudb.fsf@posteo.net \
--to=philipk@posteo.net \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.