$RUSH_DIR/etc/.irushrc

When the user runs irush, the $RUSH_DIR/etc/.irushrc file is loaded first, then the user's own ~/.irushrc file is loaded, overriding the defaults.

This lets the administrator be able to have some control over the defaults in irush.

Currently, the admin can define the default entries that will appear in the IRUSH 'Hotkeys' menu.

Use empirical techniques to become familiar with this file's format, eg:

1. Leave the $RUSH_DIR/etc/.irushrc file empty.
2. Run 'irush'.
3. Create some new Hotkey commands using 'Hotkey -> Edit'.
4. Quit irush.
5. Study the contents of your ~/.irushrc file.

Then paste excerpts from your ~/.irushrc file into the global $RUSH_DIR/etc/.irushrc file, so that all users get these as defaults.

You can release the global $RUSH_DIR/etc/.irushrc to the entire network using rushadmin(1), or 'rush -push .irushrc +any'.

Caveats

Environment variables can be specified in the 'command' lines in .irushrc files. The variables will be expanded at runtime.

The global $RUSH_DIR/etc/.irushrc file can be managed and distributed with the rushadmin(1) or 'rush -push' commands.

The user's ~/.irushrc file will override global entries under these conditions:

• The user defines a command that uses the same function key as a global one.

• If the user picks a 'Name' that is the same as a global one.

The contents of the global .irushrc file is never saved back into the user's ~/.irushrc file, so the sysadmin can be free to make changes to the global file without affecting the user's own settings.