Re: Re: 'Fatal error (6).Abort' (with fix)
Steven Tamm <[email protected]> Thu, 8 Aug 2002 22:59:27 -0700
| Newsgroups | gmane.emacs.macintosh.devel |
|---|---|
| Message-ID | <[email protected]> |
--Apple-Mail-1--974039523 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=US-ASCII; format=flowed Andrew - If /usr/local/bin/emacs is a shell forward to Emacs.app/Contents/MacOS/Emacs, then I have no idea what the problem is. On my machine (which may be anomalous), emacs behaves exactly as intended wrt the -nw flag if you start it from a bundle. If you start it from the command-line without -nw, it also works, except that you have to hit return once to get the emacs executable going. So the only thing this patch seems to fix is that you don't have to hit return. That, however, is beyond useful. When 10.2 comes around and the multithreaded UI can be used, a call to add_keyboard_wait_descriptor would fix the select problem that this patch concerns. My only comments about the patch would be: 1. MakeMeTheFrontProcess would be nice to have as a lisp function. 2. mac_do_receive_drag should call MakeMeTheFrontProcess instead of duplicating the code. In any case, I still think my patch is a good idea to prevent a random Emacs executable from trying to use Carbon if it is outside a bundle (and thus can't connect to the window server). But if /usr/local/bin/emacs is going to be a forward to Emacs.app... which will always be in a bundle, then it's not of much use. -Steven P.S. Is the ADC Developer Mailing worth the $199? It seems that for the extra $70 over purchasing jaguar, it may make sense to get a year of updates on disc. --Apple-Mail-1--974039523 Content-Transfer-Encoding: 7bit Content-Type: text/enriched; charset=US-ASCII Andrew - If /usr/local/bin/emacs is a shell forward to Emacs.app/Contents/MacOS/Emacs, then I have no idea what the problem is. On my machine (which may be anomalous), emacs behaves exactly as intended wrt the -nw flag if you start it from a bundle. If you start it from the command-line without -nw, it also works, except that you have to hit return once to get the emacs executable going. So the only thing this patch seems to fix is that you don't have to hit return. That, however, is beyond useful. When 10.2 comes around and the multithreaded UI can be used, a call to add_keyboard_wait_descriptor would fix the select problem that this patch concerns. My only comments about the patch would be: 1. <color><param>0000,0000,0000</param> MakeMeTheFrontProcess would be nice to have as a lisp function. </color>2. mac_do_receive_drag should call MakeMeTheFrontProcess instead of duplicating the code. In any case, I still think my patch is a good idea to prevent a random Emacs executable from trying to use Carbon if it is outside a bundle (and thus can't connect to the window server). But if /usr/local/bin/emacs is going to be a forward to Emacs.app... which will always be in a bundle, then it's not of much use. -Steven P.S. Is the ADC Developer Mailing worth the $199? It seems that for the extra $70 over purchasing jaguar, it may make sense to get a year of updates on disc. --Apple-Mail-1--974039523-- ------------------------------------------------------- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf