On Fri, Mar 7, 2008 at 8:18 PM, Dan Villiom Podlaski Christiansen <[EMAIL PROTECTED]> wrote:
> BTW, I'd suggest using a Subversion repository (e.g. on SourceForge) > for maintaining Emacs.app until it's merged. That will allow you/us to > keep the CVS metadata present and under version control, making > following trunk trivially easy. This would have been a great idea ;), but now I'm hoping to get this into GNU CVS (on a branch) within a week. As you probably know, the FSF requires copyright assignment papers to > > be filed for > > accepting contributions of more than 15 lines or so. Do you have > > papers on > > file or would you be willing to do so? > > No, yes :-) Should we do so now, or can it wait? I'd rather do so now if possible.. all other contributions are already signed over, so I'd have to either wait to include your config changes, or face questions on the emacs-devel list. ;-) > ... lastfile.c ... > No reason to apply it since I never got it to work anyway. OK, will hold off or put in commented form for now. > Other than that, I hope to get Emacs.app to behave much more like > Carbon Emacs on Mac OS X — hopefully making it a drop-in replacement > eventually This is my and emacs-devs' goal as well, though I (and others I believe) would disagree that the Carbon port is uniformly more pleasant or better integrated. ;-) If the Carbon port stays around, hopefully both can bend a little. > what's already there in Emacs.app is very good indeed. With a bit > of spit and polish, perfection may not be far away… ah, perfection... Adrian ------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ _______________________________________________ Emacs-app-dev- mailing list Emacs-app-dev-@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/emacs-app-dev-