From: merlyn@stonehenge.com (Randal L. Schwartz)
To: emacs-devel@gnu.org
Subject: Re: carbon build hangs on startup
Date: Sun, 07 Oct 2007 08:05:51 -0700 [thread overview]
Message-ID: <864ph32cds.fsf@blue.stonehenge.com> (raw)
In-Reply-To: 200710062009.l96K9uNb021892@oogie-boogie.ics.uci.edu
>>>>> "Dan" == Dan Nicolaescu <dann@ics.uci.edu> writes:
Dan> The Carbon port on CVS trunk has been abandoned by its maintainers and
Dan> it is known to be broken. If you don't intend to work on fixing it,
Dan> it is better to avoid it. The X11 port should still work ...
For some meaning of "work". I don't fire up X11 on my mac more than once
every month or two. But I use Carbon Emacs every day... it's essential in my
workflow.
What kind of skills are needed to make Carbon Emacs "work" again? Maybe I can
go to the OSX mailing lists and plea for someone to pick up the cause. But I
need to know what skills a person will need. Can someone at least outline
that?
--
Randal L. Schwartz - Stonehenge Consulting Services, Inc. - +1 503 777 0095
<merlyn@stonehenge.com> <URL:http://www.stonehenge.com/merlyn/>
Perl/Unix/security consulting, Technical writing, Comedy, etc. etc.
See PerlTraining.Stonehenge.com for onsite and open-enrollment Perl training!
next prev parent reply other threads:[~2007-10-07 15:05 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-06 16:22 carbon build hangs on startup Cyrus Harmon
2007-10-06 20:09 ` Dan Nicolaescu
2007-10-07 15:05 ` Randal L. Schwartz [this message]
2007-10-07 15:36 ` Dan Nicolaescu
2007-10-07 15:56 ` Jason Rumney
2007-10-07 16:02 ` Dan Nicolaescu
2007-10-08 1:27 ` YAMAMOTO Mitsuharu
2007-10-08 2:56 ` Randal L. Schwartz
2007-10-08 3:59 ` YAMAMOTO Mitsuharu
2007-10-11 4:08 ` Cyrus Harmon
2007-10-11 4:31 ` YAMAMOTO Mitsuharu
2007-10-11 14:52 ` Randal L. Schwartz
2007-10-13 17:02 ` Dan Nicolaescu
2007-10-15 18:24 ` Randal L. Schwartz
2007-10-15 18:53 ` Carbon port input problems: keyboard events linger (was: carbon build hangs on startup) Ted Zlatanov
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=864ph32cds.fsf@blue.stonehenge.com \
--to=merlyn@stonehenge.com \
--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).