Kiln » TortoiseHg » TortoiseHg
Clone URL:  
Pushed to one repository · View In Graph Contained in 0.8.2, 0.8.3, and 0.9

doc: put handy vim modelines on source files

reST recommends tabs instead of spaces, and 4-wide tabs

Changeset 4dced60bb05f…

Parent d40ad17483b5…

by Steve Borho

Changes to 13 files · Browse files at 4dced60bb05f Showing diff from parent d40ad17483b5 Diff from another changeset...

Change 1 of 1 Show Entire File doc/​source/​changelog.txt Stacked
 
187
188
189
 
 
 
187
188
189
190
191
@@ -187,3 +187,5 @@
  Maximum size of file to be diffed  :guilabel:`Bottom Diffs`   Show diffs below file list + +.. vim: noet tw=4
Change 1 of 1 Show Entire File doc/​source/​commit.txt Stacked
 
317
318
319
 
 
317
318
319
320
@@ -317,3 +317,4 @@
 command. Qct was already doing both of these things, so this  will come as no surprise to Qct users.   +.. vim: noet tw=4
Change 1 of 1 Show Entire File doc/​source/​common.txt Stacked
 
106
107
108
 
 
 
106
107
108
109
110
@@ -106,3 +106,5 @@
   *hgcmd* also responds appropriately to the global :kbd:`CTRL-W` and  more drastic :kbd:`CTRL-Q` accelerators. + +.. vim: noet tw=4
Change 1 of 1 Show Entire File doc/​source/​datamine.txt Stacked
 
102
103
104
 
 
 
102
103
104
105
106
@@ -102,3 +102,5 @@
  Give each author a separate color in the changelog graph  :menuselection:`TortoiseHg --> Tab width`   Number of spaces to expand tabs in diffs and annotate output + +.. vim: noet tw=4
Change 1 of 1 Show Entire File doc/​source/​explorer.txt Stacked
 
67
68
69
 
 
 
67
68
69
70
71
@@ -67,3 +67,5 @@
 (droplet) icon in the system tray and select :guilabel:`Options`.  In the options dialog you can promote individual menu options to  the top menu. + +.. vim: noet tw=4
Change 1 of 1 Show Entire File doc/​source/​index.txt Stacked
 
32
33
34
 
 
32
33
34
35
@@ -32,3 +32,4 @@
 * :ref:`modindex`  * :ref:`search`   +.. vim: noet tw=4
Change 1 of 1 Show Entire File doc/​source/​intro.txt Stacked
 
24
25
26
 
 
 
24
25
26
27
28
@@ -24,3 +24,5 @@
 TortoiseHg is primarily written in Python and PyGtk (the Windows shell  extension being a noticeable exception). The hgtk script can be used  on any platform that supports PyGtk, including Mac OS X. + +.. vim: noet tw=4
Change 1 of 1 Show Entire File doc/​source/​preface.txt Stacked
 
86
87
88
 
 
 
86
87
88
89
90
@@ -86,3 +86,5 @@
   .. warning::   An important note. Pay attention. + +.. vim: noet tw=4
Change 1 of 1 Show Entire File doc/​source/​recovery.txt Stacked
 
27
28
29
 
 
27
28
29
30
@@ -27,3 +27,4 @@
  :command:`hg verify` - perform a consistency check of the contents of your   repository   +.. vim: noet tw=4
Change 1 of 1 Show Entire File doc/​source/​serve.txt Stacked
 
50
51
52
 
 
 
50
51
52
53
54
@@ -50,3 +50,5 @@
 -----------------  * Improved error handling  * i18n fixes + +.. vim: noet tw=4
Change 1 of 1 Show Entire File doc/​source/​settings.txt Stacked
 
80
81
82
 
 
80
81
82
83
@@ -80,3 +80,4 @@
 :guilabel:`TortoiseHg`, :guilabel:`Commit`, :guilabel:`Changelog`, which  are specifically for TortoiseHg).   +.. vim: noet tw=4
Change 1 of 1 Show Entire File doc/​source/​shelve.txt Stacked
 
119
120
121
 
 
 
119
120
121
122
123
@@ -119,3 +119,5 @@
   * :menuselection:`TortoiseHg --> Bottom Diffs`  * :menuselection:`TortoiseHg --> Tab Width` + +.. vim: noet tw=4
