1 <?xml version="1.0" encoding="UTF-8"?>
\r
2 <!DOCTYPE sect2 SYSTEM "../../../dtd/dblite.dtd">
\r
3 <sect2 id="tgit-dug-settings-main">
\r
4 <?dbhh topicname="HIDD_SETTINGSMAIN"?>
\r
5 <?dbhh topicname="HIDD_FIRSTSTARTWIZARD_GIT"?>
\r
6 <title>General Settings</title>
\r
8 <primary>git.exe path</primary>
\r
11 <primary>Cygwin Git</primary>
\r
14 <primary>MSYS2 Git</primary>
\r
17 <primary>Extern DLL Path</primary>
\r
20 <primary>Extra PATH</primary>
\r
23 <figure id="tgit-dug-settings-dia-main">
\r
24 <title>The Settings Dialog, General Page</title>
\r
25 <graphic fileref="../images/SettingsMain.png"/>
\r
27 This dialog allows you to specify your preferred language,
\r
28 and the Git-specific settings.
\r
32 <term>Language</term>
\r
35 Selects your user interface language.
\r
36 What else did you expect? Only languages of installed language packs are listed.
\r
37 You can download language packs on the <ulink url="https://tortoisegit.org/download">TortoiseGit download page</ulink>
\r
38 or <ulink url="https://tortoisegit.org/translate">help translating</ulink>.
\r
43 <term>Automatically check for newer versions every week</term>
\r
46 If checked, TortoiseGit will contact its download site once a week
\r
47 to see if there is a newer version of the program available.
\r
48 Use <guibutton>Check now</guibutton> if you want an answer
\r
49 right away. The new version will not be downloaded; you
\r
50 simply receive an information dialog telling you that the
\r
51 new version is available.
\r
56 <term>Create Library</term>
\r
59 On Windows 7 you can create a Library in which to group working copies
\r
60 which are scattered in various places on your system.
\r
65 <term>Git.exe Path</term>
\r
68 TortoiseGit needs to know which <filename>git.exe</filename> to use for it's operations. Enter the full path to <filename>git.exe</filename> here.
\r
73 <filename>git.exe</filename> must not be marked to be run in elevated mode (i.e. <guilabel>Run as administrator</guilabel> or run in any compatibility mode).
\r
78 There is a <ulink url="https://github.com/msysgit/msysgit/issues/103"><citetitle>known issue in msysGit/Git for Windows</citetitle></ulink>:
\r
79 Git for Windows provides two <filename>git.exe</filename>-files (one in a folder named <filename>bin</filename> and one in a folder named <filename>cmd</filename>).
\r
80 Make sure <guilabel>Git.exe Path</guilabel> points to the <filename>bin</filename>-folder within the Git for Windows installation folder.
\r
85 If you don't use Git for Windows, please see the sections for "Cygwin Git" and "MSYS2 Git" below as special settings are required here.
\r
88 As a general note: There is <ulink url="https://tortoisegit.org/support/faq/#nongitforwindowsunsupported">no official support</ulink> for Cygwin or MSYS2 Git in TortoiseGit. The TortoiseGit developers only use Git for Windows. Bug reports, however, are welcome.
\r
95 In order to debug problems you can open TortoiseGit advanced settings and set <literal>DebugOutputString</literal> to "true" (<xref linkend="tgit-dug-settings-registry"/>). Start capturing the debug output.
\r
96 Then start TortoiseGit settings, click on <guilabel>Check now</guilabel> and observe the debug messages.
\r
103 <term>Extra PATH</term>
\r
106 If your git installation needs an extra entry in the PATH environment variable,
\r
107 you can enter it here and it will get added to the PATH environment variable automatically when TortoiseGit starts.
\r
110 This is especially needed if you installed the developer version of msysGit ("Full installer (self-contained) if you want to hack on Git" with the filename <filename>msysGit-fullinstall-*.exe</filename>),
\r
111 in this case it is necessary that the <filename>[MSYSGIT-INSTALL-PATH]\mingw\bin</filename>-folder is on the path (i.e. entered in the <guilabel>Extra PATH</guilabel> textbox) in order to execute <filename>git.exe</filename>.
\r
114 Often you can see if you need this when you start <filename>git.exe</filename> in <filename>[MSYSGIT-INSTALL-PATH]\mingw\bin</filename>-folder and you get a message box saying that a DLL is missing.
\r
119 <term>Cygwin Git</term>
\r
122 As noted above: There is <ulink url="https://tortoisegit.org/support/faq/#nongitforwindowsunsupported">no official support</ulink> for Cygwin Git in TortoiseGit (do not enable this for the "Git for Windows" package!). The TortoiseGit developers only use Git for Windows. Bug reports, however, are welcome. If you really want to use it, here are the steps you have to perform:
\r
125 1) Select the <filename>[CYGWIN-INSTALL-PATH]\bin</filename>-folder as <filename>git.exe</filename> folder.
\r
128 2) Configure the <literal>HOME</literal> environment variable in Windows, so that Cygwin and TortoiseGit are using the same home directory and global git-config. Use the normal Windows notation here (e.g., "C:\Users\USERNAME"). By default, TortoiseGit uses the Windows home directory which is normally located under <filename>c:\Users</filename> and Cygwin uses its own home directories which are located under <filename>[CYGWIN-INSTALL-PATH]\home</filename>.
\r
131 3) Configure AutoCrLf, this is necessary as TortoiseGit and Cygwin Git have different defaults. The default in Cygwin Git is <literal>true</literal>.
\r
134 4) Go to TortoiseGit <xref linkend="tgit-dug-settings-registry"/> and set <literal>CygwinHack</literal> to <literal>true</literal> in order to activate Cygwin workarounds.
\r
142 <term>MSYS2 Git</term>
\r
145 As noted above: There is <ulink url="https://tortoisegit.org/support/faq/#nongitforwindowsunsupported">no official support</ulink> for MSYS2 Git in TortoiseGit (do not enable this for the "Git for Windows" package!). The TortoiseGit developers only use Git for Windows. Bug reports, however, are welcome. If you really want to use it, here are the steps you have to perform:
\r
148 1) Select the <filename>[MSYS2-INSTALL-PATH]\usr\bin</filename>-folder as <filename>git.exe</filename> folder.
\r
151 2) Configure the <literal>HOME</literal> environment variable in Windows, so that MSYS2 and TortoiseGit are using the same home directory and global git-config. Use the normal Windows notation here (e.g., <filename>C:\Users\USERNAME</filename>). By default, TortoiseGit uses the Windows home directory which is normally located under <filename>c:\Users</filename> and MSYS2 uses its own home directories which are located under <filename>[MSYS2-INSTALL-PATH]\home</filename>.
\r
154 3) Configure AutoCrLf, this is necessary as TortoiseGit and MSYS2 Git might have different defaults.
\r
157 4) Go to TortoiseGit <xref linkend="tgit-dug-settings-registry"/> and set <literal>Msys2Hack</literal> to <literal>true</literal> in order to activate MSYS2 workarounds.
\r
165 <sect3 id="tgit-dug-settings-look-feel">
\r
166 <title>Context Menu Settings</title>
\r
167 <?dbhh topicname="HIDD_SETTINGSLOOKANDFEEL"?>
\r
169 <figure id="tgit-dug-settings-dia-context">
\r
170 <title>The Settings Dialog, Context Menu Page</title>
\r
171 <graphic fileref="../images/SettingsContext.png"/>
\r
173 This page allows you to specify which of the TortoiseGit context menu
\r
174 entries will show up in the main context menu (on the first level),
\r
175 and which entries will appear
\r
176 in the TortoiseGit submenu. By default most items are unchecked and
\r
177 appear in the submenu.
\r
178 If you want to hide specific entries, see <xref linkend="tgit-dug-settings-look-feel-extended"/>.
\r
181 Most of the time, you won't need the TortoiseGit context menu, apart
\r
182 for folders that are under version control by Git. For non-
\r
183 versioned folders, you only really need the context menu when you
\r
184 want to do a checkout. If you check the option <guilabel>Hide menus
\r
185 for unversioned paths</guilabel>, TortoiseGit will not add its entries
\r
186 to the context menu for unversioned folders. But the entries are
\r
187 added for all items and paths in a versioned folder. And you can
\r
188 get the entries back for unversioned folders by holding the
\r
189 <keycap>Shift</keycap> key down while showing the context menu.
\r
192 If there are some paths on your computer where you just don't want
\r
193 TortoiseGit's context menu to appear at all, you can list them in
\r
194 the box at the bottom.
\r
195 A trailing <literal>*</literal> is treated as a wildcard character matching
\r
196 any characters. Additionally, a path ending with <literal>\</literal> will
\r
197 match a folder and all its files and subfolders.
\r
198 <emphasis>Please note:</emphasis> <literal>*</literal> cannot be used as a wildcard
\r
199 character within a path.
\r
202 If you right click and drag folder/file in Windows Explorer,
\r
203 a context menu will be shown when you drop. It provides some TortoiseGit actions.
\r
204 You can uncheck <guibutton>Enable drag context menu</guibutton>
\r
205 to prevent from carelessly clicking the TortoiseGit actions.
\r
208 There's a different settings page for the Windows 11 context menu.
\r
209 That page also has a button to register the TortoiseGit entries in
\r
210 the context menu. You only have to do this if TortoiseGit was installed
\r
211 as a different user.
\r
215 <sect3 id="tgit-dug-settings-look-feel-extended">
\r
216 <title>Context Menu 2 Settings</title>
\r
217 <?dbhh topicname="HIDD_SETTINGSEXTMENU"?>
\r
219 <figure id="tgit-dug-settings-ext-menu">
\r
220 <title>The Settings Dialog, Context Menu 2</title>
\r
221 <graphic fileref="../images/SettingsExtendMenu.png"/>
\r
223 This page allows you to specify which of the TortoiseGit context menu
\r
224 entries will be hidden by default. Selected item will only be visible when you hold the <keycap>Shift</keycap>
\r
225 key on <action>right click</action> (this is the so-called extended context menu, please don't mix this with the TortoiseGit submenu, which is also configurable (cf. <xref linkend="tgit-dug-settings-look-feel"/>)).
\r
226 This configuration helps you to reduce the number of context menu entries according to your needs.
\r
230 <sect3 id="tgit-dug-settings-dialogs">
\r
231 <title>TortoiseGit Dialog Settings</title>
\r
232 <?dbhh topicname="HIDD_SETTINGSDIALOGS"?>
\r
234 <figure id="tgit-dug-settings-dia-dialogs-1">
\r
235 <title>The Settings Dialog, Dialogs Page</title>
\r
236 <graphic fileref="../images/SettingsDialog.png"/>
\r
238 This dialog allows you to configure some of TortoiseGit's
\r
239 dialogs the way you like them.
\r
243 <term>Default limitation of log messages</term>
\r
246 Limits the number of log messages that TortoiseGit loads and displays when you first select
\r
248 <guimenu>TortoiseGit</guimenu>
\r
249 <guimenuitem>Show log...</guimenuitem>
\r
250 </menuchoice> (cf. <xref linkend="tgit-dug-showlog"/>).
\r
251 The number of log messages can be limited by a fixed number of revisions to display,
\r
252 it can remember the last selected date when the Log Dialog is opened again,
\r
253 it can be limited to the last N year(s)/month(s)/week(s),
\r
254 or just be unlimited (i.e., all revisions are shown; this is the default).
\r
255 When a default limitation is active, the <guilabel>From</guilabel> label has a blueish background in the Revision Log dialog.
\r
256 By opening the context menu on the <guilabel>From</guilabel> date picker, you can configure the default limit or disable the default limit for the current dialog.
\r
261 <term>Font for log messages</term>
\r
264 Selects the font face and size used to display the log
\r
265 message itself in the middle pane of the Revision Log
\r
266 dialog, and when composing log messages in the Commit
\r
272 <term>Short date / time format in log messages</term>
\r
275 If the standard long messages use up too much
\r
276 space on your screen use the short format.
\r
281 <term>Show asterisk log prefix</term>
\r
284 An asterisk is inserted as the prefix of log message in Log dialog.
\r
289 <term>Can double-click in log list to compare with previous revision</term>
\r
292 If you frequently find yourself comparing revisions in the top
\r
293 pane of the log dialog, you can use this option to allow that
\r
294 action on double-click. It is not enabled by default because
\r
295 fetching the diff is often a long process, and many people
\r
296 prefer to avoid the wait after an accidental double-click,
\r
297 which is why this option is not enabled by default.
\r
302 <term>Abbreviate renamings</term>
\r
305 Normally renamed files are listed as <filename>long/path/for/file.txt (from long/path/to/file.txt)</filename>.
\r
306 If you check this option renamed files will be listed in a shorter format (<filename>long/path/{to => for}/file.txt</filename>),
\r
307 however, this abbreviated format might be harder to understand.
\r
312 <term>Symbolize ref names</term>
\r
315 Show symbols on ref labels to substitute part of the ref names in order to make them smaller.
\r
316 If this option is enabled, the following description and example will apply.
\r
317 If there is only a single remote, an up-arrow symbol (↑) will substitute the remote name part of each remote branch.
\r
318 If the remote branch is the upstream of a local branch, an equivalent symbol (≡) will substitute the branch name part of the remote branch.
\r
319 <figure id="tgit-dug-settings-symbolizerefname-example">
\r
320 <title>Example of Symbolize ref names</title>
\r
321 <graphic fileref="../images/SymbolizeRefNamesExample.png"/>
\r
327 <term>Enable log cache</term>
\r
330 Load/saves log cache in <filename>.git</filename> folder (<filename>tortoisegit.data</filename>, <filename>tortoisegit.index</filename>) to boost performance of subsequent use of log list.
\r
331 If this option is disabled, the cache files are not read or written.
\r
332 Default is enabled.
\r
337 <term>Enable Gravatar</term>
\r
340 Shows the Gravatar image of the author of the commit in Log Dialog.
\r
341 The URL is customizable so you may specify more options supported by the server,
\r
342 or use your own avatar server.
\r
343 The default URL is <literal>https://www.gravatar.com/avatar/%HASH%?d=identicon</literal>
\r
344 Currently, the supported parameter is <literal>%HASH%</literal>, which is the MD5 email hash.
\r
345 To specify a default image, add <literal>d=</literal> parameter,
\r
346 e.g. <literal>https://www.gravatar.com/avatar/%HASH%?d=identicon</literal>
\r
347 See <ulink url="https://en.gravatar.com/site/implement/images/">
\r
348 <citetitle>Gravatar: Image Requests</citetitle>
\r
349 </ulink> for a list of parameters.
\r
354 <term>Draw tag/branch labels on right side</term>
\r
357 Shows tag/branch labels after the commit message.
\r
362 <term>Display branch revision number</term>
\r
365 Displays for every selected commit a so called "branch revision number" in the commit message field of the Log Dialog.
\r
366 The branch revision number is calculated by calling <literal>git rev-list --count --first-parent [SHA1]</literal> and
\r
367 represents the number of commits between the beginning of time and the selected commit.
\r
368 This number is NOT guaranteed to be unique, especially if you alter the history (e.g., using rebase) or
\r
369 use several branches at the same time. It can be seen "kinda unique" per branch in case you don't alter its history
\r
370 (e.g. by rebasing, resetting) and only commit or merge other branches on it. This number is only displayed
\r
371 for first-parent commits and not for commits on non-fast-forward merges (here duplicate numbers could occur).
\r
372 See <ulink url="https://gcc.gnu.org/ml/gcc/2015-08/msg00148.html">
\r
373 <citetitle>https://gcc.gnu.org/ml/gcc/2015-08/msg00148.html</citetitle>
\r
376 <ulink url="https://gitlab.com/tortoisegit/tortoisegit/merge_requests/1">
\r
377 <citetitle>https://gitlab.com/tortoisegit/tortoisegit/merge_requests/1</citetitle>
\r
378 </ulink> for more details.
\r
383 <term>Show describe in log</term>
\r
386 Shows describe above commit message in the Log dialog.
\r
387 For example, <literal>v0.21.0-589-gdeadc43</literal> refers to the commit
\r
388 <literal>deadc43</literal> that is 589 commits ahead the tag <literal>v0.21.0</literal>.
\r
389 Note: Describe may take longer to run if the commit
\r
390 is far ahead away from a tag.
\r
395 <term>Describe strategy</term>
\r
398 Determine reference lookup strategy:
\r
399 Available options: Annotated tags, All tags, All refs.
\r
400 Default strategy is annotated tags only.
\r
401 If your repository uses lightweight tags to mark releases, choose All tags.
\r
406 <term>Describe Abbreviated size</term>
\r
409 Number of chars of the abbreviated commit id to show in describe.
\r
415 <term>Describe Always show long format</term>
\r
418 Whether to use the long format even when a shorter name could be used.
\r
419 For example, when the commit <literal>g28f087c</literal> has tag <literal>v0.21.0</literal>,
\r
420 it still shows long format <literal>v0.21.0-0-g28f087c</literal> instead of just <literal>v0.21.0</literal>.
\r
426 <sect3 id="tgit-dug-settings-dialogs2">
\r
427 <title>TortoiseGit Dialog Settings 2</title>
\r
428 <?dbhh topicname="HIDD_SETTINGSDIALOGS2"?>
\r
430 <figure id="tgit-dug-settings-dia-dialogs-2">
\r
431 <title>The Settings Dialog, Dialogs Page 2</title>
\r
432 <graphic fileref="../images/SettingsDialog2.png"/>
\r
434 This dialog allows you to configure some more of TortoiseGit's
\r
435 dialogs the way you like them.
\r
439 <term>Git.exe Progress Dialog</term>
\r
442 TortoiseGit can automatically close all progress dialogs
\r
443 when the action is finished without error. This setting
\r
444 allows you to select the conditions for closing the
\r
445 dialogs. The default (recommended) setting is
\r
446 <guilabel>Close manually</guilabel>
\r
447 which allows you to review all messages and check what
\r
448 has happened. However, you may decide that you want to
\r
449 ignore some types of message and have the dialog
\r
450 close automatically if there are no critical changes.
\r
454 <guilabel>Auto-close if no merges, adds or deletes</guilabel>
\r
455 means that the progress dialog will close if there were
\r
456 simple updates, but if changes from the repository were
\r
457 merged with yours, or if any files were added or deleted,
\r
458 the dialog will remain open. It will also stay open if
\r
459 there were any conflicts or errors during the operation.
\r
462 <guilabel>Auto-close if no merges, adds or deletes for
\r
463 local operations</guilabel> means that the progress dialog
\r
464 will close as for <guilabel>Auto-close if no merges, adds
\r
465 or deletes</guilabel> but only for local operations like adding
\r
466 files or reverting changes. For remote operations the
\r
467 dialog will stay open.
\r
470 <guilabel>Auto-close if no conflicts</guilabel>
\r
471 relaxes the criteria further and will close the dialog
\r
472 even if there were merges, adds or deletes. However,
\r
473 if there were any conflicts or errors, the dialog
\r
478 <guilabel>Auto-close if no further options are available</guilabel>
\r
479 will close the dialog if <filename>git.exe</filename> exited cleanly (i.e. no error occurred)
\r
480 and no further options are presented in the progress dialog.
\r
483 <guilabel>Auto-close if no errors</guilabel>
\r
484 always closes the dialog if <filename>git.exe</filename> exited with 0 error code.
\r
489 <term>Use recycle bin when reverting</term>
\r
492 When you revert local modifications, your changes are
\r
493 discarded. TortoiseGit gives you an extra safety net by
\r
494 sending the modified file to the recycle bin before
\r
495 bringing back the pristine copy. If you prefer to
\r
496 skip the recycle bin, uncheck this option.
\r
501 <term>Confirm to kill running git process</term>
\r
504 When enabled, if you close Progress Dialog or Sync Dialog with a running git process,
\r
505 you will be asked for confirmation before killing it.
\r
506 This avoids closing the dialog by accident that kills running git process.
\r
511 <term>Randomize Sync Dialog startup position</term>
\r
514 When enabled, the startup position of Sync Dialog will be randomized.
\r
515 If you open many Sync Dialogs and press pull button at the same time,
\r
516 you may easily press the pull button in any previous Sync Dialog if it finishes and becomes foreground.
\r
521 <term>Hide unchanged refs in Ref Compare List</term>
\r
524 When enabled, unchanged refs will not be shown in Ref Compare List, so you can focus on changed refs.
\r
525 Currently, this list is in Sync Dialog Ref List tab.
\r
530 <term>Show <filename>git.exe</filename> execution timings and timestamp</term>
\r
533 When enabled, <filename>git.exe</filename> execution timings and timestamp will be appended at the end of progress message.
\r
538 <term>Sort tag list in reversed order</term>
\r
541 When enabled, tag list is sorted in reversed order.
\r
542 It is because newer versions are more useful.
\r
543 e.g. Export Dialog allows to select the latest tag when this option is enabled.
\r
548 <term>Use auto-completion of file paths and keywords</term>
\r
551 The commit dialog includes a facility to parse the list
\r
552 of filenames being committed. When you type the first 3
\r
553 letters of an item in the list, the auto-completion
\r
554 box pops up, and you can press Enter to complete the
\r
555 filename. Check the box to enable this feature.
\r
560 <term>Timeout in seconds to stop the auto-completion parsing</term>
\r
563 The auto-completion parser can be quite slow if there are a lot
\r
564 of large files to check. This timeout stops the commit dialog
\r
565 being held up for too long. If you are missing important
\r
566 auto-completion information, you can extend the timeout.
\r
571 <term>Max. items to keep in the log message history</term>
\r
574 When you type in a log message in the commit dialog, TortoiseGit
\r
575 stores it for possible re-use later. By default it will keep the
\r
576 last 25 log messages for each repository, but you can customize
\r
578 If you have many different repositories, you may wish to
\r
579 reduce this to avoid filling your registry.
\r
582 Note that this setting applies only to messages that you type
\r
583 in on this computer. It has nothing to do with the log cache.
\r
588 <term>Select items automatically</term>
\r
591 The normal behavior in the commit dialog is for all modified
\r
592 (versioned) items to be selected for commit automatically.
\r
593 If you prefer to start with nothing selected and pick the
\r
594 items for commit manually, uncheck this box.
\r
600 <sect3 id="tgit-dug-settings-dialogs3">
\r
601 <title>TortoiseGit Dialog Settings 3</title>
\r
602 <?dbhh topicname="HIDD_SETTINGSDIALOGS3"?>
\r
604 <figure id="tgit-dug-settings-dia-dialogs-3">
\r
605 <title>The Settings Dialog, Dialogs 3 Page</title>
\r
606 <graphic fileref="../images/SettingsDialog3.png"/>
\r
608 This dialog allows you to configure some of TortoiseGit's
\r
609 dialogs the way you like them.
\r
610 This third page mainly affects the Commit dialog and the settings which are stored in git config files.
\r
614 If you have problems entering/storing data please see <xref linkend="tgit-dug-settings-hierarchical"/>.
\r
619 <term>Language</term>
\r
622 TortoiseGit by default uses the spell checker modules which are also
\r
623 used by OpenOffice, LibreOffice and Mozilla.
\r
624 Optionally, the Windows 8+ spell checker can also be used (needs to be enabled manually at the moment).
\r
625 If you have those installed or use the Windows spell checker
\r
626 this property will determine which spell checker to use, i.e.
\r
627 in which language the log messages for your project should
\r
629 The <literal>tgit.projectlanguage</literal> config key sets the language
\r
630 module the spell checking engine should use when you enter
\r
631 a log message. You can find the values for your language
\r
633 <ulink url="https://docs.microsoft.com/windows/desktop/intl/language-identifier-constants-and-strings">
\r
634 <citetitle>MSDN: Language Identifiers</citetitle>
\r
638 Enter this value in decimal. For example English (US) can be entered as <literal>1033</literal>.
\r
641 Use <literal>-1</literal> to disable the spell checker.
\r
649 <literal>tgit.logminsize</literal>
\r
650 sets the minimum length of a log message for a commit.
\r
651 If you enter a shorter message than specified here, the commit button
\r
652 is disabled. This feature is very useful for reminding you to
\r
653 supply a proper descriptive message for every commit.
\r
654 If this property is not set,
\r
655 or the value is zero, empty log messages are allowed.
\r
660 <term>Border</term>
\r
663 <literal>tgit.logwidthmarker</literal> is used with projects which
\r
664 require log messages to be formatted with some maximum width
\r
665 (typically 72 characters) before a line break. Setting this
\r
666 property to a non-zero will place a marker to indicate the maximum width
\r
667 and performs line wrapping. Note: this feature
\r
668 will only work correctly if you have a fixed-width font
\r
669 selected for log messages.
\r
674 <term>Warn on Signed-Off-By on commit</term>
\r
677 <literal>tgit.warnnosignedoffby</literal> is used with projects which
\r
678 require Signed-off-by line in commit messages.
\r
683 <term>Overlay Icon</term>
\r
686 <literal>tgit.icon</literal> is used with projects which wish to show the logo
\r
687 on the taskbar for easier identification when multiple TortoiseGit application instances
\r
688 of different projects are running at the same time.
\r
689 <graphic fileref="../images/TaskbarOverlayIcon.png"/>
\r
690 If icon is not 16x16 pixels in size, it will be automatically scaled.
\r
691 Supported formats are <filename>.ico</filename>, <filename>.png</filename>, <filename>.jpg</filename>, <filename>.gif</filename>, <filename>.bmp</filename>.
\r
692 If no icon is included by that project, you may find one on you own,
\r
693 put it in <filename>.git</filename> folder and set the relative path in local config. e.g. <filename>.git/logo.ico</filename>
\r
694 If you want to disable it, you may set <literal>tgit.icon</literal> as an empty string in local config.
\r
695 It will fallback to a color block when disabled or load failed.
\r
696 Note that the advanced option <literal>GroupTaskbarIconsPerRepo</literal> should be 3 or 4 in order to use this function.
\r
702 <sect3 id="tgit-dug-settings-colours">
\r
703 <title>TortoiseGit color Settings</title>
\r
704 <?dbhh topicname="HIDD_SETTINGSCOLORS_1"?>
\r
706 <figure id="tgit-dug-settings-dia-colors">
\r
707 <title>The Settings Dialog, colors Page</title>
\r
708 <graphic fileref="../images/SettingsColors.png"/>
\r
710 This dialog allows you to configure the text colors
\r
711 used in TortoiseGit's dialogs the way you like them.
\r
715 <term>Possible or real conflict / obstructed</term>
\r
718 A conflict has occurred during update, or may occur during merge.
\r
719 Update is obstructed by an existing unversioned file/folder of
\r
720 the same name as a versioned one.
\r
723 This color is also used for error messages in the progress dialogs.
\r
728 <term>Added files</term>
\r
731 Items added to the repository.
\r
736 <term>Missing / deleted / replaced</term>
\r
739 Items deleted from the repository, missing from the working
\r
740 copy, or deleted from the working tree and replaced with
\r
741 another file of the same name.
\r
746 <term>Merged</term>
\r
749 Changes from the repository successfully merged into the working tree
\r
750 without creating any conflicts.
\r
755 <term>Modified / copied</term>
\r
758 Add with history, or paths copied in the repository.
\r
759 Also used in the log dialog for entries which include
\r
765 <term>Note node</term>
\r
768 A reference which points to git notes, under refs/notes name space.
\r
773 <term>Use local branch color for current branch</term>
\r
776 In revision graph, use local branch color for current branch.
\r
777 You may not want to emphasize current branch of a local
\r
778 repository in revision graph.
\r
787 <term>Dark theme</term>
\r
790 The dialogs in TortoiseGit can be shown in a dark mode on Windows 10 1809 and later.
\r
791 This feature also requires that dark mode for applications is enabled in the Windows 10 settings.
\r
795 Note that not all controls in all dialogs are shown in a dark theme.
\r
803 <sect3 id="tgit-dug-settings-colours2">
\r
804 <title>TortoiseGit color Settings 2</title>
\r
805 <?dbhh topicname="HIDD_SETTINGSCOLORS_2"?>
\r
807 <figure id="tgit-dug-settings-dia-colors2">
\r
808 <title>The Settings Dialog, colors Page</title>
\r
809 <graphic fileref="../images/SettingsColors2.png"/>
\r
811 This dialog allows you to configure the text colors
\r
812 used in TortoiseGit's dialogs the way you like them.
\r
815 <sect3 id="tgit-dug-settings-colours3">
\r
816 <title>TortoiseGit color Settings 3</title>
\r
817 <?dbhh topicname="HIDD_SETTINGSCOLORS_3"?>
\r
819 <figure id="tgit-dug-settings-dia-colors-3">
\r
820 <title>The Settings Dialog, colors Page</title>
\r
821 <graphic fileref="../images/SettingsColors3.png"/>
\r
823 This dialog allows you to configure the line colors, line width and node size
\r
824 in the graph column used in TortoiseGit's log dialog the way you like them.
\r