all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: joakim@verona.se
To: emacs-devel@gnu.org
Cc: klaus.berndl@sdm.de
Subject: Re: Things I would like to be added after the release
Date: Tue, 29 May 2007 12:02:45 +0200	[thread overview]
Message-ID: <m3veecdk1m.fsf@kurono.home> (raw)
In-Reply-To: A47B192B0358794C958615D788BF7FB70352586E@mucmail1.sdm.de

<klaus.berndl@sdm.de> writes:

> joakim@verona.se wrote:
>
> But here is (4): Currently ECB contains a lot of compatibility-code so
> ECB runs as best as possible with Emacs and XEmacs... this is a goal of
> ECB and should remain as a goal. I doubt Richard wants to have XEmacs-
> compatibility-code in the ECB integrated in the Emacs-trunc ;-)
>
> But then we would have to maintain two ECB-trunks: That one integrated into
> Emacs and that one running with both emacs-flavors...
>
> In general i would greatly appreciate if ECB could be integrated into Emacs but
> seems really be a big big job...

As far as I've been able to gather from this list, having XEmacs
compatibility code in an Emacs package isnt a problem in principle,
though it might become a maintenance problem.

If ECB is integrated in Emacs, and interfaces between lisp code and
the C core are worked out, the maintenance burden might even become
less because XEmacs might choose to implement the same
interfaces. (Ok, this is naive optimism, but this list might benefit
from some of that :)

> To get a realistic picture about the necessary code-changing-efforts it would 
> help to get a "review" of the code from one of the Emacs-gurus responsible for
> Emacs-coding-guidelines and responsible for integrating big packages...
> The code is well documented (at least in most cases) and should follow
> Emacs coding standards... but its really a huge code-base!
>
> Klaus
>
>> 
>> 
>>> everyone involved.
>>> 
>>> Would people like to start on these tasks?

-- 
Joakim Verona
http://www.verona.se

  parent reply	other threads:[~2007-05-29 10:02 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-05-28  9:04 Things I would like to be added after the release joakim
2007-05-29  0:02 ` Richard Stallman
2007-05-29  8:02   ` joakim
2007-05-29  9:36     ` klaus.berndl
2007-05-29  9:52       ` Michael Albinus
2007-05-29  9:56       ` David Kastrup
2007-06-16  5:01         ` T. V. Raman
2007-06-16 18:50           ` Richard Stallman
2007-06-16 23:37             ` T. V. Raman
2007-06-16 23:50               ` Miles Bader
2007-06-17 18:08                 ` T. V. Raman
2007-06-17 20:15                   ` Nick Roberts
2007-06-18  3:25                     ` Stephen J. Turnbull
2007-06-18 21:31                       ` Richard Stallman
2007-06-21  7:29                       ` T. V. Raman
2007-06-21  8:09                         ` Stefan Monnier
2007-06-17  8:54               ` Richard Stallman
2007-06-17 12:47           ` Stefan Monnier
2007-06-17 16:00             ` joakim
2007-05-29 10:02       ` joakim [this message]
2007-05-29 10:16         ` David Kastrup
2007-06-02  2:54       ` Richard Stallman
2007-06-04  0:17     ` Richard Stallman
2007-06-04  0:17     ` Richard Stallman

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=m3veecdk1m.fsf@kurono.home \
    --to=joakim@verona.se \
    --cc=emacs-devel@gnu.org \
    --cc=klaus.berndl@sdm.de \
    /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.