Changes between Version 4 and Version 5 of TracLinks


Ignore:
Timestamp:
08/08/15 13:07:50 (2 years ago)
Author:
trac
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • TracLinks

    v4 v5  
    2828 Milestones :: `milestone:1.0` 
    2929 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]` 
    3131 Revision log :: `r1:3`, `[1:3]` or `log:@1:3`, `log:trunk@1:3`, `[2:5/trunk]` 
    3232 Diffs :: `diff:@1:3`, `diff:plugins/0.12/mercurial-plugin@9128:9953`, 
     
    4343 Milestones :: milestone:1.0 
    4444 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] 
    4646 Revision log :: r1:3, [1:3] or log:@1:3, log:trunk@1:3, [2:5/trunk] 
    4747 Diffs :: diff:@1:3, diff:plugins/0.12/mercurial-plugin@9128:9953, 
     
    134134 
    135135In order to link explicitly to a [=#toplevel toplevel] Wiki page, 
    136 use the `wiki:/` prefix. 
    137 Be careful **not** to use the `/` prefix alone, as this corresponds to the 
    138 [#Server-relativelinks] syntax and with such a link you will lack the `/wiki/`  
    139 part in the resulting URL. 
    140  
    141 ''(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.  
    142 See [#Server-relativelinks] for the new syntax. 
     136use 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. 
    143137 
    144138=== Link anchors === 
     
    312306 - `ticket:1,150` 
    313307 
    314 ''(since Trac 0.11)'' 
    315  
    316308=== timeline: links === 
    317309 
    318 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. 
     310Links 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. 
    319311 
    320312Examples: 
     
    323315 - `timeline:2008-01-29T15:48Z` 
    324316 - `timeline:2008-01-29T16:48+01` 
    325  
    326 ''(since Trac 0.11)'' 
     317 - `timeline:2008-01-29T16:48+0100` 
     318 - `timeline:2008-01-29T16:48+01:00` 
    327319 
    328320=== wiki: links === 
     
    339331 ''aliases:'' `browser:`, `repos:` 
    340332 
    341 The default behavior for a source:/some/path link is to open the browser in that directory directory  
     333The default behavior for a `source:/some/path link` is to open the browser in that directory directory  
    342334if the path points to a directory or to show the latest content of the file. 
    343335 
     
    351343 
    352344Finally, one can also highlight an arbitrary set of lines: 
    353  - `source:/some/file@123:10-20,100,103#L99` - highlight lines 10 to 20, and lines 100 and 103. 
    354    ''(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 
    355347 
    356348Note 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)''