From: Carsten Dominik <carsten.dominik@gmail.com>
To: Michael Sperber <sperber@deinprogramm.de>
Cc: emacs-orgmode@gnu.org
Subject: Re: Re: Support (or not) for Emacs 21, and XEmacs
Date: Mon, 19 Apr 2010 17:59:25 +0200 [thread overview]
Message-ID: <A0E1F0DC-3C91-4ECD-B246-92635AADE3F1@gmail.com> (raw)
In-Reply-To: <y9l4oj7672m.fsf@deinprogramm.de>
On Apr 19, 2010, at 1:00 PM, Michael Sperber wrote:
>
> Carsten Dominik <carsten.dominik@gmail.com> writes:
>
>> The compromise for me would be this:
>>
>> - You fix the things above.
>> - I leave the rest of the necessary compatibility code in
>> - I program any new features with whatever is available
>> in Emacs 22/23 and rely on you to make it XEmacs compatible.....
>
> That would be wonderful. I'll see that the issues are addressed:
>
>> 1. posix character classes in regular expressions, thinks like
>> [:alpha:]
>> These are nice because they work well with arbitrary languages.
>> Does XEmacs suppor these now?
>
> No, but I'll see to it that they are.
Right now I am using a macro to replace them with the corresponding
ASCII character sets - but this is not nice and even wrong in foreign
languages.
>
>> 2. The overlay API - I think XEmacs actually has a compatibility lib
>> for these, is that correct?
>
> Correct.
>
>> One of the things you could do it to figure out if I can also
>> switch
>> to the API calls overlays-in and overlays-at in that library.
>
> You should, anyway: I'll take care of any problems. I take it
> something
> about these didn't work for you in the past: If that is so, a sentence
> or two on what those problems were would be much appreciated.
I don't remember - I wrote these compatibility functions without
knowledge
of the library in XEmacs. So it is well possible that the library
functions just work - I will just switch - and wait for any bug reports.
>
>> 3. outline.el. Last time looked, XEmacs still had the horrible old
>> outline.el which is pretty much impossible to program.
>> I do have a port, xemacs/noutline.el in the Org distribution - if
>> you
>> could get that into XEmacs, that would get rid of a major
>> annoyance,
>> including complicated installation instructions.
>
> I'm working on this right now - should be no big problem. A few minor
> incompatibilities with our current outline.el need to be addressed,
> but
> I'm working on them.
OK. This is a potential source of future problems - but we will see.
>
>> 4. Can you make XEmacs understand mouse-3 instead of button3 ? Or
>> maybe it does understand these by now?
>
> No; I'll try to get this in.
>
> Won't all happen overnight, but I'm getting to work on it. I very
> much
> appreciate your willingness to help!
Thank you for your willingness to take much off my task list.
- Carsten
next prev parent reply other threads:[~2010-04-19 15:59 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-14 8:15 Support (or not) for Emacs 21, and XEmacs Carsten Dominik
2010-04-16 10:26 ` Carsten Dominik
2010-04-16 10:27 ` Carsten Dominik
2010-04-16 12:19 ` Matt Lundin
2010-04-16 16:41 ` Carsten Dominik
2010-04-16 13:03 ` Sebastian Rose
2010-04-16 13:13 ` Bernt Hansen
2010-04-16 14:39 ` Carsten Dominik
2010-04-16 14:42 ` Bernt Hansen
2010-04-16 14:42 ` Carsten Dominik
2010-04-16 19:15 ` Bernt Hansen
2010-04-16 22:02 ` Carsten Dominik
2010-04-16 13:32 ` Rémi Vanicat
2010-04-16 13:56 ` Sebastian Rose
2010-04-16 13:07 ` Jan Böcker
2010-04-16 13:47 ` Günter Kolousek
2010-04-17 15:39 ` Michael Sperber
2010-04-17 20:31 ` Carsten Dominik
2010-04-18 8:22 ` Michael Sperber
2010-04-18 14:03 ` Carsten Dominik
2010-04-19 11:00 ` Michael Sperber
2010-04-19 11:19 ` Michael Sperber
2010-04-19 15:51 ` Carsten Dominik
2010-04-19 15:54 ` Michael Sperber
2010-04-19 15:55 ` Carsten Dominik
2010-04-19 15:59 ` Carsten Dominik [this message]
2010-05-07 7:51 ` Carsten Dominik
2010-05-07 8:30 ` Michael Sperber
2010-05-07 9:21 ` Carsten Dominik
2010-04-23 15:50 ` Michael Sperber
2010-04-23 19:03 ` Carsten Dominik
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.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=A0E1F0DC-3C91-4ECD-B246-92635AADE3F1@gmail.com \
--to=carsten.dominik@gmail.com \
--cc=emacs-orgmode@gnu.org \
--cc=sperber@deinprogramm.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 public inbox
https://git.savannah.gnu.org/cgit/emacs/org-mode.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).