Where possible, a login shell will be started. i.e. login scripts ( /etc/profile, ~/profile, ~/.bash_profile, ~/.bash_login, /etc/csh.login, /etc/zprofile, $ZDOTDIR/.zprofile /etc/zlogin $ZDOTDIR/.zlogin ) are run as appropriate for the shell. This does not apply to cmd, which does not have any login scripts.
The title of the window is not set. It will default to whatever the terminal sets it to. This can usually be controlled from the shell by passing an escape sequence to the shell.
Supported terminals: cmd rxvt xterm
Supported shells: ash bash cmd pdksh tcsh zsh passwd
A command ( -iulr ) must be specified before chere does anything. All other options modify how these commands work.
The -i (install) and -u (uninstall) commands are mutually exclusive. The -l and -r commands may be specified in addition to -i or -u , in which case the read/list is done after the install/uninstall.
The context menu may be (un)installed for all users -a , or just yourself -c. To (un)install for all users, you will require appropriate access rights. i.e. you need to have Administrator rights.
If the -i flag is passed without specifying a shell, the shell specified in /etc/passwd for the current user is added. If term is not specified, cmd is used.
If the -u flag is passed without specifying a shell, all installed context menus will be uninstalled. If -a or -c is also specified, only the context menus for the specified users are uninstalled. Otherwise the context menus are removed for all users and the current user.
It is not possible to uninstall a context menu for a user who is not the current user.
The passwd shell tries to determine your preferred shell at runtime from your /etc/passwd entry. This is most useful on multi-user systems.
By default, registry entries are added so that the context menus can be removed using the Add Remove Programs utility in the Windows Control Panel. The -m option prevents this. Note that this uninstall option invokes chere. When installing for the current user, chere will attempt to set an uninstall entry. If the user does not have appropriate rights to add keys to the HKLM hive, then the uninstall will not be present. Using -m will avoid the error message.
The -1 and -2 options select how shell is started. The original method of registry one-liners is succint, but does not work on network shares or with ash and tcsh. It also results in an extra sh process when the passwd shell is used. These issues should not be present when invoked via xhere. xhere requires your login script to check the environment variable CHERE_INVOKING , and avoid changing to your HOME directory if it is present.
The -p option will print the regtool commands to stdout for inspection instead of executing them.
The -l command lists the currently installed shell here context menus.
The -r command lists the commands currently in the registry associated with all possible context menus.
The -f option forces chere to overwrite existing commands even if shell can't be found
Install tcsh, for all users using rxvt as the terminal, then list what is installed.
If you really do like cmd you can still use it as a shell in rxvt or xterm.
Use ~/.Xdefaults to set terminal resources (colour, font etc)
http://biocycle.atmos.colostate.edu/~johnk/Xterm-Title.html has information on setting up Dynamic titles from various shells