After giving it much thought I have come to agree with Dave about erlware-mode deprecation. There just isn't any reason for us to have a complete mode any more. The erlang mode has all of our fixes and a lot of additional functionality besides.
That doesn't mean we need to get rid of everything. erlang mode allows us to provide a custom skeletons file, and I think we should do that. Our new style is much more lean and clear then the default, but I think thats all we really need to supply. So I propose that we trim erlware-mode down just to the sinan support and the custom skel file along with instructions on how to use them with erlang-mode. Then we get the benefit of continued development of erlang mode along with the things we actually care about. Thats my proposal in any case. -- You received this message because you are subscribed to the Google Groups "erlware-dev" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/erlware-dev?hl=en.
