On 6 Mar 2008, at 16:21, Adrian Robert wrote:
Thanks, I've had a chance to look through this. It appears you've updated to the TRUNK. ("HEAD" is the latest state of a particular branch in CVS, trunkor otherwise.)
Really? I thought CVS HEAD was the equivalent of Subversion trunk. There you go; you learn something new every day. Actually, that was the point of my entire quest[1] ;-)
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.
I've incorporated some of your smaller changes to clean up the source code. However, I'd also like to use your improvements to the configure process. 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 onfile or would you be willing to do so?
No, yes :-) Should we do so now, or can it wait? For me, it would be really nice if the FSF accepted S/MIME signatures. I have an official, Danish digital ID, and I believe digitally signed emails are legally binding under current Danish law.
(I've always found the need for copyright assignment rather peculiar, but that's just the way it is…)
Also, quick question, what is the reason behind the change to lastfile.c?
I tried to compile Emacs with the Apple GCC 4.2 preview available from the Apple Developer Connection, but it failed in the unexec() stage. (Hence the check for __APPLE_CC__ being greater than 5500.) It mitigated the error somewhat, only to fail somewhere else. No reason to apply it since I never got it to work anyway.
Someday, I'll try to compile Emacs with LLVM and llvm-gcc 4.2 to see if it speeds things up. That may require similar patches, but there's no way to know until someone has tried it. The Apple GCC 4.2 preview is fairly old and buggy, and llvm-gcc 4.2 is based on an updated version of it, but I haven't been able to find the non-LLVM version anywhere.
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 — and in general just to make it more pleasant to use on Mac OS X. BTW, the new Emacs icons[2] suite it really well :-) Anyway, what's already there in Emacs.app is very good indeed. With a bit of spit and polish, perfection may not be far away…
(Cc'ed to the Emacs.app list; who knows, I may have written something clever.)
-- Dan Villiom Podlaski Christiansen stud.scient., [EMAIL PROTECTED] [1] Updating, not learning.[2] Discussion on emacs-devel: <http://lists.gnu.org/archive/html/emacs-devel/2008-03/msg00127.html >
smime.p7s
Description: S/MIME cryptographic signature
------------------------------------------------------------------------- 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-
