Changes between Version 3 and Version 4 of 0.12/TracLinks
- Timestamp:
- Mar 19, 2010, 11:43:36 AM (14 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
0.12/TracLinks
v3 v4 142 142 This can be seen as a kind of InterWiki link specialized for targeting other Trac projects. 143 143 144 Any type of Trac links could be written in one Trac environment and actually refer to resources present in another Trac environment, provided the Trac link is prefixed by the name of that other Trac environment followed by a colon. That other Trac environment must be registered, under its name or an alias. See InterTrac for details. 145 146 A distinctive advantage of InterTrac links over InterWiki links is that the shorthand form of Trac links usually have a way to understand the InterTrac prefixes. For example, links to Trac tickets can be written #T234 (if T was set as an alias for Trac), links to Trac changesets can be written [trac 1508]. 144 Any type of Trac link can be written in one Trac environment and actually refer to resources in another Trac environment. All that is required is to prefix the Trac link with the name of the other Trac environment followed by a colon. The other Trac environment must be registered on the InterTrac page. 145 146 A distinctive advantage of InterTrac links over InterWiki links is that the shorthand form of Trac links (e.g. `{}`, `r`, `#`) can also be used. For example if T was set as an alias for Trac, links to Trac tickets can be written #T234, links to Trac changesets can be written [trac 1508]. 147 See InterTrac for the complete details. 147 148 148 149 === Server-relative links === … … 195 196 === Parameterized Trac links === 196 197 197 The Trac links target Trac resources which have generally more than one way to be rendered, according tosome extra parameters. For example, a Wiki page can accept a `version` or a `format` parameter, a report can make use of dynamic variables, etc.198 199 AnyTrac links can support an arbitrary set of parameters, written in the same way as they would be for the corresponding URL. Some examples:198 Many Trac resources have more than one way to be rendered, depending on some extra parameters. For example, a Wiki page can accept a `version` or a `format` parameter, a report can make use of dynamic variables, etc. 199 200 Trac links can support an arbitrary set of parameters, written in the same way as they would be for the corresponding URL. Some examples: 200 201 - `wiki:WikiStart?format=txt` 201 202 - `ticket:1?version=1` … … 204 205 205 206 == TracLinks Reference == 206 The following sections describe the individual link types in detail, as well as several notesadvanced usage of links.207 The following sections describe the individual link types in detail, as well as notes on advanced usage of links. 207 208 208 209 === attachment: links === … … 223 224 === comment: links === 224 225 225 When you're inside a given ticket s, you can simply write e.g. !comment:3 to link to the third change comment.226 When you're inside a given ticket, you can simply write e.g. !comment:3 to link to the third change comment. 226 227 It is possible to link to a comment of a specific ticket from anywhere using one of the following syntax: 227 - !comment:3:ticket:123228 - !ticket:123#comment:3 (note that you can't write !#123#!comment:3!)228 - `comment:3:ticket:123` 229 - `ticket:123#comment:3` (note that you can't write `#123#!comment:3`!) 229 230 It is also possible to link to the ticket's description using one of the following syntax: 230 - !comment:description231 - !comment:description:ticket:123232 - !ticket:123#comment:description231 - `comment:description` (within the ticket) 232 - `comment:description:ticket:123` 233 - `ticket:123#comment:description` 233 234 234 235 === query: links === … … 241 242 242 243 === ticket: links === 243 ''alias e:'' bug:244 ''alias:'' `bug:` 244 245 245 246 Besides the obvious `ticket:id` form, it is also possible to specify a list of tickets or even a range of tickets instead of the `id`. This generates a link to a custom query view containing this fixed set of tickets. … … 269 270 === Version Control related links === 270 271 ==== source: links ==== 271 ''aliases:'' browser:, repos:272 273 The default behavior for a source:/some/path link is to open the directory browser272 ''aliases:'' `browser:`, `repos:` 273 274 The default behavior for a source:/some/path link is to open the browser in that directory directory 274 275 if the path points to a directory or to show the latest content of the file. 275 276 … … 286 287 ''(since 0.11)'' 287 288 288 Note that in presence of multiple repositories, the name of the repository is simply integrated in the path you specify for `source:` .289 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)'' 289 290 290 291 ==== export: links ==== … … 301 302 ==== log: links ==== 302 303 303 The `log:` links are used to display revision ranges. In its simplest form, it can link to the latest revisions fromthe specified path, but it can also support displaying an arbitrary set of revisions.304 The `log:` links are used to display revision ranges. In its simplest form, it can link to the latest revisions of the specified path, but it can also support displaying an arbitrary set of revisions. 304 305 - `log:/` - the latest revisions starting at the root of the repository 305 306 - `log:/trunk/tools` - the latest revisions in `trunk/tools` 306 307 - `log:/trunk/tools@10000` - the revisions in `trunk/tools` starting from revision 10000 307 - `log:@20788,20791:20795` - list revision 20788 and the 20791 to 20795 revision range308 - `log:/trunk/tools@20788,20791:20795` - list revision 20788 and the revisions from the 20791 to 20795 rangewhich affect the given path308 - `log:@20788,20791:20795` - list revision 20788 and the revisions from 20791 to 20795 309 - `log:/trunk/tools@20788,20791:20795` - list revision 20788 and the revisions from 20791 to 20795 which affect the given path 309 310 310 311 There are short forms for revision ranges as well: … … 313 314 - `r20791:20795` (but not `r20788,20791:20795` nor `r20791:20795/trunk`) 314 315 315 Finally, note that in all of the above, a revision range can be written indifferently`x:y` or `x-y`.316 317 Again, in the presence of multiple repositories, the name of the repository should come first and be integrated inthe path, e.g. `log:repos/branches` or `[20-40/repos]`.316 Finally, note that in all of the above, a revision range can be written either as `x:y` or `x-y`. 317 318 In the presence of multiple repositories, the name of the repository should be specified as the first part of the path, e.g. `log:repos/branches` or `[20-40/repos]`. 318 319 319 320 ----