Changes between Version 1 and Version 2 of TracLinks


Ignore:
Timestamp:
Nov 5, 2016, 11:49:48 AM (3 years ago)
Author:
trac
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • TracLinks

    v1 v2  
    1 = Trac Links =
     1= Trac Links
     2
    23[[TracGuideToc]]
    3 
    4 TracLinks are a fundamental feature of Trac, because they allow easy hyperlinking between the various entities in the system—such as tickets, reports, changesets, Wiki pages, milestones, and source files—from anywhere WikiFormatting is used.
    5 
    6 TracLinks are generally of the form '''type:id''' (where ''id'' represents the
    7 number, name or path of the item) though some frequently used kinds of items
    8 also have short-hand notations.
    9 
    10 == Where to use TracLinks ==
     4[[PageOutline(2-5,Contents,pullout)]]
     5
     6TracLinks are a fundamental feature of Trac, because they allow easy hyperlinking between the various entities in the system — such as tickets, reports, changesets, Wiki pages, milestones, and source files — from anywhere where WikiFormatting is used.
     7
     8TracLinks are generally of the form '''type:id''' (where ''id'' represents the number, name or path of the item) though some frequently used kinds of items also have short-hand notations.
     9
     10== Where to use TracLinks
     11
    1112You can use TracLinks in:
    1213
     
    1718and any other text fields explicitly marked as supporting WikiFormatting.
    1819
    19 Some examples:
    20  * Tickets: '''!#1''' or '''!ticket:1'''
    21  * Ticket comments: '''!comment:1:ticket:2'''
    22  * Reports: '''!{1}''' or '''!report:1'''
    23  * Changesets: '''!r1''', '''![1]''', '''!changeset:1''' or (restricted) '''![1/trunk]''', '''!changeset:1/trunk'''
    24  * Revision log: '''!r1:3''', '''![1:3]''' or '''!log:@1:3''', '''!log:trunk@1:3''', '''![2:5/trunk]'''
    25  * Diffs (requires [trac:milestone:0.10 0.10]): '''!diff:@1:3''', '''!diff:tags/trac-0.9.2/wiki-default//tags/trac-0.9.3/wiki-default''' or '''!diff:trunk/trac@3538//sandbox/vc-refactoring@3539'''
    26  * Wiki pages: '''!CamelCase''' or '''!wiki:CamelCase'''
    27  * Parent page: '''![..]'''
    28  * Milestones: '''!milestone:1.0'''
    29  * Attachment: '''!attachment:example.tgz''' (for current page attachment), '''!attachment:attachment.1073.diff:ticket:944'''
    30 (absolute path)
    31  * Files: '''!source:trunk/COPYING'''
    32  * A specific file revision: '''!source:/trunk/COPYING@200'''
    33  * A particular line of a specific file revision: '''!source:/trunk/COPYING@200#L25'''
    34 Display:
    35  * Tickets: #1 or ticket:1
    36  * Ticket comments: comment:1:ticket:2
    37  * Reports: {1} or report:1
    38  * Changesets: r1, [1], changeset:1 or (restricted) [1/trunk], changeset:1/trunk
    39  * Revision log: r1:3, [1:3] or log:@1:3, log:trunk@1:3, [2:5/trunk]
    40  * Diffs (requires [milestone:0.10 0.10]): diff:@1:3, diff:tags/trac-0.9.2/wiki-default//tags/trac-0.9.3/wiki-default or diff:trunk/trac@3538//sandbox/vc-refactoring@3539
    41  * Wiki pages: CamelCase or wiki:CamelCase
    42  * Parent page: [..]
    43  * Milestones: milestone:1.0
    44  * Attachment: attachment:example.tgz (for current page attachment), attachment:attachment.1073.diff:ticket:944
    45 (absolute path)
    46  * Files: source:trunk/COPYING
    47  * A specific file revision: source:/trunk/COPYING@200
    48  * A particular line of a specific file revision: source:/trunk/COPYING@200#L25
    49 
    50 '''Note:''' The wiki:CamelCase form is rarely used, but it can be convenient to refer to
    51 pages whose names do not follow WikiPageNames rules, i.e., single words,
    52 non-alphabetic characters, etc. See WikiPageNames for more about features specific
    53 to links to Wiki page names.
    54 
    55 Trac links using the full (non-shorthand) notation can also be given a custom
    56 link title like this:
    57 
    58 {{{
    59 [ticket:1 This is a link to ticket number one].
    60 }}}
    61 
    62 Display: [ticket:1 This is a link to ticket number one].
    63 
    64 If the title is omitted, only the id (the part after the colon) is displayed:
    65 
    66 {{{
    67 [ticket:1]
    68 }}}
    69 
    70 Display: [ticket:1]
    71 
    72 `wiki` is the default if the namespace part of a full link is omitted (''since version 0.10''):
    73 
    74 {{{
    75 [SandBox the sandbox]
    76 }}}
    77 
    78 Display: [SandBox the sandbox]
     20== Overview
     21
     22||= Wiki Markup =||= Display =||
     23{{{#!td
     24 Wiki pages :: `CamelCase` or `wiki:CamelCase`
     25 Parent page :: `[..]`
     26 Tickets :: `#1` or `ticket:1`
     27 Ticket comments :: `comment:1:ticket:2`
     28 Reports :: `{1}` or `report:1`
     29 Milestones :: `milestone:1.0`
     30 Attachment :: `attachment:example.tgz` (for current page attachment), `attachment:attachment.1073.diff:ticket:944` (absolute path)
     31 Changesets :: `r1`, `[1]`, `changeset:1` or (restricted) `[1/trunk]`, `changeset:1/trunk`, `[1/repository]`
     32 Revision log :: `r1:3`, `[1:3]` or `log:@1:3`, `log:trunk@1:3`, `[2:5/trunk]`
     33 Diffs :: `diff:@1:3`, `diff:plugins/0.12/mercurial-plugin@9128:9953`,
     34          `diff:tags/trac-0.9.2/wiki-default//tags/trac-0.9.3/wiki-default`
     35          or `diff:trunk/trac@3538//sandbox/vc-refactoring@3539`
     36 Files :: `source:trunk/COPYING`, `source:/trunk/COPYING@200` (at version 200), `source:/trunk/COPYING@200#L25` (at version 200, line 25)
     37}}}
     38{{{#!td
     39 Wiki pages :: CamelCase or wiki:CamelCase
     40 Parent page :: [..]
     41 Tickets :: #1 or ticket:1
     42 Ticket comments :: comment:1:ticket:2
     43 Reports :: {1} or report:1
     44 Milestones :: milestone:1.0
     45 Attachment :: attachment:example.tgz (for current page attachment), attachment:attachment.1073.diff:ticket:944 (absolute path)
     46 Changesets :: r1, [1], changeset:1 or (restricted) [1/trunk], changeset:1/trunk, [1/repository]
     47 Revision log :: r1:3, [1:3] or log:@1:3, log:trunk@1:3, [2:5/trunk]
     48 Diffs :: diff:@1:3, diff:plugins/0.12/mercurial-plugin@9128:9953,
     49          diff:tags/trac-0.9.2/wiki-default//tags/trac-0.9.3/wiki-default
     50          or diff:trunk/trac@3538//sandbox/vc-refactoring@3539
     51 Files :: source:trunk/COPYING, source:/trunk/COPYING@200 (at version 200), source:/trunk/COPYING@200#L25 (at version 200, line 25)
     52}}}
     53
     54'''Note:''' The wiki:CamelCase form is rarely used, but it can be convenient to refer to pages whose names do not follow WikiPageNames rules, ie single words, non-alphabetic characters, etc. See WikiPageNames for more about features specific to links to Wiki page names.
     55
     56
     57{{{#!table class=""
     58|||| Trac links using the full (non-shorthand) notation can also be given a custom link title like this: ||
     59{{{#!td
     60{{{
     61[ticket:1 This is a link to ticket number one] or
     62[[ticket:1|This is another link to ticket number one]].
     63}}}
     64}}}
     65{{{#!td
     66[ticket:1 This is a link to ticket number one] or
     67[[ticket:1|This is another link to ticket number one]].
     68}}}
     69|--------------------------------------------------------------------------------------
     70|||| If the title is omitted, only the id (the part after the colon) is displayed:  ||
     71{{{#!td
     72{{{
     73[ticket:1] or [[ticket:2]]
     74}}}
     75}}}
     76{{{#!td
     77[ticket:1] or [[ticket:2]]
     78}}}
     79|--------------------------------------------------------------------------------------
     80|||| `wiki` is the default if the namespace part of a full link is omitted:  ||
     81{{{#!td
     82{{{
     83[SandBox the sandbox] or
     84[[SandBox|the sandbox]]
     85}}}
     86}}}
     87{{{#!td
     88[SandBox the sandbox] or
     89[[SandBox|the sandbox]]
     90}}}
     91|--------------------------------------------------------------------------------------
     92|||| The short form ''realm:target'' can also be wrapped within a <...> pair, [[br]] which allow for arbitrary characters (i.e. anything but >)  ||
     93{{{#!td
     94{{{
     95<wiki:Strange(page@!)>
     96}}}
     97}}}
     98{{{#!td
     99<wiki:Strange(page@!)>
     100}}}
     101}}}
    79102
    80103TracLinks are a very simple idea, but actually allow quite a complex network of information. In practice, it's very intuitive and simple to use, and we've found the "link trail" extremely helpful to better understand what's happening in a project or why a particular change was made.
    81104
    82 
    83 == Advanced use of TracLinks ==
    84 
    85 === Relative links ===
     105== Advanced use of TracLinks
     106
     107=== Relative links
     108
     109To create a link to a [trac:SubWiki SubWiki]-page just use a '/':
     110{{{
     111 WikiPage/SubWikiPage or ./SubWikiPage
     112}}}
     113
     114To link from a [trac:SubWiki SubWiki] page to a parent, simply use a '..':
     115{{{
     116  [..] or [[..]]
     117}}}
     118  [..] or [[..]]
     119
     120To link from a [trac:SubWiki SubWiki] page to a [=#sibling sibling] page, use a '../':
     121{{{
     122  [../Sibling see next sibling] or [[../Sibling|see next sibling]]
     123}}}
     124  [../Sibling see next sibling] or [[../Sibling|see next sibling]]
     125
     126But in practice you often won't need to add the `../` prefix to link to a sibling page.
     127For resolving the location of a wiki link, it's the target page closest in the hierarchy to the page where the link is written which will be selected. So for example, within a sub-hierarchy, a sibling page will be targeted in preference to a toplevel page.
     128This makes it easy to copy or move pages to a sub-hierarchy by [[WikiNewPage#renaming|renaming]] without having to adapt the links.
     129
     130To link explicitly to a [=#toplevel toplevel] Wiki page, 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.
     131
     132=== Link anchors
    86133
    87134To create a link to a specific anchor in a page, use '#':
    88135{{{
    89  [#Relativelinks relative links]
    90 }}}
    91 Displays:
    92   [#Relativelinks relative links]
     136 [#Linkanchors Link anchors] or [[#Linkanchors|Link anchors]]
     137}}}
     138  [#Linkanchors Link anchors] or [[#Linkanchors|Link anchors]]
    93139
    94140Hint: 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.
    95141
    96 To create a link to a [trac:SubWiki SubWiki]-page just use a '/':
    97 {{{
    98  WikiPage/SubWikiPage or ./SubWikiPage
    99 }}}
    100 
    101 To link from a [trac:SubWiki SubWiki] page to a parent, simply use a '..':
    102 {{{
    103   [..]
    104 }}}
    105 
    106 To link from a [trac:SubWiki SubWiki] page to a sibling page, use a '../':
    107 {{{
    108   [../Sibling see next sibling]
    109 }}}
    110 
    111 ''(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 now in 0.11 it will stay in the wiki namespace and link to a sibling page. See [#Server-relativelinks] for the new syntax.
    112 
    113 === InterWiki links ===
    114 
    115 Other prefixes can be defined freely and made to point to resources in other Web applications. The definition of those prefixes as well as the URLs of the corresponding Web applications is defined in a special Wiki page, the InterMapTxt page. Note that while this could be used to create links to other Trac environments, there's a more specialized way to register other Trac environments which offers greater flexibility.
    116 
    117 === InterTrac links ===
     142To create a link to the first or last occurrence of a term on a page, use a ''pseudo anchor'' starting with '#/' or '#?':
     143{{{
     144 [#/Milestone first occurrence of Milestone] or
     145 [#?Milestone last occurrence of Milestone]
     146}}}
     147 [#/Milestone first occurrence of Milestone] or
     148 [#?Milestone last occurrence of Milestone]
     149This 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':
     150{{{
     151 [#/Milestone/i first occurrence of Milestone or milestone] or
     152 [#?Milestone/i last occurrence of Milestone or milestone]
     153}}}
     154 [#/Milestone/i first occurrence of Milestone or milestone] or
     155 [#?Milestone/i last occurrence of Milestone or milestone]
     156
     157''(since Trac 1.0)''
     158
     159Such anchors can be very useful for linking to specific lines in a file in the source browser:
     160{{{
     161 [trac:source:tags/trac-0.12/trac/wiki/api.py#L127 Line 127] or
     162 [trac:source:tags/trac-0.12/trac/ticket/roadmap.py#L47 Line 47]
     163}}}
     164 [trac:source:tags/trac-0.12/trac/wiki/api.py#L127 Line 127] or
     165 [trac:source:tags/trac-0.12/trac/ticket/roadmap.py#L47 Line 47]
     166(Hint: The line numbers displayed in the source browser are links to anchors on the respective lines.)
     167
     168Since such links become outdated when the file changes, it can be useful to link using a '#/' pseudo anchor instead:
     169{{{
     170 [trac:source:trunk/trac/wiki/api.py#/IWikiSyntaxProvider IWikiSyntaxProvider] or
     171 [trac:source:trunk/trac/env.py#/ISystemInfoProvider ISystemInfoProvider]
     172}}}
     173 [trac:source:trunk/trac/wiki/api.py#/IWikiSyntaxProvider IWikiSyntaxProvider] or
     174 [trac:source:trunk/trac/env.py#/ISystemInfoProvider ISystemInfoProvider]
     175
     176=== InterWiki links
     177
     178Other prefixes can be defined freely and made to point to resources in other Web applications. The definition of those prefixes as well as the URLs of the corresponding Web applications is defined in a special Wiki page, the InterMapTxt page. Note that while this could be used to create links to other Trac environments, there is a more specialized way to register other Trac environments which offers greater flexibility.
     179
     180=== InterTrac links
    118181
    119182This can be seen as a kind of InterWiki link specialized for targeting other Trac projects.
    120183
    121 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.
    122 
    123 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].
    124 
    125 === Server-relative links ===
    126 
    127 It is often useful to be able to link to objects in your project that
    128 have no built-in Trac linking mechanism, such as static resources, `newticket`,
    129 a shared `/register` page on the server, etc.
    130 
    131 To link to resources inside the project, use either an absolute path from the project root,
    132 or a relative link from the URL of the current page (''Changed in 0.11''):
    133 
    134 {{{
    135 [/newticket Create a new ticket]
    136 [/ home]
    137 }}}
    138 
    139 Display: [/newticket newticket] [/ home]
    140 
    141 To link to another location on the server (outside the project), use the '//location' link syntax (''Changed in 0.11''):
    142 
    143 {{{
    144 [//register Register Here]
    145 }}}
    146 
    147 Display: [//register Register Here]
    148 
    149 === Quoting space in TracLinks ===
    150 
    151 Immediately after a TracLinks prefix, targets containing space characters should
    152 be enclosed in a pair of quotes or double quotes.
     184Any 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.
     185
     186A 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].
     187See InterTrac for the complete details.
     188
     189=== Server-relative links
     190
     191It is often useful to be able to link to objects in your project that have no built-in Trac linking mechanism, such as static resources, `newticket`, a shared `/register` page on the server, etc.
     192
     193To link to resources inside the project, use either an absolute path from the project root, or a relative link from the URL of the current page (''Changed in 0.11''):
     194
     195{{{
     196[/newticket Create a new ticket] or [[//newticket|Create a new ticket]]
     197[/ home] or [[/|home]]
     198}}}
     199
     200Display: [/newticket Create a new ticket] or [[//newticket|Create a new ticket]]
     201[/ home] or [[/|home]]
     202
     203To link to another location on the server (possibly outside the project but on the same host), use the `//` prefix (''Changed in 0.11''):
     204
     205{{{
     206[//register Register Here] or [[//register|Register Here]]
     207}}}
     208
     209Display: [//register Register Here] or [[//register|Register Here]]
     210
     211=== Quoting space in TracLinks
     212
     213Immediately after a TracLinks prefix, targets containing space characters should be enclosed in a pair of quotes or double quotes.
    153214Examples:
    154215 * !wiki:"The whitespace convention"
     
    157218 * !attachment:"the file.txt:ticket:123"
    158219
    159 === Escaping Links ===
     220Note that by using [trac:WikiCreole] style links, it's quite natural to write links containing spaces:
     221 * ![[The whitespace convention]]
     222 * ![[attachment:the file.txt]]
     223
     224=== Escaping Links
    160225
    161226To prevent parsing of a !TracLink, you can escape it by preceding it with a '!' (exclamation mark).
     
    169234 ![42] is not a link either.
    170235
    171 
    172 === Parameterized Trac links ===
    173 
    174 The Trac links target Trac resources which have generally more than one way to be rendered, according to 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.
    175 
    176 Any Trac links can support an arbitrary set of parameters, written in the same way as they would be for the corresponding URL. Some examples:
     236=== Parameterized Trac links
     237
     238Many 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.
     239
     240Trac links can support an arbitrary set of parameters, written in the same way as they would be for the corresponding URL. Some examples:
    177241 - `wiki:WikiStart?format=txt`
    178242 - `ticket:1?version=1`
    179243 - `[/newticket?component=module1 create a ticket for module1]`
    180 
    181 
    182 == TracLinks Reference ==
    183 The following sections describe the individual link types in detail, as well as several notes advanced usage of links.
    184 
    185 === attachment: links ===
     244 - `[/newticket?summary=Add+short+description+here create a ticket with URL with spaces]`
     245
     246== TracLinks Reference
     247
     248The following sections describe the individual link types in detail, as well as notes on advanced usage of links.
     249
     250=== attachment: links
    186251
    187252The link syntax for attachments is as follows:
     
    198263See also [#export:links].
    199264
    200 === comment: links ===
    201 
    202 When you're inside a given tickets, you can simply write e.g. !comment:3 to link to the third change comment.
    203 It's also possible to link to a comment of a specific ticket from anywhere using one of the following syntax:
    204  - !comment:3:ticket:123
    205  - !ticket:123#comment:3 (note that you can't write !#123#!comment:3!)
    206 
    207 === query: links ===
     265=== comment: links
     266
     267When you're inside a given ticket, you can simply write e.g. !comment:3 to link to the third change comment.
     268It is possible to link to a comment of a specific ticket from anywhere using one of the following syntax:
     269 - `comment:3:ticket:123`
     270 - `ticket:123#comment:3` (note that you can't write `#123#!comment:3`!)
     271It is also possible to link to the ticket's description using one of the following syntax:
     272 - `comment:description` (within the ticket)
     273 - `comment:description:ticket:123`
     274 - `ticket:123#comment:description`
     275
     276=== htdocs: links
     277
     278Use `htdocs:path/to/file` to reference files in the `htdocs` directory of the Trac environment, the [TracEnvironment#DirectoryStructure web resource directory].
     279
     280=== query: links
    208281
    209282See TracQuery#UsingTracLinks and [#ticket:links].
    210283
    211 === search: links ===
     284=== search: links
    212285
    213286See TracSearch#SearchLinks
    214287
    215 === ticket: links ===
     288=== ticket: links
     289
     290 ''alias:'' `bug:`
    216291
    217292Besides 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.
     
    221296 - `ticket:1,150`
    222297
    223 ''(since Trac 0.11)''
    224 
    225 === timeline: links ===
    226 
    227 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.
     298=== timeline: links
     299
     300Links 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.
    228301
    229302Examples:
    230303 - `timeline:2008-01-29`
    231304 - `timeline:2008-01-29T15:48`
    232  - `timeline:2008-01-29T16:48Z+01`
    233 
    234 ''(since Trac 0.11)''
    235 
    236 === wiki: links ===
    237 
    238 See WikiPageNames and [#QuotingspaceinTracLinks quoting space in TracLinks] above.
    239 
    240 === Version Control related links ===
    241 ==== source: links ====
    242 
    243 The default behavior for a source:/some/path link is to open the directory browser
    244 if the path points to a directory and otherwise open the log view.
     305 - `timeline:2008-01-29T15:48Z`
     306 - `timeline:2008-01-29T16:48+01`
     307 - `timeline:2008-01-29T16:48+0100`
     308 - `timeline:2008-01-29T16:48+01:00`
     309
     310=== wiki: links
     311
     312See WikiPageNames and [#QuotingspaceinTracLinks quoting space in TracLinks] above. It is possible to create a link to a specific page revision using the syntax WikiStart@1.
     313
     314=== Version Control related links
     315
     316It should be noted that multiple repository support works by creating a kind of virtual namespace for versioned files in which the toplevel folders correspond to the repository names. Therefore, in presence of multiple repositories, a ''/path'' specification in the syntax of links detailed below should start with the name of the repository. If omitted, the default repository is used. In case a toplevel folder of the default repository has the same name as a repository, the latter "wins". One can always access such folder by fully qualifying it. The default repository can be an alias of a named repository, or conversely, it is always possible to create an alias for the default repository, ask your Trac administrator.
     317
     318For example, `source:/trunk/COPYING` targets the path `/trunk/COPYING` in the default repository, whereas `source:/projectA/trunk/COPYING` targets the path `/trunk/COPYING` in the repository named `projectA`. This can be the same file if `'projectA'` is an alias to the default repository or if `''` (the default repository) is an alias to `'projectA'`.
     319
     320==== source: links
     321
     322 ''aliases:'' `browser:`, `repos:`
     323
     324The default behavior for a `source:/some/path link` is to open the browser in that directory directory if the path points to a directory or to show the latest content of the file.
    245325
    246326It's also possible to link directly to a specific revision of a file like this:
    247327 - `source:/some/file@123` - link to the file's revision 123
    248328 - `source:/some/file@head` - link explicitly to the latest revision of the file
     329 - `source:/some/file@named-branch` - link to latest revision of the specified file in `named-branch` (DVCS such as Git or Mercurial)
    249330
    250331If the revision is specified, one can even link to a specific line number:
    251332 - `source:/some/file@123#L10`
    252333 - `source:/tag/0.10@head#L10`
     334 - `source:/some/file@named-branch#L10`
    253335
    254336Finally, one can also highlight an arbitrary set of lines:
    255  - `source:/some/file@123:10-20,100,103#L99` - highlight lines 10 to 20, and lines 100 and 103.
    256 ''(since 0.11)''
    257 
    258 ==== export: links ====
     337 - `source:/some/file@123:10-20,100,103#L99` - highlight lines 10 to 20, and lines 100 and 103, and target line 99
     338 - 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.
     339
     340Note 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)''
     341
     342==== export: links
    259343
    260344To force the download of a file in the repository, as opposed to displaying it in the browser, use the `export` link.  Several forms are available:
     
    262346 * `export:123:/some/file` - get revision 123 of the specified file
    263347 * `export:/some/file@123` - get revision 123 of the specified file
     348 * `export:/some/file@named-branch` - get latest revision of the specified file in `named-branch` (DVCS such as Git or Mercurial).
    264349
    265350This 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.
     
    267352If the path is to a directory in the repository instead of a specific file, the source browser will be used to display the directory (identical to the result of `source:/some/dir`).
    268353
    269 ==== log: links ====
    270 
    271 The `log:` links are used to display revision ranges. In its simplest form, it can link to the latest revisions from the specified path, but it can also support displaying an arbitrary set of revisions.
     354==== log: links
     355
     356The `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.
    272357 - `log:/` - the latest revisions starting at the root of the repository
    273358 - `log:/trunk/tools` - the latest revisions in `trunk/tools`
    274359 - `log:/trunk/tools@10000` - the revisions in `trunk/tools` starting from  revision 10000
    275  - `log:@20788,20791:20795` - list revision 20788 and the 20791 to 20795 revision range
    276  - `log:/trunk/tools@20788,20791:20795` - list revision 20788 and the revisions from the 20791 to 20795 range which affect the given path
     360 - `log:@20788,20791:20795` - list revision 20788 and the revisions from 20791 to 20795
     361 - `log:/trunk/tools@20788,20791:20795` - list revision 20788 and the revisions from 20791 to 20795 which affect the given path
     362 - `log:/tools@named-branch` - the revisions in `tools` starting from the latest revision in `named-branch` (DVCS such as Git or Mercurial)
    277363
    278364There are short forms for revision ranges as well:
     
    281367 - `r20791:20795` (but not `r20788,20791:20795` nor `r20791:20795/trunk`)
    282368
    283 Finally, note that in all of the above, a revision range can be written indifferently `x:y` or `x-y`.
     369Finally, note that in all of the above, a revision range can be written either as `x:y` or `x-y`.
     370
     371In 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]`.
    284372
    285373----