Changes between Version 1 and Version 2 of TracLinks


Ignore:
Timestamp:
Feb 13, 2021 12:24:55 AM (4 years ago)
Author:
trac
Comment:

--

Legend:

Unmodified
Added
Removed
Modified

  • TracLinks

    v1 v2  
    1 = Trac Links =
    2 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.
    3 
    4 TracLinks are generally of the form '''type:id''' (where ''id'' represents the
    5 number, name or path of the item) though some frequently used kinds of items
    6 also have short-hand notations.
    7 
    8 Some examples:
    9  * Tickets: '''!#1''' or '''!ticket:1'''
    10  * Ticket comments: '''!comment:ticket:1:2'''
    11  * Reports: '''!{1}''' or '''!report:1'''
    12  * Changesets: '''!r1''', '''![1]''', '''!changeset:1''' or (restricted) '''![1/trunk]''', '''!changeset:1/trunk'''
    13  * Revision log: '''!r1:3''', '''![1:3]''' or '''!log:@1:3''', '''!log:trunk@1:3'''
    14  * 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'''
    15  * Wiki pages: '''!CamelCase''' or '''!wiki:CamelCase'''
    16  * Milestones: '''!milestone:1.0'''
    17  * Attachment: '''!attachment:ticket:944:attachment.1073.diff'''
    18  * Files: '''!source:trunk/COPYING'''
    19  * A specific file revision: '''!source:/trunk/COPYING@200'''
    20  * A particular line of a specific file revision: '''!source:/trunk/COPYING@200#L25'''
    21 Display:
    22  * Tickets: #1 or ticket:1
    23  * Ticket comments: comment:ticket:1:2
    24  * Reports: {1} or report:1
    25  * Changesets: r1, [1], changeset:1, or (restricted) [1/trunk], changeset:1/trunk
    26  * Revision log: r1:3, [1:3] or log:@1:3, log:trunk@1:3
    27  * Diffs (requires [milestone:0.10 0.10]): diff:@20:30, diff:tags/trac-0.9.2/wiki-default//tags/trac-0.9.3/wiki-default or diff:trunk/trac@3538//sandbox/vc-refactoring/trac@3539
    28  * Wiki pages: CamelCase or wiki:CamelCase
    29  * Milestones: milestone:1.0
    30  * Attachment: attachment:ticket:944:attachment.1073.diff
    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 
    35 '''Note:''' The wiki:CamelCase form is rarely used, but it can be convenient to refer to
    36 pages whose names do not follow WikiPageNames rules, i.e., single words,
    37 non-alphabetic characters, etc. See WikiPageNames for more about features specific
    38 to links to Wiki page names.
    39 
    40 Trac links using the full (non-shorthand) notation can also be given a custom
    41 link title like this:
    42 
    43 {{{
    44 [ticket:1 This is a link to ticket number one].
    45 }}}
    46 
    47 Display: [ticket:1 This is a link to ticket number one].
    48 
    49 If the title is be omitted, only the id (the part after the colon) is displayed:
    50 
    51 {{{
    52 [ticket:1]
    53 }}}
    54 
    55 Display: [ticket:1]
    56 
    57 `wiki` is the default if the namespace part of a full link is omitted (''since version 0.10''):
    58 
    59 {{{
    60 [SandBox the sandbox]
    61 }}}
    62 
    63 Display: [SandBox the sandbox]
     1= Trac Links
     2
     3[[TracGuideToc]]
     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
     12You can use TracLinks in:
     13
     14 * Source code (Subversion) commit messages
     15 * Wiki pages
     16 * Full descriptions for tickets, reports and milestones
     17
     18and any other text fields explicitly marked as supporting WikiFormatting.
     19
     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}}}
    64102
    65103TracLinks 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.
    66104
    67 The following sections describe the individual link types in detail, as well as several notes advanced usage of links.
    68 
    69 == attachment: links ==
    70 
    71 The link syntax for attachments is as follows:
    72  * !attachment:the_file.txt creates a link to the attachment the_file.txt of the current object
    73  * !attachment:wiki:MyPage:the_file.txt creates a link to the attachment the_file.txt of the !MyPage wiki page
    74  * !attachment:ticket:753:the_file.txt creates a link to the attachment the_file.txt of the ticket 753
    75 
    76 == source: links ==
    77 
    78 The default behavior for a source:/some/path link is to open the directory browser
    79 if the path points to a directory and otherwise open the log view.
    80 It's also possible to link directly to a specific revision of a file like this: source:/some/file@123
    81 or like this to link to the latest revision: source:/some/file@latest.
    82 If the revision is specified, one can even link to a specific line number: source:/some/file@123#L10
    83 
    84 == search: and query: links ==
    85 
    86 See TracSearch#SearchLinks and TracQuery#UsingTracLinks
    87 
    88 == !SubWiki links ==
    89 To create a SubWiki link to a SubWiki-page just use a '/':
    90 {{{
    91  [wiki:WikiPage/SubWikiPage].
    92 }}}
    93 
    94 == InterWiki links ==
    95 
    96 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.
    97 
    98 == InterTrac links ==
    99 
    100 Any of the above form 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. See InterTrac for details.
    101 
    102 
    103 == Server-relative links ==
    104 
    105 It is often useful to be able to link to objects on your server that have no built-in
    106 Trac linking mechanism, such as static resources, a `/register` page, etc. This
    107 can be achieved by simply using either an absolute path from the server root,
    108 or a relative link from the URL of the current page:
    109 
    110 {{{
    111 [../newticket newticket]
    112 [/ home]
    113 }}}
    114 
    115 Display: [../newticket newticket] [/ home]
    116 
    117 == Quoting space in TracLinks ==
    118 
    119 Immediately after a TracLinks prefix, targets containing space characters should
    120 be enclosed in a pair of quotes or double quotes.
     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
     133
     134To create a link to a specific anchor in a page, use '#':
     135{{{
     136 [#Linkanchors Link anchors] or [[#Linkanchors|Link anchors]]
     137}}}
     138  [#Linkanchors Link anchors] or [[#Linkanchors|Link anchors]]
     139
     140Hint: 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.
     141
     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
     181
     182This can be seen as a kind of InterWiki link specialized for targeting other Trac projects.
     183
     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.
    121214Examples:
    122215 * !wiki:"The whitespace convention"
    123216 * !attachment:'the file.txt' or
    124217 * !attachment:"the file.txt"
    125  * !attachment:"ticket:123:the file.txt"
    126 
    127 == Where to use TracLinks ==
    128 You can use TracLinks in:
    129 
    130  * Source code (Subversion) commit messages
    131  * Wiki pages
    132  * Full descriptions for tickets, reports and milestones
    133 
    134 and any other text fields explicitly marked as supporting WikiFormatting.
    135 
    136 == Escaping Links ==
     218 * !attachment:"the file.txt:ticket:123"
     219
     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
    137225
    138226To prevent parsing of a !TracLink, you can escape it by preceding it with a '!' (exclamation mark).
    … …  
    146234 ![42] is not a link either.
    147235
     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:
     241 - `wiki:WikiStart?format=txt`
     242 - `ticket:1?version=1`
     243 - `[/newticket?component=module1 create a ticket for module1]`
     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
     251
     252The link syntax for attachments is as follows:
     253 * !attachment:the_file.txt creates a link to the attachment the_file.txt of the current object
     254 * !attachment:the_file.txt:wiki:MyPage creates a link to the attachment the_file.txt of the !MyPage wiki page
     255 * !attachment:the_file.txt:ticket:753 creates a link to the attachment the_file.txt of the ticket 753
     256
     257Note that the older way, putting the filename at the end, is still supported: !attachment:ticket:753:the_file.txt.
     258
     259If you'd like to create a direct link to the content of the attached file instead of a link to the attachment page, simply use `raw-attachment:` instead of `attachment:`.
     260
     261This can be useful for pointing directly to an HTML document, for example. Note that for this use case, you'd have to allow the web browser to render the content by setting `[attachment] render_unsafe_content = yes` (see TracIni#attachment-section). Caveat: only do that in environments for which you're 100% confident you can trust the people who are able to attach files, as otherwise this would open up your site to [wikipedia:Cross-site_scripting cross-site scripting] attacks.
     262
     263See also [#export:links].
     264
     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
     281
     282See TracQuery#UsingTracLinks and [#ticket:links].
     283
     284=== search: links
     285
     286See TracSearch#SearchLinks
     287
     288=== ticket: links
     289
     290 ''alias:'' `bug:`
     291
     292Besides 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.
     293
     294Example:
     295 - `ticket:5000-6000`
     296 - `ticket:1,150`
     297
     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.
     301
     302Examples:
     303 - `timeline:2008-01-29`
     304 - `timeline:2008-01-29T15:48`
     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.
     325
     326It's also possible to link directly to a specific revision of a file like this:
     327 - `source:/some/file@123` - link to the file's revision 123
     328 - `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)
     330
     331If the revision is specified, one can even link to a specific line number:
     332 - `source:/some/file@123#L10`
     333 - `source:/tag/0.10@head#L10`
     334 - `source:/some/file@named-branch#L10`
     335
     336Finally, one can also highlight an arbitrary set of lines:
     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
     343
     344To 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:
     345 * `export:/some/file` - get the HEAD revision of the specified file
     346 * `export:123:/some/file` - get revision 123 of the specified file
     347 * `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).
     349
     350This 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.
     351
     352If 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`).
     353
     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.
     357 - `log:/` - the latest revisions starting at the root of the repository
     358 - `log:/trunk/tools` - the latest revisions in `trunk/tools`
     359 - `log:/trunk/tools@10000` - the revisions in `trunk/tools` starting from  revision 10000
     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)
     363
     364There are short forms for revision ranges as well:
     365 - `[20788,20791:20795]`
     366 - `[20788,20791:20795/trunk/tools]`
     367 - `r20791:20795` (but not `r20788,20791:20795` nor `r20791:20795/trunk`)
     368
     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]`.
     372
    148373----
    149374See also: WikiFormatting, TracWiki, WikiPageNames, InterTrac, InterWiki