Eric? I also have another suggestion. We should remove the
%%---- lines from infront of functions, either both or the one at the bottom. Including the spec below that line seems odd to me. Thoughts? On Sat, Oct 9, 2010 at 6:29 PM, Dave Peticolas <[email protected]> wrote: > That's cool, but it will need a new maintainer :) I'm done with > Emacs hacking for a while and I'm using the version from core > now. > > On Sat, Oct 9, 2010 at 4:18 PM, Martin Logan <[email protected]> wrote: >> I like the idea of having the competing mode actually. A place where >> new features are experimented with. The Erlang mode is naturally a >> more conservative project. >> >> On Sat, Oct 9, 2010 at 6:09 PM, Dave Peticolas <[email protected]> wrote: >>> Sounds good, except why not just submit patches directly to core? >>> >>> The erlang mode has now got patches from outside of the erlware-mode >>> so they have already diverged. >>> >>> dave >>> >>> On Sat, Oct 9, 2010 at 3:24 PM, Eric Merritt <[email protected]> wrote: >>>> Guys, >>>> >>>> I am going to propose a few changes to erlware-mode (yes I know its going >>>> away but changes seem to be feeding erlang mode). >>>> >>>> >>>> 1. Lets change the generated documentation specs to the modern spec >>>> syntax/placement >>>> 2. Lets drop the redundant documentation in on the various gen_* >>>> skeletons. I am coming to the conclusion that its more clutter then help. >>>> We should encourage people to document their public api functions. >>>> >>>> 3. I would like to add place holders for a types area and generate >>>> -export_type to encourage people to document and export their public types. >>>> >>>> These changes are pretty simple overall, but should increase the usability >>>> quite a bit. I am willing to create the patches when I get time. >>>> >>>> Comments, feedback? >>>> >>>> Eric >>>> >>>> -- >>>> 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. >>>> >>>> >>> >>> -- >>> 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. >>> >>> >> >> -- >> 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. >> >> > > -- > 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. > > -- 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.
