From: gerd.moellmann@t-online.de (Gerd Moellmann)
Cc: rms@gnu.org, emacs-devel@gnu.org
Subject: Re: [storm@cua.dk: Redisplay bug in latest CVS]
Date: 15 May 2002 20:24:49 +0200 [thread overview]
Message-ID: <867km5s1zi.fsf@gerd.dnsq.org> (raw)
In-Reply-To: 9791-Wed15May2002192434+0300-eliz@is.elta.co.il
"Eli Zaretskii" <eliz@is.elta.co.il> writes:
> > From: gerd.moellmann@t-online.de
> > Date: 15 May 2002 15:50:45 +0200
> >
> > The Emacs/Guile plan has moved Emacs to the low end of my personal
> > priority list. I'll queue reports, but it's currently unlikely that
> > I'll work on them.
>
> If moving to Guile means we lose Gerd's help, then I'm against moving
> to Guile as a matter of practice.
I see that what I wrote can be misunderstood, for example as simply
being opposed to Scheme or Guile as a matter of principle. So please
let me clarify.
There are technical reasons for being against a reimplementation of
ELisp in Guile, or for making Guile Emacs' principal extension
language. These issues can theoretically be solved with enough
effort. I personally think there's too much effort and risk involved;
others might find that debatable or irrelevant in the bigger GNU
picture. I also don't like the way this crept up again, but this is a
completely different story which I won't belabor here. Anyway,
although I'm against such a move, the reason Emacs has lost priority
for me _today_ is this, in short:
The "new" redisplay is anything but new for me. Today, working on it
is for me a mixture of incredibly boring and inherently and constantly
complex that makes it essentially a pain in the neck. That's not a
good motivation, of course, and it's getting worse.
In the past, it helped me to find something else in Emacs to work on,
and do a bit there, a bit in redisplay etc. Lately, the only "else"
part remaining that might have interested me enough was the ELisp
interpreter. But work there doesn't make sense when the ELisp
implementation is anyway replaced, and something else becomes the
primary extension language. (What makes sense is working on Guile
instead (not saying that I'll do that.))
(I've been looking for other projects that might play that role, but
there's currently nothing.)
So, no motivation => low priority.
next prev parent reply other threads:[~2002-05-15 18:24 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-05-15 7:01 [storm@cua.dk: Redisplay bug in latest CVS] Richard Stallman
2002-05-15 13:50 ` Gerd Moellmann
2002-05-15 14:03 ` Miles Bader
2002-05-15 15:11 ` Gerd Moellmann
2002-05-15 15:29 ` Miles Bader
2002-05-15 15:56 ` Gerd Moellmann
2002-05-15 16:24 ` Eli Zaretskii
2002-05-15 18:24 ` Gerd Moellmann [this message]
2002-05-15 21:49 ` Thien-Thi Nguyen
2002-05-16 20:24 ` Richard Stallman
2002-05-16 21:47 ` Gerd Moellmann
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=867km5s1zi.fsf@gerd.dnsq.org \
--to=gerd.moellmann@t-online.de \
--cc=emacs-devel@gnu.org \
--cc=rms@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 public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).