On May 8, 2008, at 10:18 AM, David Reitter wrote: > On 8 May 2008, at 12:45, Adrian Robert wrote: > >>> Do they really stand in the way of a merge? >> >> For various reasons, yes. Also, as you point out, there is the >> Carbon work, which should also be done beforehand. Both because of >> prevailing opinion on emacs-devel > > Fact is that the Carbon maintainer is not interested in keeping > Carbon alive on the 23 branch. He might be convinced otherwise, > but I don't see how the Carbon port should delay your merge!
As I said, both emacs devs and current users care about drop-in Carbon compatibility. When the merge happens, new users expecting Carbon behavior will result. (If you don't believe Mac users are compiling from Emacs CVS trunk and would try a new port if it appeared there, consult the emacs-devel list (search for "Carbon" "deprecated" "unmaintained" "fix bugs" ;)). I'd rather have it ready than deal with a flood of complaints after merge. >> Could someone who is familiar with the mac-* variables post a summary >> of them? Or even better, a patch to ns-win.el adding aliases for >> corresponding ns-* variables.. > > Their Doc strings are good, but I'm more than happy to explain > missing details. Posting a list of the aliases needed will make this happen a lot sooner. thanks, Adrian ------------------------------------------------------------------------- This SF.net email is sponsored by the 2008 JavaOne(SM) Conference Don't miss this year's exciting event. There's still time to save $100. Use priority code J8TL2D2. http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone _______________________________________________ Emacs-app-dev- mailing list Emacs-app-dev-@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/emacs-app-dev-
