From: Eli Zaretskii <eliz@gnu.org>
To: "Gerd Möllmann" <gerd.moellmann@gmail.com>
Cc: emacs-devel@gnu.org
Subject: Re: MPS experiment successful
Date: Wed, 17 Apr 2024 18:49:48 +0300 [thread overview]
Message-ID: <86bk68gfab.fsf@gnu.org> (raw)
In-Reply-To: <m2pluogiy5.fsf@Pro.fritz.box> (message from Gerd Möllmann on Wed, 17 Apr 2024 16:30:42 +0200)
> From: Gerd Möllmann <gerd.moellmann@gmail.com>
> Cc: emacs-devel@gnu.org
> Date: Wed, 17 Apr 2024 16:30:42 +0200
>
> Eli Zaretskii <eliz@gnu.org> writes:
>
> >> That's all. There is nothing more. And I'm currently undecided how to
> >> proceed with this.
> >
> > The next step would be to push a feature branch into the Emacs Git
> > repository and let people try the branch on the other supported
> > platforms. If the code is not yet mature enough for that, please
> > suggest how to get from here to there.
>
> I think technically it could be done, but there are some things that
> would need to be done. From the top of my head:
>
> - CL packages vs. obarrays (I do have packages but no obarrays)
> - Handling of pure space
> - Handling the new JSON stuff, which I don't have in my branch, I think.
> - ...
The packages code will need to be moved aside, yes. But for the rest,
why shouldn't a simple merge do the job? They seem to be orthogonal,
by and large.
What is the issue with handling pure space?
> Will increase memory usage in its current state, part of which could be
> optimized.
How much larger is the memory footprint?
> Some configurations/platform might not be possible to support.
Which ones?
next prev parent reply other threads:[~2024-04-17 15:49 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-17 10:46 MPS experiment successful Gerd Möllmann
2024-04-17 12:22 ` Björn Bidar
[not found] ` <87cyqo89gk.fsf@>
2024-04-17 12:35 ` Björn Bidar
2024-04-17 13:09 ` Eli Zaretskii
2024-04-17 14:30 ` Gerd Möllmann
2024-04-17 15:49 ` Eli Zaretskii [this message]
2024-04-17 16:29 ` Gerd Möllmann
2024-04-17 17:51 ` Eli Zaretskii
2024-04-17 18:34 ` Gerd Möllmann
2024-04-17 19:21 ` Eli Zaretskii
2024-04-17 18:41 ` Gerd Möllmann
2024-04-17 19:23 ` Eli Zaretskii
2024-04-17 19:51 ` Gerd Möllmann
2024-04-17 23:45 ` Dmitry Gutov
2024-04-18 4:27 ` Gerd Möllmann
2024-04-18 5:08 ` Eli Zaretskii
2024-04-18 8:57 ` Gerd Möllmann
2024-04-18 19:18 ` Gerd Möllmann
2024-04-17 23:48 ` Dmitry Gutov
2024-04-18 4:31 ` Gerd Möllmann
2024-04-18 9:14 ` Andrea Corallo
[not found] ` <661fbf1d.050a0220.936ef.ee84SMTPIN_ADDED_BROKEN@mx.google.com>
2024-04-17 13:26 ` Gerd Möllmann
[not found] ` <661fc22e.170a0220.18fe3.c635SMTPIN_ADDED_BROKEN@mx.google.com>
2024-04-17 13:33 ` Gerd Möllmann
2024-04-17 14:22 ` Björn Bidar
[not found] ` <661fdb15.5d0a0220.4bfec.1ac8SMTPIN_ADDED_BROKEN@mx.google.com>
2024-04-17 14:34 ` Gerd Möllmann
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=86bk68gfab.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=gerd.moellmann@gmail.com \
/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.