From: Dave Carlton <davec@apple.com>
Subject: Re: Do we need legal papers
Date: Wed, 5 Nov 2003 09:34:07 -0800 [thread overview]
Message-ID: <4241666F-0FB6-11D8-8400-000393D00076@apple.com> (raw)
In-Reply-To: <m31xsnoeek.fsf@kfs-l.imdomain.dk>
[-- Attachment #1.1: Type: text/plain, Size: 742 bytes --]
Andrew, I too would ask that you reconsider. I am a recent convert to
EMACS and as you can see I only use a Macintosh and OSX. I would gladly
take your place or help you out but I am just a neophyte when it comes
to C and Lisp (I work in Forth and Open Firmware :). While I like the X
version the problems of cut and paste (among others) between the OSX
and X versions makes it too cumbersome for me to use.
So please please stay on board, I was so much looking forward to 21.4!
On Nov 04, 2003, at 16:19, Kim F. Storm wrote:
> Andrew Choi <akochoi@shaw.ca> writes:
>
>>
>> Perhaps it is best if I'm relieved from being the Mac maintainer. I
>> program for the love of programming and not for any other reasons.
---
davec@apple.com
[-- Attachment #1.2: Type: text/enriched, Size: 829 bytes --]
Andrew, I too would ask that you reconsider. I am a recent convert to
EMACS and as you can see I only use a Macintosh and OSX. I would
gladly take your place or help you out but I am just a neophyte when
it comes to C and Lisp (I work in Forth and Open Firmware :). While I
like the X version the problems of cut and paste (among others)
between the OSX and X versions makes it too cumbersome for me to use.
So please please stay on board, I was so much looking forward to 21.4!
On Nov 04, 2003, at 16:19, Kim F. Storm wrote:
<excerpt>Andrew Choi <<akochoi@shaw.ca> writes:
<excerpt>
Perhaps it is best if I'm relieved from being the Mac maintainer. I
program for the love of programming and not for any other reasons.
</excerpt></excerpt><fontfamily><param>Lucida Grande</param>---
davec@apple.com
</fontfamily>
[-- Attachment #2: Type: text/plain, Size: 141 bytes --]
_______________________________________________
Emacs-devel mailing list
Emacs-devel@gnu.org
http://mail.gnu.org/mailman/listinfo/emacs-devel
next prev parent reply other threads:[~2003-11-05 17:34 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-12 14:34 patch for unexmacosx.c: supporting non-prebound dynamic library Nozomu Ando
2003-10-31 20:08 ` Andrew Choi
2003-11-01 23:51 ` Do we need legal papers [was: patch for unexmacosx.c: supporting non-prebound dynamic library] Kim F. Storm
2003-11-02 1:21 ` Andrew Choi
2003-11-02 23:18 ` Richard Stallman
2003-11-02 23:44 ` Do we need legal papers Andrew Choi
2003-11-04 14:25 ` Richard Stallman
2003-11-04 15:44 ` Andrew Choi
2003-11-04 16:00 ` David Kastrup
2003-11-05 0:19 ` Kim F. Storm
2003-11-05 17:34 ` Dave Carlton [this message]
2003-11-05 18:58 ` Joseph C. Slater
2003-11-05 23:32 ` Richard Stallman
2003-11-06 16:24 ` Andrew Choi
2003-11-07 9:03 ` Sébastien Kirche
2003-11-09 23:02 ` Kim F. Storm
2003-11-02 23:18 ` Do we need legal papers [was: patch for unexmacosx.c: supporting non-prebound dynamic library] Richard Stallman
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=4241666F-0FB6-11D8-8400-000393D00076@apple.com \
--to=davec@apple.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.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).