On Sun, 2 Nov 2008 16:40:34 +0100 Carsten Bormann <[EMAIL PROTECTED]> wrote: 

CB> One problem that needs to be fixed is that fatal_error_signal/
CB> shut_down_emacs/ns_term_shutdown essentially hides the bugs -- when
CB> Emacs runs into an abort(), this "cleans up" and makes sure there is
CB> no trace of the bug anywhere.  So we never find out what exactly hit
CB> Emacs.  I'd rather see a nice OSX crash report.

Agreed.  With a crash report we'd have something useful to report,
otherwise we're just complaining.

On Sun, 2 Nov 2008 19:13:21 +0100 Peter Dyballa <[EMAIL PROTECTED]> wrote: 

PD> Am 02.11.2008 um 16:40 schrieb Carsten Bormann:

>> Click on "Options" in the menu bar and Emacs is gone.

PD> The yesterday compiled version on PPC and Tiger behaves better. It  
PD> seems only to have problems when invoked with arguments from the  
PD> command line and with key bindings. And yes: when return to Emacs.app  
PD> from another application and click into one window, the cursor stays  
PD> in the other window. No other Cocoa application behaves like Emacs.app!

I'm happy to put work into finding the bugs if I knew how.  The Intel
version I compiled from CVS doesn't have the problem you report with key
bindings and focus.

Ted

-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
Emacs-app-dev- mailing list
Emacs-app-dev-@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/emacs-app-dev-

Reply via email to