From: Dan Nicolaescu <dann@ics.uci.edu>
To: Eli Zaretskii <eliz@gnu.org>
Cc: emacs-devel@gnu.org
Subject: Re: [multi-tty] Emacs port status
Date: Sun, 20 May 2007 08:49:06 -0700 [thread overview]
Message-ID: <200705201549.l4KFn6W3012902@oogie-boogie.ics.uci.edu> (raw)
In-Reply-To: <uabw2uqnj.fsf@gnu.org> (Eli Zaretskii's message of "Fri\, 18 May 2007 17\:56\:16 +0300")
Eli Zaretskii <eliz@gnu.org> writes:
> > From: David Kastrup <dak@gnu.org>
> > Date: Thu, 17 May 2007 23:14:18 +0200
> > Cc: Emacs Devel <emacs-devel@gnu.org>
> >
> > Jason Rumney <jasonr@gnu.org> writes:
> >
> > > Thanks to some help from Dan Nicolaescu, I think we have reached a
> > > point with the Windows port where I would be comfortable merging
> > > into the trunk.
> >
> > That was pleasantly fast. Of the other ports, probably the MSDOS port
> > will provide the most puzzlers.
>
> I'm not sure I will continue the MSDOS support in Emacs 23. It sounds
> like Emacs 23 will be Unicode-based; if that is indeed so, it will be
> most probably well beyond my resources to make all the Unicode-related
> features work on MSDOS.
If you decide you want to still keep the MSDOS port, don't let
multi-tty deter you, a port is not hard to do.
next prev parent reply other threads:[~2007-05-20 15:49 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-17 20:52 [multi-tty] Emacs port status Jason Rumney
2007-05-17 21:14 ` David Kastrup
2007-05-18 14:56 ` Eli Zaretskii
2007-05-18 19:09 ` Károly Lőrentey
2007-05-18 19:56 ` [multi-tty] X or tty (was Re: Emacs port status) csant
2007-05-18 20:14 ` [multi-tty] X or tty David Kastrup
2007-05-18 20:39 ` csant
2007-05-18 20:59 ` David Kastrup
2007-05-20 11:47 ` Károly Lőrentey
2007-05-20 11:43 ` [multi-tty] X or tty (was Re: Emacs port status) Karoly Lorentey
2007-05-19 11:15 ` [multi-tty] Emacs port status Eli Zaretskii
2007-05-19 10:55 ` Richard Stallman
2007-05-19 11:11 ` Eli Zaretskii
2007-05-19 11:29 ` Juanma Barranquero
2007-05-20 6:50 ` Richard Stallman
2007-05-20 7:35 ` David Kastrup
2007-05-20 18:57 ` Eli Zaretskii
2007-05-20 22:04 ` Richard Stallman
2007-05-20 18:56 ` Eli Zaretskii
2007-05-20 11:32 ` Kenichi Handa
2007-05-20 19:09 ` Eli Zaretskii
2007-05-20 15:49 ` Dan Nicolaescu [this message]
2007-05-20 19:14 ` Eli Zaretskii
2007-05-18 3:06 ` Károly Lo"rentey
2007-05-19 23:25 ` MacOS port functional too (was Re: [multi-tty] Emacs port status) Dan Nicolaescu
2007-05-20 9:26 ` MacOS port functional too David Kastrup
2007-05-20 18:59 ` Eli Zaretskii
2007-05-20 20:38 ` Jason Rumney
2007-05-21 6:00 ` vms for emacs [was: MacOS port functional too] Thien-Thi Nguyen
2007-05-21 7:21 ` vms for emacs David Kastrup
2007-05-21 11:21 ` jasonr
2007-05-21 11:32 ` David Kastrup
2007-05-21 13:14 ` Miles Bader
2007-05-22 8:30 ` Richard Stallman
2007-05-21 14:22 ` vms for emacs [was: MacOS port functional too] Chip Coldwell
2007-05-22 5:25 ` dhruva
2007-05-21 10:33 ` MacOS port functional too Richard Stallman
2007-05-20 16:12 ` MacOS port functional too (was Re: [multi-tty] Emacs port status) Karoly Lorentey
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=200705201549.l4KFn6W3012902@oogie-boogie.ics.uci.edu \
--to=dann@ics.uci.edu \
--cc=eliz@gnu.org \
--cc=emacs-devel@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).