From: Carsten Dominik <carsten.dominik@gmail.com>
To: Leo <sdl.web@gmail.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: Re: undo in org.el
Date: Tue, 13 Nov 2007 23:12:05 +0100 [thread overview]
Message-ID: <6F39CE50-0F79-4E6E-9390-FAF1560C4A88@science.uva.nl> (raw)
In-Reply-To: <m3tznpuakd.fsf@cam.ac.uk>
On 13Nov2007, at 9:58 PM, Leo wrote:
> On 2007-11-13 15:37 +0000, Carsten Dominik wrote:
> [...]
>>> If that was a call to Xemacs users to identify themselves, then here
>>> is one. Even though it is in the Emacs CVS tree now should not
>>> turn it
>>> into an Emacs only tool IMHO.
>>
>> Well, the fact that it is in Emacs CVS has not kept me from
>> supporting
>> XEmacs for quite a while now. But it is extra work and requires
>> catering for missing features and different implementations - so
>> it is
>> important for me to know that this is used and still appreciated.
>>
>> How about someone stepping forward and trying to release an XEmacs
>> package containing noutline.el and org-mode? Anyone who feels up to
>> this? Because I will not have the time.
>>
>> - Carsten
>
> I think org 5.13 (or maybe 5.14) can be used by XEmacs users for
> foreseeable feature. Remember XEmacs is packaging quite a few outdated
> package anyway such as AUCTeX (11.5x).
>
> If no one steps up for this task, we should start thinking of moving
> forward anyway.
I am not sure what you mean by "moving forward". Sure, the world can
survive withoout an XEmacs package for Org-mode.
However, even if the package would not be up-to-date, it would be
nice if XEmacs users would get some version simply with the sumo
tarball. Would lower the the entry borders quite a bit in my
opinion. Lets not forget that not everyone is as happy to download a
new version of a package frequently as we are here...
Anyway, just a thought. I will continue to support XEmacs as much as
I can, within the limits of available time. But that support already
has some holes, most importantly columns view does not work with it
and the difficulties to make it work are so substantial that I am not
expecting to ever get around to it.
We should all thank Gregory Chernov again for porting noutline to
XEmacs - without that I would have given up long ago.
- Carsten
next prev parent reply other threads:[~2007-11-13 22:12 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-12 21:23 undo in org.el Leo
2007-11-13 9:03 ` Carsten Dominik
2007-11-13 11:44 ` Tim O'Callaghan
2007-11-13 15:28 ` Ed Hirgelt
2007-11-13 15:37 ` Carsten Dominik
2007-11-13 20:58 ` Leo
2007-11-13 22:12 ` Carsten Dominik [this message]
2007-11-15 11:45 ` Dr. Volker Zell
2007-11-15 11:55 ` Carsten Dominik
2007-11-13 22:50 ` Wes Nakamura
[not found] ` <E6B22961-FEA9-4D09-9743-64202CB7DB8D@science.uva.nl>
2007-11-14 8:08 ` Carsten Dominik
2007-11-14 8:13 ` Tassilo Horn
2007-11-14 15:02 ` William Henney
2007-11-14 19:46 ` Tassilo Horn
2007-11-14 22:37 ` William Henney
2007-11-14 9:02 ` Carsten Dominik
2007-11-13 12:15 ` Dr. Volker Zell
2007-11-13 12:19 ` Stefan Kamphausen
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=6F39CE50-0F79-4E6E-9390-FAF1560C4A88@science.uva.nl \
--to=carsten.dominik@gmail.com \
--cc=emacs-orgmode@gnu.org \
--cc=sdl.web@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 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).