i³SP site-lisp Features

I'll get more info on here later. For Now:

Heres a list of the packages provided and what they cover:

• browse-yank.el Bound to M-y, a browser for the kill-ring.
• cygwin-mount.el When enabled, lets emacs on NT understand your cygwin mountpoints.
• decompile.el Open a class file and it'll try to run jad over it so you can see the decompiled source.
• default.el setup code.
• filladapt.el A clever auto-fill that tries to guess your fill prefix.
• folding.el A Folding mode.
• gnuserv.el I can't live without this. Unfortunately, I don't provide the binaries.
• i3sp-folding.el Mouse and menu bindings for the folding mode.
• i3sp-frame-buffers.el Associate buffers with the frame they were opened in. If you kill the frame, it kills all those buffers. Very handy when used in conjunction with gnuserv.
• i3sp-functions.el common code.
• i3sp-group.el comon customisation groups.
• i3sp-jde-gen.el template extensions for JDEE.
• i3sp-key-bindings.el Overiding bindings. See M-x customize-group i3sp-bindings
• i3sp-mouse-bindings.el Overiding bindings. See M-x customize-group i3sp-bindings
• i3sp-ose.el Extensions for C++ programmers who use the OSE Class Library and Tools
• i3sp-overrides.el Overriding variables. See M-x customize-group i3sp-startup-overrides
• i3sp-server-19.el Get emacsserver to throw up buffers in a new frame.
• i3sp-settings.el Customisation settings: See M-x customize-group i3sp-settings
• i3sp-startup.el Startup loading options: See M-x customize-group i3sp-startup
• i3sp-tempo.el Tempo template definitions: See M-x customize-group i3sp-tempo
• java-comment.el An older javadoc adder for java. Superseded by the javadoc templates in JDEE, but still useful for java-mode.
• lib-complete.el Complete names of libraries for M-x load-library
• mailcrypt.el Add PGP handling to mail.
• make-regexp.el Library to build efficient regexps from lists of words.
• mc-pgp.el Mailcrypt support.
• mc-remail.el Mailcrypt support.
• mc-toplev.el Mailcrypt support.
• mqr-replace.el Multi-file query/replace.
• site-start.el support code.
• xfile.el C-S-Mouse1 pops up a menu of files in the current directory.

All of the customisations can be accessed from M-x customize-group i3sp. This also gives a good overview of what the package as a whole does.

JDEE Extensions

When jde and tempo are enabled, a lot of functionality is added to the JDEE.

• a "i3SP Class" menu item is added to the File/JDE New menu. This creates a new java file with a template I provide that adds a few things the standard ones don't. This is equivalent to the "Source file header and class definition" on the Java mode menu and the "header" tempo template.
• Adds "Comment member separator" to the Java mode (inserts a /*--*/ comment line (automatically sized and indented) above the current line).
• Adds "Class Definition" to the Java mode menu. Prompts for class name.
• The above three are also added to the JDE/Code Generation/Templates menu.
• Adds a "JDE Extras" menu to the JDE mode, which has many JDE commands not accessible otherwise.
• C-S-Mouse3 (actually a global binding) pops up a menu of the defined tempo templates for the current buffer (mode specific).
• M-x customize-option i3sp-jde-gen-org-settings allows the user to set up default compile commands, copyright messages (used by the "i3SP Class", the modified jde-gen-boilerplate and the "boilerplate" tempo template), version id specifiers (for use in javadoc) and default imports (used by the "i3SP Class"). These are added on a per-organisation basis, where the "organisation name" (really a regexp) is matched against the package name of the current buffer. Adding an Organisation of "." at the end will act as a default. The standard jde javadoc templates can be modified by the user to use the functions (i3sp-jde-gen-imports, (i3sp-jde-gen-copyright, (i3sp-jde-gen-versionid and (i3sp-jde-gen-compile. The jde-javadoc-author-tag-template and jde-javadoc-version-tag-template are already overridden to use these functions.
• Adds the function i3sp-jde-gen-get-package-statement which works like the jde one but if the jde fails to find a package name, it will look for certain root prefixes in the current directory. These are defined in M-x customize-option i3sp-jde-gen-java-root. Thus the package guessing will work even without a jde project set up. This is used by the "i3SP Class" template.