1 <?xml version="1.0" encoding="UTF-8"?>
\r
2 <!DOCTYPE sect2 SYSTEM "../../../dtd/dblite.dtd">
\r
3 <sect2 id="tsvn-dug-settings-registry">
\r
4 <title>Registry Settings</title>
\r
6 <primary>registry</primary>
\r
9 A few infrequently used settings are available only by editing
\r
10 the registry directly. It goes without saying that you should
\r
11 only edit registry values if you know what you are doing.
\r
15 <term>Configuration</term>
\r
18 You can specify a different location for the Git
\r
19 configuration file using registry location
\r
20 <literal>HKCU\Software\TortoiseGit\ConfigDir</literal>.
\r
21 This will affect all TortoiseGit operations.
\r
26 <term>Cache tray icon</term>
\r
29 To add a cache tray icon for the TSVNCache program,
\r
30 create a <literal>DWORD</literal> key with a value of 1 at
\r
31 <literal>HKCU\Software\TortoiseGit\CacheTrayIcon</literal>.
\r
32 This is really only useful for developers as it allows
\r
33 you to terminate the program gracefully.
\r
41 To show the command line parameters passed from the shell
\r
42 extension to TortoiseProc.exe
\r
43 create a <literal>DWORD</literal> key with a value of 1 at
\r
44 <literal>HKCU\Software\TortoiseGit\Debug</literal>.
\r
49 <term>Owner-Drawn Menus</term>
\r
52 This can be useful if you use something other than the windows explorer
\r
53 or if you get problems with the context menu displaying correctly.
\r
54 create a <literal>DWORD</literal> key with a value of 0 at
\r
55 <literal>HKCU\Software\TortoiseGit\OwnerdrawnMenus</literal>
\r
56 if you don't want TortoiseGit to use owner-draw menu items in the shell
\r
57 context menu. Set this value to 2 if you don't want TortoiseGit to use
\r
58 icons in the context menu at all.
\r
63 <term>Block Overlay Status</term>
\r
66 If you don't want the explorer to update the status overlays while another
\r
67 TortoiseGit command is running (e.g. Update, Commit, ...) then
\r
68 create a <literal>DWORD</literal> key with a value of 1 at
\r
69 <literal>HKCU\Software\TortoiseGit\BlockStatus</literal>.
\r
74 <term>Update Check URL</term>
\r
77 <literal>HKCU\Software\TortoiseGit\UpdateCheckURL</literal>
\r
78 contains the URL from which TortoiseGit tries to download a text file
\r
79 to find out if there are updates available. You can also set this under
\r
80 <literal>HKLM</literal> instead of <literal>HKCU</literal> if you want,
\r
81 but <literal>HKCU</literal> overwrites the setting in <literal>HKLM</literal>.
\r
82 This might be useful for company admins who don't want their users to
\r
83 update TortoiseGit until they approve it.
\r
88 <term>Filenames without extensions in auto-completion list</term>
\r
91 The auto-completion list shown in the commit message editor
\r
92 displays the names of files listed for commit.
\r
93 To also include these names with extensions removed,
\r
94 create a <literal>DWORD</literal> key with a value of 1 at
\r
95 <literal>HKCU\Software\TortoiseGit\AutocompleteRemovesExtensions</literal>.
\r
100 <term>Explorer columns everywhere</term>
\r
103 The extra columns the TortoiseGit adds to the details view
\r
104 in Windows Explorer are normally only active in a working
\r
105 copy. If you want those to be accessible everywhere, not
\r
106 just in working copies, create a <literal>DWORD</literal>
\r
107 key with a value of 1 at
\r
108 <literal>HKCU\Software\TortoiseGit\ColumnsEveryWhere</literal>.
\r
113 <term>Merge log separator</term>
\r
116 When you merge revisions from another branch, and merge tracking
\r
117 information is available, the log messages from the revisions
\r
118 you merge will be collected to make up a commit log message.
\r
119 A pre-defined string is used to separate the individual log
\r
120 messages of the merged revisions. If you prefer, you can create
\r
121 a <literal>SZ</literal> key at
\r
122 <literal>HKCU\Software\TortoiseGit\MergeLogSeparator</literal>
\r
123 containing a separator string of your choice.
\r
128 <term>Always blame changes with TortoiseMerge</term>
\r
131 TortoiseGit allows you to assign external diff viewer.
\r
132 Most such viewers, however, are not suited for change blaming
\r
133 (<xref linkend="tsvn-dug-blame-diffs"/>),
\r
134 so you might wish to fall back to TortoiseMerge in this case.
\r
135 To do so, create a <literal>DWORD</literal> key with a value of 1 at
\r
136 <literal>HKCU\Software\TortoiseGit\DiffBlamesWithTortoiseMerge</literal>.
\r
141 <term>Current revision highlighting for folders in log dialog</term>
\r
144 The log dialog highlights the current working copy revision
\r
145 when the log is shown for a file. To do the same thing for a
\r
146 folder requires a working copy crawl, which can be a slow
\r
147 operation for large working copies.
\r
148 If you want to enable this feature you must create a
\r
149 <literal>DWORD</literal> registry key at
\r
150 <literal>HKCU\Software\TortoiseGit\RecursiveLogRev</literal>.
\r
151 A value of 0 disables the feature (no highlighting for folders),
\r
152 a value of 1 (default) will fetch the status recursively (find the
\r
153 highest revision in the working copy tree), and a value of 2 will
\r
154 check the revision of the selected folder itself, but will
\r
155 not check any child items.
\r
160 <term>Make checkout fail if an item of the same name exists</term>
\r
163 By default, if you checkout a working copy over an existing
\r
164 unversioned folder structure, as you might do after import,
\r
165 then any existing which differ from the repository content
\r
166 will be left unchanged and marked as modified. When you come
\r
167 to commit, it is your local copy which will then be sent back
\r
168 to the repository. Some people would prefer the checkout to
\r
169 fail if the existing content differs, so that if two people
\r
170 add the same file the second person's version does not
\r
171 overwrite the original version by mistake.
\r
172 If you want to force checkouts to fail in this instance you must
\r
173 create a <literal>DWORD</literal> registry key with value 0 at
\r
174 <literal>HKCU\Software\TortoiseGit\AllowUnversionedObstruction</literal>.
\r