Changes between Version 2 and Version 3 of TracLinks

Timestamp:

12/24/20 10:50:38 (4 years ago)

Author:

trac

Comment:

--

TracLinks

@@ -32 +32 @@
  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`
+          `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), `source:/trunk/COPYING@200:27-30#L25` (at version 200, line 25, highlighting lines 27-30)
@@ -40 +40 @@
  Parent page :: [..]
  Tickets :: #1 or ticket:1
- Ticket comments :: comment:1:ticket:2
+ Ticket comments :: comment:1:ticket:2 
  Reports :: {1} or report:1
  Milestones :: milestone:1.0
@@ -47 +47 @@
  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
+          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) source:/trunk/COPYING@200:28-31#L25 (at version 200, line 25, highlighting lines 28-31)
@@ -78 +78 @@
 }}}
 |--------------------------------------------------------------------------------------
-|||| `wiki` is the default if the namespace part of a full link is omitted:  ||
+|||| `wiki` is the default if the namespace part of a full link is omitted:  || 
 {{{#!td
 {{{
@@ -192 +192 @@
 This can be seen as a kind of InterWiki link specialized for targeting other Trac projects.
 
-Any 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.
+Any 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. 
 
 A distinct advantage of InterTrac links over InterWiki links is that the shorthand form of Trac links can also be used, such as `{}`, `r`, `#`. For example, if T was set as an alias for Trac, then links to Trac tickets can be written as #T234, and links to Trac changesets can be written as [trac 1508].
-See InterTrac for the complete details.
+See InterTrac for the complete details. 
 
 === Server-relative links
@@ -225 +225 @@
  * !wiki:"The whitespace convention"
  * !attachment:'the file.txt' or
- * !attachment:"the file.txt"
- * !attachment:"the file.txt:ticket:123"
+ * !attachment:"the file.txt" 
+ * !attachment:"the file.txt:ticket:123" 
 
 Note that by using [trac:WikiCreole] style links, it's quite natural to write links containing spaces:
@@ -277 +277 @@
 When you're inside a given ticket, you can simply write e.g. !comment:3 to link to the third change comment.
 It is possible to link to a comment of a specific ticket from anywhere using one of the following syntax:
- - `comment:3:ticket:123`
+ - `comment:3:ticket:123` 
  - `ticket:123#comment:3` (note that you can't write `#123#!comment:3`!)
 It is also possible to link to the ticket's description using one of the following syntax:
@@ -302 +302 @@
 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.
 
-Example:
+Example: 
  - `ticket:5000-6000`
  - `ticket:1,150`
@@ -358 +358 @@
  * `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.
+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`).
@@ -368 +368 @@
  - `log:/trunk/tools` - the latest revisions in `trunk/tools`
  - `log:/trunk/tools@10000` - the revisions in `trunk/tools` starting from  revision 10000
- - `log:@20788,20791:20795` - list revision 20788 and the revisions from 20791 to 20795
+ - `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)