Context Navigation

Changes between Version 2 and Version 3 of TracLinks

Timestamp:: Jan 13, 2020, 11:35:39 PM (5 years ago)
Author:: trac
Comment:: --

Legend:

: Unmodified
: Added
: Removed
: Modified

TracLinks

-              v2
+              v3
+= Trac Links =
+= Trac Links
 [[TracGuideToc]]
+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.
+TracLinks 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.
+== Where to use TracLinks ==
+[[PageOutline(2-5,Contents,pullout)]]
+TracLinks are a fundamental feature of Trac, allowing 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.
+TracLinks 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.
+== Where to use TracLinks
 You can use TracLinks in:
 …
 and any other text fields explicitly marked as supporting WikiFormatting.
 == Overview ==
+== Overview
 ||= Wiki Markup =||= Display =||
 …
  Milestones :: `milestone:1.0`
  Attachment :: `attachment:example.tgz` (for current page attachment), `attachment:attachment.1073.diff:ticket:944` (absolute path)
  Changesets :: `r1`, `[1]`, `changeset:1` or (restricted) `[1/trunk]`, `changeset:1/trunk`
+ Changesets :: `r1`, `[1]`, `changeset:1` or (restricted) `[1/trunk]`, `changeset:1/trunk`, `[1/repository]`
  Revision log :: `r1:3`, `[1:3]` or `log:@1:3`, `log:trunk@1:3`, `[2:5/trunk]`
  Diffs :: `diff:@1:3`, `diff:plugins/0.12/mercurial-plugin@9128:9953`,
           `diff:tags/trac-0.9.2/wiki-default//tags/trac-0.9.3/wiki-default`
           or `diff:trunk/trac@3538//sandbox/vc-refactoring@3539`
  Files :: `source:trunk/COPYING`, `source:/trunk/COPYING@200` (at version 200), `source:/trunk/COPYING@200#L25` (at version 200, line 25)
