Begin/end style - Specify the brace style to be used for Syntax Indent and Syntax Expansion. The hyperlink indicates if Adaptive Formatting is on or off for this setting. After specifying the brace style, choose from the following options:

Indent first level of code - Specifies whether Syntax Indent should indent the cursor after declarations such as functions.

Use continuation indent on function parameters - Determines whether function parameters should always use the continuation indent.

By default, SlickEdit Core formats multi-line function parameters as follows:

myLongMethodName(firstarg,
secondarg,
thirdarg
);
myLongMethodName(
    firstarg,
    new ActionListener() {
        public void actionPerformed(ActionEvent e) {
            createdButtonFired(buttonIndex);
        }
    },
    thirdarg
    );
myLongMethodName(new ActionListener() {   // special case anonymous class first argument
        public void actionPerformed(ActionEvent e) {
            createdButtonFired(buttonIndex);
        }
    },
    secondarg,
    thirdarg
    );
myLongMethodName(
    secondarg,
    new ActionListener() {
        public void actionPerformed(ActionEvent e) {
            createdButtonFired(buttonIndex);
        }
    },
    thirdarg
    );

If Use continuation indent on function parameters is selected, the format will change as follows:

myLongMethodName(firstarg,
    secondarg,
    thirdarg
    );
myLongMethodName(
    firstarg,
    new ActionListener() {
        public void actionPerformed(ActionEvent e) {
            createdButtonFired(buttonIndex);
        }
    },
    thirdarg
    );
myLongMethodName(new ActionListener() {   // special case anonymous class first argument
        public void actionPerformed(ActionEvent e) {
            createdButtonFired(buttonIndex);
        }
    },
    secondarg,
    thirdarg
    );

Indent CASE from SWITCH - When checked, Syntax Expansion places the case statement indented from the switch statement column. The hyperlink indicates if Adaptive Formatting is on or off for this setting.

No space before parenthesis - Determines whether a space is placed between a keyword such as if, for, or while and the open paren when syntax expansion occurs. Example: (if( or if () The hyperlink indicates if Adaptive Formatting is on or off for this setting.

Insert padding between parentheses - When checked, a space is placed after the open paren, and before the close paren, providing padding for the enclosed text. For example, if () becomes if ( ). The hyperlink indicates if Adaptive Formatting is on or off for this setting.

From the main menu, click Format → Imports → Options

Select Format → Imports → Options from the right-click context menu in the editor window.

Use the jrefactor_organize_imports_options command.

Package explicit import limit before using wildcard(.*) - If more than this number of classes are explicitly imported from the same package in one file, the imports will be replaced with a single wildcard import.

Add blank line between groups of imports - Organize Imports will group imports by package name or top-level package name. Select this option to force Organize Imports to add a blank line between these groups instead of having just one flat list of imports.

Automatically add import during code help for Java - If selected, SlickEdit® Core will attempt to automatically add imports as you edit Java code.

Automatically add import during code help for JSP - If selected, SlickEdit Core will attempt to automatically add imports as you edit Java code embedded in HTML. JSP imports are added using the following notation: <%@ page import="java.util.Vector"%>.

Package sort order - This list specifies the order in which package groups are sorted. Use the Ellipses (...) button to add a new package. Use the Up and Down arrow buttons to move items. Use the X button to delete the currently selected package from the list.

Align parameter comments to longest parameter name - If checked, the parameters are aligned to the length of the longest parameter name. If the parameter name length is less than the minimum length, the minimum length is used. If the parameter length is longer than the maximum parameter length, the description for the parameter will start on the next line.

Align exception comments to longest exception name - If checked, the exceptions are aligned to the length of the longest exception name. If the exception name length is less than the minimum length, the minimum length is used. If the exception length is longer than the maximum exception length, the description of the parameter will start on the next line.

Align return comments - Indicates whether @return comments should be aligned to the first line of comment text. No alignment is performed if tags which are indent-sensitive such as the <pre> tag are used.

Align deprecated comments - Indicates whether @return comments should be aligned to the first line of comment text. No alignment is performed if tags which are indent-sensitive such as the <pre> tag are used.

Add blank line after parameter comment - If checked, a blank line is added if a tag follows an @param tag.

Add blank line after parameter comment group - If checked, a blank line is added if a tag follows an @param group.

Add blank line after return comment - If checked, a blank line is added if a tag follows the @return tag.

Add blank line after description - If checked, a blank line is added between the description and the first @ tag. This option is ignored if the description contains a custom or unsupported @ tag.

Add blank line after example - If checked, a blank line is added if a tag follows the @example tag.