Lior wrote: > Hi Dean, > I disagree with the change you suggested. Since gPHPEdit is an IDE > for PHP, I think it belongs to the "Programming" section and not > "Editors", as it have more capabilities than normal editors.
Not sure on your definition of "normal editor"... ed(1)? From <http://www.gphpedit.org/features.phtml>, gphpedit has: - syntax highlighting (this is a standard editor feature, no?) - syntax checking (perhaps special) - incremental search and goto-line... standard editor stuff - integrated help/popups (perhaps this isn't standard) Take a look at how other maintainers have used the menu sections. The policy manual has this to say about the section: "Programming: debuggers, etc". Other packages adding themselves to this category tend to be interpreters and debuggers (currently I see ocaml, guile, gdb, hugs, tclsh, bsh). The only exception on my system that is primarily an editor is eclipse, but that has integrated source level debugging. Consider that all of gphpedit's features for programming PHP have equivalents in emacs when programming C and elisp. Furthermore, emacs has integrated source level debugging and its own interpreter. Emacs adds its menu entry to the Editors section. The policy manual is ambiguous, but I don't believe you're following the established conventions for categorisation. Lior, can you reference many prior packages that support your view? -- Dean -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
