2 .TH chere 1 "Sep 2007" "User Commands"
4 chere \- manage Shell Here context menu items
26 combination to the folder context menu. This allows you to right click a folder in Windows Explorer and open
30 Where possible, a login shell will be started. i.e. login scripts (
31 .B /etc/profile, ~/profile, ~/.bash_profile, ~/.bash_login, /etc/csh.login, /etc/zprofile, $ZDOTDIR/.zprofile /etc/zlogin $ZDOTDIR/.zlogin
32 ) are run as appropriate for the shell. This does not apply to cmd, which does not have any login scripts.
34 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.
44 Refresh eXisting context menu items
47 List currently installed Shell Here
52 registry entries to stdout
55 Operation affects all users
58 Operation affects current user only
61 Be Nice and provide Control Panel uninstall option (Default)
64 Minimal, no Control Panel uninstall
69 commands to stdout rather than running them
72 Force write (overwrite existing, ignore missing files)
75 Start shell using registry one-liners. This doesn\'t work with ash, tcsh or network shares.
80 script. Relies on windows to change directory, and login scripts avoiding doing a cd
84 Specifies the display to use if xterm is specified as the shell. Defaults to :0. If set to env, then the environment variable
86 is read when the context menu item is selected.
91 to the terminal startup command. If more than one option is specified, they should all be contained within a single set of quotes.
97 as the context menu text.
110 .B ash bash cmd pdksh tcsh zsh passwd
116 ) must be specified before
118 does anything. All other options modify how these commands work.
124 (uninstall) commands are mutually exclusive. The
128 commands may be specified in addition to
134 , in which case the read/list is done after the install/uninstall/refresh.
137 The context menu may be (un)installed for all users
141 To (un)install for all users, you will require appropriate access rights. i.e. you need to have Administrator rights.
144 If the -i flag is passed without specifying a shell, the shell specified in
146 for the current user is added. If
155 flag is passed without specifying a shell, all installed context menus will be uninstalled. If
159 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.
162 It is not possible to uninstall a context menu for a user who is not the current user.
167 shell tries to determine your preferred shell at runtime from your
169 entry. This is most useful on multi-user systems.
172 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
174 option prevents this. Note that this uninstall option invokes
176 When installing for the current user,
178 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
180 will avoid the error message.
189 is started. The original method (
191 ) of registry one-liners is succint, but does not work on network shares or with
194 .B tcsh. Nor will it cope with paths containing apostrophes.
195 It also results in an extra
199 shell is used. These issues should not be present when invoked via
205 requires your login script to check the environment variable
207 , and avoid changing to your
209 directory if it is present. The login script should unset the variable after it sees it, so that subsequent child logins are unaffected.
213 you can specify a keyboard shortcut for the context menu by prefixing the appropriate letter in the text with an ampersand (&).
217 ) updates all currently installed context menu items. However, it does not preserve custom user arguments and menu entry text. If you have previously specified these with
222 Freshening does support the use of
224 in the same invocation. It will abort if you attempt to specify the menu text entry with
228 Several options are present to aid debugging.
233 option will print the
237 for inspection instead of executing them.
242 command lists the currently installed shell here context menus.
247 command lists the commands currently in the registry associated with all possible context menus.
254 to overwrite existing commands even if
260 \&./chere -il -t rxvt -s tcsh
266 as the terminal, then list what is installed.
269 If you have an old or custom startup script, the shell may not enter the desired directory. The login script modifications described above are provided in the default startup scripts; the cygwin setup program attempts to merge updates in these scripts to your local login scripts, but this may not work. The default startup scripts can be found at:
271 .B /etc/defaults/etc/profile
272 (provided by base-files, used by
278 .B /usr/share/doc/zsh-x.x.x/StartupFiles/zprofile
281 .B /usr/share/doc/tcsh/...
282 (not currently provided)
287 as a terminal because you don't want to install
293 If you really do like
295 you can still use it as a shell in
302 to set terminal resources (colour, font etc). This even works for rxvt in non-X11 mode.
306 to set the terminals -name option,
308 to distinguish the context menu entries, and specify separate terminal resources for each of the context menu entries in
311 .B http://biocycle.atmos.colostate.edu/~johnk/Xterm-Title.html
312 has information on setting up Dynamic titles from various shells
315 .B CHERE_INVOKING DISPLAY
318 .B /etc/passwd /bin/xhere /etc/profile ~/profile ~/.bash_profile ~/.bash_login /etc/csh.login /etc/zprofile $ZDOTDIR/.zprofile /etc/zlogin $ZDOTDIR/.zlogin
321 Written by Dave Kilroy <kilroyd@gmail.com>
324 Report bugs to <cygwin@cygwin.com>, following the directions in http://cygwin.com/problems.html. Also attach verbatim output of the command
328 This script is in the public domain.
331 .B ash bash pdksh tcsh zsh rxvt xterm regtool