+ Files :: `source:trunk/COPYING`, `source:/trunk/COPYING@200` (at version 200), `source:/trunk/COPYING@200#L25` (at version 200, line 25), `source:/trunk/COPYING@200:27-30#L25` (at version 200, line 25, highlighting lines 27-30)
 }}}
 {{{#!td
 …
  Milestones :: milestone:1.0
  Attachment :: attachment:example.tgz (for current page attachment), attachment:attachment.1073.diff:ticket:944 (absolute path)
  Changesets :: r1, [1], changeset:1 or (restricted) [1/trunk], changeset:1/trunk
+ Changesets :: r1, [1], changeset:1 or (restricted) [1/trunk], changeset:1/trunk, [1/repository]
  Revision log :: r1:3, [1:3] or log:@1:3, log:trunk@1:3, [2:5/trunk]
  Diffs :: diff:@1:3, diff:plugins/0.12/mercurial-plugin@9128:9953,
           diff:tags/trac-0.9.2/wiki-default//tags/trac-0.9.3/wiki-default
           or diff:trunk/trac@3538//sandbox/vc-refactoring@3539
+ Files :: source:trunk/COPYING, source:/trunk/COPYING@200 (at version 200), source:/trunk/COPYING@200#L25 (at version 200, line 25)
+}}}
+'''Note:''' The wiki:CamelCase form is rarely used, but it can be convenient to refer to
+pages whose names do not follow WikiPageNames rules, i.e., single words,
+non-alphabetic characters, etc. See WikiPageNames for more about features specific
+to links to Wiki page names.
+ Files :: source:trunk/COPYING, source:/trunk/COPYING@200 (at version 200), source:/trunk/COPYING@200#L25 (at version 200, line 25) source:/trunk/COPYING@200:28-31#L25 (at version 200, line 25, highlighting lines 28-31)
+}}}
+'''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.
 …
 <wiki:Strange(page@!)>
 }}}
+|--------------------------------------------------------------------------------------
+|||| Quoting can be used with the full notation to allow brackets in the label. ||
+{{{#!td
+{{{
+[TracIni#logging-log_type-option "[logging] log_type"]
+}}}
+}}}
+{{{#!td
+[TracIni#logging-log_type-option "[logging] log_type"]
+}}}
 }}}
 TracLinks 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.
+== Advanced use of TracLinks ==
+=== Relative links ===
+== Advanced use of TracLinks
+=== Relative links
 To create a link to a [trac:SubWiki SubWiki]-page just use a '/':
 …
 But in practice you often won't need to add the `../` prefix to link to a sibling page.
+For 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.
+For 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.
 This makes it easy to copy or move pages to a sub-hierarchy by [[WikiNewPage#renaming|renaming]] without having to adapt the links.
+In order to 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.
+''(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.
+See [#Server-relativelinks] for the new syntax.
+=== Link anchors ===
+To 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.
+=== Link anchors
 To create a link to a specific anchor in a page, use '#':
 …
  [trac:source:trunk/trac/env.py#/ISystemInfoProvider ISystemInfoProvider]
 === InterWiki links ===
 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.
 === InterTrac links ===
+=== InterWiki links
+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 is a more specialized way to register other Trac environments which offers greater flexibility.
+=== InterTrac links
 This can be seen as a kind of InterWiki link specialized for targeting other Trac projects.
 …
 See InterTrac for the complete details.
+=== Server-relative links ===
+It 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.
+To 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''):
+=== Server-relative links
+It 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.
+To 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''):
 {{{
 …
 Display: [//register Register Here] or [[//register|Register Here]]
+=== Quoting space in TracLinks ===
+Immediately after a TracLinks prefix, targets containing space characters should
+be enclosed in a pair of quotes or double quotes.
+=== Quoting space in TracLinks
+Immediately after a TracLinks prefix, targets containing space characters should be enclosed in a pair of quotes or double quotes.
 Examples:
  * !wiki:"The whitespace convention"
 …
  * ![[attachment:the file.txt]]
 === Escaping Links ===
+=== Escaping Links
 To prevent parsing of a !TracLink, you can escape it by preceding it with a '!' (exclamation mark).
 …
  ![42] is not a link either.
+=== Parameterized Trac links ===
+=== Parameterized Trac links
 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.
 …
  - `[/newticket?summary=Add+short+description+here create a ticket with URL with spaces]`
+== TracLinks Reference ==
+== TracLinks Reference
 The following sections describe the individual link types in detail, as well as notes on advanced usage of links.
 === attachment: links ===
+=== attachment: links
 The link syntax for attachments is as follows:
  * !attachment:the_file.txt creates a link to the attachment the_file.txt of the current object
+ * !attachment:the_file.txt creates a link to the attachment the_file.txt of the current page
  * !attachment:the_file.txt:wiki:MyPage creates a link to the attachment the_file.txt of the !MyPage wiki page
  * !attachment:the_file.txt:ticket:753 creates a link to the attachment the_file.txt of the ticket 753
 Note that the older way, putting the filename at the end, is still supported: !attachment:ticket:753:the_file.txt.
+Note that the older way, putting the filename at the end, is still supported: !attachment:ticket:753:the_file.txt, but is not recommended.
 If 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:`.
 This 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.
+This 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 [[TracIni#attachment-render_unsafe_content-option|"[attachment] render_unsafe_content"]] = `enabled`. Caveat: only do that in environments for which you're 100% confident you can trust the people who are able to attach files, as this opens up your site to [wikipedia:Cross-site_scripting cross-site scripting] attacks.
 See also [#export:links].
 === comment: links ===
+=== comment: links
 When you're inside a given ticket, you can simply write e.g. !comment:3 to link to the third change comment.
 …
  - `ticket:123#comment:description`
 === htdocs: links ===
+=== htdocs: links
 Use `htdocs:path/to/file` to reference files in the `htdocs` directory of the Trac environment, the [TracEnvironment#DirectoryStructure web resource directory].
 === query: links ===
+=== query: links
 See TracQuery#UsingTracLinks and [#ticket:links].
+=== search: links ===
+See TracSearch#SearchLinks
+=== ticket: links ===
+ ''alias:'' `bug:`
+=== search: links
+See TracSearch#SearchTracLinks
+=== ticket: links
+ ''aliases:'' `bug:`, `issue:`
 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.
 …
  - `ticket:1,150`
+''(since Trac 0.11)''
+=== timeline: links ===
+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.
+=== timeline: links
+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 if you don't want to compute the UTC time, you can specify a local time followed by your timezone offset relative to UTC.
 Examples:
 …
  - `timeline:2008-01-29T15:48Z`
  - `timeline:2008-01-29T16:48+01`
+''(since Trac 0.11)''
 === wiki: links ===
+ - `timeline:2008-01-29T16:48+0100`
+ - `timeline:2008-01-29T16:48+01:00`
+=== wiki: links
 See 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.
 === Version Control related links ===
 It 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).
+=== Version Control system links
+It 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 link directs to the latter. One can always access such folder by fully qualifying it. The default repository can be an alias of a named repository, or conversely, there may be one or more aliases for the default repository, ask your Trac administrator.
 For 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'`.
+==== source: links ====
+==== source: links
  ''aliases:'' `browser:`, `repos:`
+The 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.
+The 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.
 It's also possible to link directly to a specific revision of a file like this:
  - `source:/some/file@123` - link to the file's revision 123
  - `source:/some/file@head` - link explicitly to the latest revision of the file
+ - `source:/some/file@named-branch` - link to latest revision of the specified file in `named-branch` (DVCS such as Git or Mercurial)
 If the revision is specified, one can even link to a specific line number:
  - `source:/some/file@123#L10`
  - `source:/tag/0.10@head#L10`
+ - `source:/some/file@named-branch#L10`
 Finally, one can also highlight an arbitrary set of lines:
  - `source:/some/file@123:10-20,100,103#L99` - highlight lines 10 to 20, and lines 100 and 103.
    ''(since 0.11)''
+ - `source:/some/file@123:10-20,100,103#L99` - highlight lines 10 to 20, and lines 100 and 103, and target line 99
+ - 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.
 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)''
 ==== export: links ====
+==== export: links
 To 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:
 …
  * `export:123:/some/file` - get revision 123 of the specified file
  * `export:/some/file@123` - get revision 123 of the specified file
+This 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.
+ * `export:/some/file@named-branch` - get latest revision of the specified file in `named-branch` (DVCS such as Git or Mercurial).
+This 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 [[TracIni#browser-render_unsafe_content-option|"[browser] render_unsafe_content"]] = `enabled`, otherwise Trac will force the files to be downloaded as attachments for security concerns.
 If 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`).
 ==== log: links ====
+==== log: links
 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.
 …
  - `log:@20788,20791:20795` - list revision 20788 and the revisions from 20791 to 20795
  - `log:/trunk/tools@20788,20791:20795` - list revision 20788 and the revisions from 20791 to 20795 which affect the given path
+ - `log:/tools@named-branch` - the revisions in `tools` starting from the latest revision in `named-branch` (DVCS such as Git or Mercurial)
 There are short forms for revision ranges as well:
 …
 Finally, note that in all of the above, a revision range can be written either as `x:y` or `x-y`.
+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]`.
+==== Multi-repository links
+In the presence of multiple repositories, the name of the repository should be specified as the first part of the path:
+- `log:repos/branch`
+- `[20-40/repos]`
+- `r20/repos`
 ----
 See also: WikiFormatting, TracWiki, WikiPageNames, InterTrac, InterWiki