Change 1 of 1 Show Changes Only doc/​source/​synchronize.txt Stacked
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
 
 
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
 ======================  TortoiseHg Synchronize  ======================    .. module:: synchronize.dialog   :synopsis: Dialog used to perform synchronization operations    .. figure:: figures/synchronize.png   :alt: Synchronize dialog     Synchronize dialog    The synchronize tool is used to transmit changesets between repositories  or optionally to email recipients.    :guilabel:`Incoming`   show changesets that would be pulled from target repository  :guilabel:`Pull`   pull incoming changesets from target repository  :guilabel:`Outgoing`   show changesets that would be pushed to target repository  :guilabel:`Push`   push outgoing changesets to target repository  :guilabel:`Email`   send outgoing changesets (to target repository) as email  :guilabel:`Stop`   stop current operation  :guilabel:`Configure`   configure repository paths (aliases)    Below the toolbar are two buttons and a text entry:    :guilabel:`Repo:`   browse for a local repository to synchronize with  :guilabel:`Bundle:`   browse for a local bundle file to pull from    The text entry/combo box is where you enter or select paths of target  repositories. The synchronize tool will seed the drop-down list with  path aliases configured for this repository.    The :guilabel:`Post Pull Operation` frame contains radio buttons for  selecting the operation which is performed after a pull. This behavior  is configurable via the :guilabel:`Configure` button. You can select a  default behavior for your user account and override that selection on a  per-repository basis.    :guilabel:`Nothing`   No operations are performed after a pull. You will be allowed to   view the pulled changesets in the log viewer, and you will have the   option to update to the new tip if applicable.  :guilabel:`Update`   Automatically update to the new branch tip if, and only if, new   revisions were pulled into the local repository. This could trigger   a merge if the pulled changes conflict with local uncommitted   changes.  :guilabel:`Fetch`   Equivalent to hg fetch. See the fetch extension documentation for   it's behavior.  :guilabel:`Rebase`   Equivalent to pull --rebase. See the rebase extension documentation   for it's behavior. Rebase operations disable connections to any   changelog tools, since it is very destructive to any app which is   holding a repository object.    The :guilabel:`use proxy` button is a quick way to disable your proxy  configuration for individual operations. The button is only sensitive  when an http proxy is configured.    All operations which require authentication will pop up dialog boxes to  get the required information from the user. TortoiseHg uses the  TortoisePlink tool (borrowed from the TortoiseSVN distribution) to  handle *ssh:* connections and authentication. See the FAQ_ for help if  you have trouble connecting to ssh servers.    .. _FAQ: http://bitbucket.org/tortoisehg/stable/wiki/FAQ#tortoisehg-faq    Under the :guilabel:`Advanced Options` fold-up panel are a number of  configurables that are valid for most push/pull operations.    :guilabel:`Force pull or push`   override warnings about multiple heads or unrelated repositories  :guilabel:`Target Revision`   to avoid sending all revisions  :guilabel:`Remote Command`   provides -e argument  :guilabel:`Show patches`   show diffs in incoming and outging changes  :guilabel:`Show Newest First`   reverse order that changesets are listed  :guilabel:`Show No Merges`   filter out merge changesets from output (does not affect push/pull)      After Pull  ----------    After changesets are pulled into your repository, two buttons may appear  at the bottom of the dialog:    :guilabel:`View pulled changesets`   Open the changelog viewer and inspect pulled changesets  :guilabel:`Update to tip`   Update your working directory to the new tip    Either button may be hidden if it is not applicable.    Email  -----    .. figure:: figures//email.png   :alt: Email dialog     Email dialog    The email dialog can be launched from two TortoiseHg tools.    1) The changelog tool, in which case the user intends to email a single   revision or a range of revisions.    2) The synchronize tool, in which case the user intends to email all   outgoing changes to the current target repository (it's good practice to   check the outgoing changes before launching the email dialog).    The :guilabel:`Send` button is obvious, and the :guilabel:`Configure`  dialog predictably opens the TortoiseHg Settings dialog to the email tab  where you can configure your SMTP settings and set default  :guilabel:`To:` and :guilabel:`From:` addresses.    :guilabel:`In-Reply-To:` can be used to get your patches properly  threaded in mailing lists.    Please consult the Mercurial documentation for the differences between  plain patches, HG patches, Git patches, and bundles.    Changes since 0.7  -----------------    * Path drop-down list no longer includes most-recently-used paths. It   only includes configured repository paths.  * Email dialog now has buttons for configuring in-reply-to tags and the   attachment types.  * Email dialog now sends an intro message only when one has been   entered, regardless of patch count. + +.. vim: noet tw=4