Changes between Version 4 and Version 5 of TracLinks
- Timestamp:
- Mar 25, 2015, 3:59:43 PM (10 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
TracLinks
v4 v5 28 28 Milestones :: `milestone:1.0` 29 29 Attachment :: `attachment:example.tgz` (for current page attachment), `attachment:attachment.1073.diff:ticket:944` (absolute path) 30 Changesets :: `r1`, `[1]`, `changeset:1` or (restricted) `[1/trunk]`, `changeset:1/trunk` 30 Changesets :: `r1`, `[1]`, `changeset:1` or (restricted) `[1/trunk]`, `changeset:1/trunk`, `[1/repository]` 31 31 Revision log :: `r1:3`, `[1:3]` or `log:@1:3`, `log:trunk@1:3`, `[2:5/trunk]` 32 32 Diffs :: `diff:@1:3`, `diff:plugins/0.12/mercurial-plugin@9128:9953`, … … 43 43 Milestones :: milestone:1.0 44 44 Attachment :: attachment:example.tgz (for current page attachment), attachment:attachment.1073.diff:ticket:944 (absolute path) 45 Changesets :: r1, [1], changeset:1 or (restricted) [1/trunk], changeset:1/trunk 45 Changesets :: r1, [1], changeset:1 or (restricted) [1/trunk], changeset:1/trunk, [1/repository] 46 46 Revision log :: r1:3, [1:3] or log:@1:3, log:trunk@1:3, [2:5/trunk] 47 47 Diffs :: diff:@1:3, diff:plugins/0.12/mercurial-plugin@9128:9953, … … 110 110 === Relative links === 111 111 112 To create a link to a specific anchor in a page, use '#':113 {{{114 [#Relativelinks relative links] or [[#Relativelinks|relative links]]115 }}}116 Displays:117 [#Relativelinks relative links] or [[#Relativelinks|relative links]]118 119 Hint: when you move your mouse over the title of a section, a '¶' character will be displayed. This is a link to that specific section and you can use this to copy the `#...` part inside a relative link to an anchor.120 121 112 To create a link to a [trac:SubWiki SubWiki]-page just use a '/': 122 113 {{{ … … 143 134 144 135 In order to link explicitly to a [=#toplevel toplevel] Wiki page, 145 use the `wiki:/` prefix. 146 Be careful **not** to use the `/` prefix alone, as this corresponds to the 147 [#Server-relativelinks] syntax and with such a link you will lack the `/wiki/` 148 part in the resulting URL. 149 150 ''(Changed in 0.11)'' Note that in Trac 0.10, using e.g. `[../newticket]` may have worked for linking to the `/newticket` top-level URL, but since 0.11, such a link will stay in the wiki namespace and therefore link to a sibling page. 151 See [#Server-relativelinks] for the new syntax. 136 use the `wiki:/` prefix. Be careful **not** to use the `/` prefix alone, as this corresponds to the [#Server-relativelinks] syntax and with such a link you will lack the `/wiki/` part in the resulting URL. A link such as `[../newticket]` will stay in the wiki namespace and therefore link to a sibling page. 137 138 === Link anchors === 139 140 To create a link to a specific anchor in a page, use '#': 141 {{{ 142 [#Linkanchors Link anchors] or [[#Linkanchors|Link anchors]] 143 }}} 144 [#Linkanchors Link anchors] or [[#Linkanchors|Link anchors]] 145 146 Hint: when you move your mouse over the title of a section, a '¶' character will be displayed. This is a link to that specific section and you can use this to copy the `#...` part inside a relative link to an anchor. 147 148 To create a link to the first or last occurrence of a term on a page, use a ''pseudo anchor'' starting with '#/' or '#?': 149 {{{ 150 [#/Milestone first occurrence of Milestone] or 151 [#?Milestone last occurrence of Milestone] 152 }}} 153 [#/Milestone first occurrence of Milestone] or 154 [#?Milestone last occurrence of Milestone] 155 This will also highlight all other matches on the linked page. By default only case sensitive matches are considered. To include case insensitive matches append '/i': 156 {{{ 157 [#/Milestone/i first occurrence of Milestone or milestone] or 158 [#?Milestone/i last occurrence of Milestone or milestone] 159 }}} 160 [#/Milestone/i first occurrence of Milestone or milestone] or 161 [#?Milestone/i last occurrence of Milestone or milestone] 162 163 ''(since Trac 1.0)'' 164 165 Such anchors can be very useful for linking to specific lines in a file in the source browser: 166 {{{ 167 [trac:source:tags/trac-0.12/trac/wiki/api.py#L127 Line 127] or 168 [trac:source:tags/trac-0.12/trac/ticket/roadmap.py#L47 Line 47] 169 }}} 170 [trac:source:tags/trac-0.12/trac/wiki/api.py#L127 Line 127] or 171 [trac:source:tags/trac-0.12/trac/ticket/roadmap.py#L47 Line 47] 172 (Hint: The line numbers displayed in the source browser are links to anchors on the respective lines.) 173 174 Since such links become outdated when the file changes, it can be useful to link using a '#/' pseudo anchor instead: 175 {{{ 176 [trac:source:trunk/trac/wiki/api.py#/IWikiSyntaxProvider IWikiSyntaxProvider] or 177 [trac:source:trunk/trac/env.py#/ISystemInfoProvider ISystemInfoProvider] 178 }}} 179 [trac:source:trunk/trac/wiki/api.py#/IWikiSyntaxProvider IWikiSyntaxProvider] or 180 [trac:source:trunk/trac/env.py#/ISystemInfoProvider ISystemInfoProvider] 152 181 153 182 === InterWiki links === … … 277 306 - `ticket:1,150` 278 307 279 ''(since Trac 0.11)''280 281 308 === timeline: links === 282 309 283 Links to the timeline can be created by specifying a date in the ISO:8601 format. The date can be optionally followed by a time specification. The time is interpreted as being UTC time, but alternatively you can specify your local time, followed by your timezone if you don't want to compute the UTC time.310 Links to the timeline can be created by specifying a date in the ISO:8601 format. The date can be optionally followed by a time specification. The time is interpreted as being UTC time, but if you don't want to compute the UTC time, you can specify a local time followed by your timezone offset relative to UTC. 284 311 285 312 Examples: … … 288 315 - `timeline:2008-01-29T15:48Z` 289 316 - `timeline:2008-01-29T16:48+01` 290 291 ''(since Trac 0.11)'' 317 - `timeline:2008-01-29T16:48+0100` 318 - `timeline:2008-01-29T16:48+01:00` 292 319 293 320 === wiki: links === … … 304 331 ''aliases:'' `browser:`, `repos:` 305 332 306 The default behavior for a source:/some/path linkis to open the browser in that directory directory333 The default behavior for a `source:/some/path link` is to open the browser in that directory directory 307 334 if the path points to a directory or to show the latest content of the file. 308 335 … … 316 343 317 344 Finally, one can also highlight an arbitrary set of lines: 318 - `source:/some/file@123:10-20,100,103#L99` - highlight lines 10 to 20, and lines 100 and 103 .319 ''(since 0.11)''345 - `source:/some/file@123:10-20,100,103#L99` - highlight lines 10 to 20, and lines 100 and 103, and target line 99 346 - or without version number (the `@` is still needed): `source:/some/file@:10-20,100,103#L99`. Version can be omitted when the path is pointing to a source file that will no longer change (like `source:/tags/...`), otherwise it's better to specify which lines of //which version// of the file you're talking about 320 347 321 348 Note that in presence of multiple repositories, the name of the repository is simply integrated in the path you specify for `source:` (e.g. `source:reponame/trunk/README`). ''(since 0.12)''