Changes between Version 1 and Version 2 of TracLinks


Ignore:
Timestamp:
Nov 29, 2015, 3:00:01 AM (6 years ago)
Author:
trac
Comment:

--

Legend:

Unmodified
Added
Removed
Modified

  • TracLinks

    v1 v2  
    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:[email protected]:3`, `[2:5/trunk]`
    32  Diffs :: `diff:@1:3`, `diff:tags/trac-0.9.2/wiki-default//tags/trac-0.9.3/wiki-default`
     32 Diffs :: `diff:@1:3`, `diff:plugins/0.12/[email protected]:9953`,
     33          `diff:tags/trac-0.9.2/wiki-default//tags/trac-0.9.3/wiki-default`
    3334          or `diff:trunk/[email protected]//sandbox/[email protected]`
    3435 Files :: `source:trunk/COPYING`, `source:/trunk/[email protected]` (at version 200), `source:/trunk/[email protected]#L25` (at version 200, line 25)
    … …  
    4243 Milestones :: milestone:1.0
    4344 Attachment :: attachment:example.tgz (for current page attachment), attachment:attachment.1073.diff:ticket:944 (absolute path)
    44  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]
    4546 Revision log :: r1:3, [1:3] or log:@1:3, log:[email protected]:3, [2:5/trunk]
    46  Diffs :: diff:@1:3, diff:tags/trac-0.9.2/wiki-default//tags/trac-0.9.3/wiki-default
     47 Diffs :: diff:@1:3, diff:plugins/0.12/[email protected]:9953,
     48          diff:tags/trac-0.9.2/wiki-default//tags/trac-0.9.3/wiki-default
    4749          or diff:trunk/[email protected]//sandbox/[email protected]
    4850 Files :: source:trunk/COPYING, source:/trunk/[email protected] (at version 200), source:/trunk/[email protected]#L25 (at version 200, line 25)
    … …  
    107109
    108110=== Relative links ===
    109 
    110 To create a link to a specific anchor in a page, use '#':
    111 {{{
    112  [#Relativelinks relative links] or [[#Relativelinks|relative links]]
    113 }}}
    114 Displays:
    115   [#Relativelinks relative links] or [[#Relativelinks|relative links]]
    116 
    117 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.
    118111
    119112To create a link to a [trac:SubWiki SubWiki]-page just use a '/':
    … …  
    141134
    142135In order to link explicitly to a [=#toplevel toplevel] Wiki page,
    143 use the `wiki:/` prefix.
    144 Be careful **not** to use the `/` prefix alone, as this corresponds to the
    145 [#Server-relativelinks] syntax and with such a link you will lack the `/wiki/`
    146 part in the resulting URL.
    147 
    148 ''(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.
    149 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.
     137
     138=== Link anchors ===
     139
     140To 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
     146Hint: 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
     148To 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]
     155This 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
     165Such 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
     174Since 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]
    150181
    151182=== InterWiki links ===
    … …  
    254285 - `ticket:123#comment:description`
    255286
     287=== htdocs: links ===
     288
     289Use `htdocs:path/to/file` to reference files in the `htdocs` directory of the Trac environment, the [TracEnvironment#DirectoryStructure web resource directory].
     290
    256291=== query: links ===
    257292
    … …  
    271306 - `ticket:1,150`
    272307
    273 ''(since Trac 0.11)''
    274 
    275308=== timeline: links ===
    276309
    277 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.
    278311
    279312Examples:
    … …  
    282315 - `timeline:2008-01-29T15:48Z`
    283316 - `timeline:2008-01-29T16:48+01`
    284 
    285 ''(since Trac 0.11)''
     317 - `timeline:2008-01-29T16:48+0100`
     318 - `timeline:2008-01-29T16:48+01:00`
    286319
    287320=== wiki: links ===
    288321
    289 See WikiPageNames and [#QuotingspaceinTracLinks quoting space in TracLinks] above.
     322See WikiPageNames and [#QuotingspaceinTracLinks quoting space in TracLinks] above. It is possible to create a link to a specific page revision using the syntax [email protected]
    290323
    291324=== Version Control related links ===
    … …  
    298331 ''aliases:'' `browser:`, `repos:`
    299332
    300 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
    301334if the path points to a directory or to show the latest content of the file.
    302335
    … …  
    304337 - `source:/some/[email protected]` - link to the file's revision 123
    305338 - `source:/some/[email protected]` - link explicitly to the latest revision of the file
     339 - `source:/some/[email protected]` - link to latest revision of the specified file in `named-branch` (DVCS such as Git or Mercurial)
    306340
    307341If the revision is specified, one can even link to a specific line number:
    308342 - `source:/some/[email protected]#L10`
    309343 - `source:/tag/[email protected]#L10`
     344 - `source:/some/[email protected]#L10`
    310345
    311346Finally, one can also highlight an arbitrary set of lines:
    312  - `source:/some/[email protected]:10-20,100,103#L99` - highlight lines 10 to 20, and lines 100 and 103.
    313    ''(since 0.11)''
     347 - `source:/some/[email protected]:10-20,100,103#L99` - highlight lines 10 to 20, and lines 100 and 103, and target line 99
     348 - or without version number (the `@` is still needed): `source:/some/[email protected]: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
    314349
    315350Note 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)''
    … …  
    321356 * `export:123:/some/file` - get revision 123 of the specified file
    322357 * `export:/some/[email protected]` - get revision 123 of the specified file
     358 * `export:/some/[email protected]` - get latest revision of the specified file in `named-branch` (DVCS such as Git or Mercurial).
    323359
    324360This can be very useful for displaying XML or HTML documentation with correct stylesheets and images, in case that has been checked in into the repository. Note that for this use case, you'd have to allow the web browser to render the content by setting `[browser] render_unsafe_content = yes` (see TracIni#browser-section), otherwise Trac will force the files to be downloaded as attachments for security concerns.
    … …  
    334370 - `log:@20788,20791:20795` - list revision 20788 and the revisions from 20791 to 20795
    335371 - `log:/trunk/[email protected],20791:20795` - list revision 20788 and the revisions from 20791 to 20795 which affect the given path
     372 - `log:/[email protected]` - the revisions in `tools` starting from the latest revision in `named-branch` (DVCS such as Git or Mercurial)
    336373
    337374There are short forms for revision ranges as well: