[OS X Emacs] dialog box issues - known problems?

[David Reitter]

On Aug 11, 2009, at 4:42 PM, Michael Gilbert wrote:
>> The best way to help with the development is to figure out why (in  
>> the code!) bugs occur and then describe the solution, either  
>> verbally or by writing a patch.  Reporting bugs with all  
>> information needed to reproduce is a minimal first step, but it is  
>> not very effective when there are not enough people actually  
>> dealing with the reports.  So: debug and write more code.
>
> I would love to contribute code, but I'm neither a Cocoa/Objective C  
> nor Lisp developer.

I wasn't, either, in early 2004.  Emacs Lisp seemed liked a strange  
beast, and I mostly copied and pasted other people's (buggy) code.   
It's a fun language though!  The same goes for Objective C.   
Different, but still fun to learn.

Both Lisp and ObjC are wide-spread in two different communities, and  
learning them is worthwhile professionally for many people.

> I do know how to write up useful bug reports, but it sounds like  
> you're telling me that I really shouldn't bother unless I can fix  
> them myself. Am I hearing you right?

By all means: file good bug reports that are reproducible (with  
minimal work).  Just don't expect fixes to happen soon.

Thanks for being considerate and willing to help!


-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 2193 bytes
Desc: not available
URL: <http://email.esm.psu.edu/pipermail/macosx-emacs/attachments/20090811/afe1c718/attachment.p7s>