From: David Kastrup <dak@gnu.org>
To: help-gnu-emacs@gnu.org
Subject: Re: Gnu Emacs and gnuclient
Date: Thu, 22 Feb 2007 21:56:58 +0100 [thread overview]
Message-ID: <851wkhewrp.fsf@lola.goethe.zz> (raw)
In-Reply-To: 87slcy3tsi.fsf@post.rwth-aachen.de
Thorsten Bonow <thorsten.bonow@post.rwth-aachen.de> writes:
> I *love* the Multi-tty features. If the XEmacs team doesn't get
> their act together any time soon, I will do the switch away from my
> beloved XEmacs because of this feature alone (Sigh).
Uh, what?
The whole point of the awfully overdesigned
locale/specifier/instantiator system in XEmacs that has from the
beginning made it impossible for anybody but the very gifted to
actually program and/or understand code seriously making use of images
and toolbars has been the support of multiple ttys with different
capabilities.
Consequently, XEmacs' gnuclient can open a frame right in the
gnuclient tty. It's been a selling point of XEmacs for decades,
actually.
Now as far as I can tell, the programming APIs of Emacs' multi-tty
support will be much much easier to understand and use.
But the basic _feature_ has, as far as I can judge, been available to
users pretty much from the beginning of Lucid Emacs' separate
existence.
I can't think of any feature gap that took Emacs longer to close.
So as long as you are talking about the user-level feature (and not
the programmers' API), I am somewhat at a loss about why this would
make you consider a switch.
I am certainly not above XEmacs-bashing, but I would not have thought
user-level multi-tty support a suitable area. It's been around in
XEmacs from very early on as far as I can tell. So could you
elaborate?
--
David Kastrup, Kriemhildstr. 15, 44793 Bochum
next prev parent reply other threads:[~2007-02-22 20:56 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-22 17:35 Gnu Emacs and gnuclient Tim
2007-02-22 18:56 ` Thorsten Bonow
2007-02-22 19:10 ` Tim
2007-02-22 20:56 ` David Kastrup [this message]
2007-02-22 22:16 ` Thorsten Bonow
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=851wkhewrp.fsf@lola.goethe.zz \
--to=dak@gnu.org \
--cc=help-gnu-emacs@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 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.