Edgewall Software

Changes between Version 104 and Version 105 of TracLinks


Ignore:
Timestamp:
Oct 15, 2019, 6:36:07 AM (8 weeks ago)
Author:
trac
Comment:

Legend:

Unmodified
Added
Removed
Modified
  • TracLinks

    v104 v105  
    3333 Revision log :: `r1:3`, `[1:3]` or `log:@1:3`, `log:trunk@1:3`, `[2:5/trunk]`
    3434 Diffs :: `diff:@1:3`, `diff:plugins/0.12/mercurial-plugin@9128:9953`,
    35           `diff:tags/trac-0.9.2/wiki-default//tags/trac-0.9.3/wiki-default` 
     35          `diff:tags/trac-0.9.2/wiki-default//tags/trac-0.9.3/wiki-default`
    3636          or `diff:trunk/trac@3538//sandbox/vc-refactoring@3539`
    3737 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)
     
    4141 Parent page :: [..]
    4242 Tickets :: #1 or ticket:1
    43  Ticket comments :: comment:1:ticket:2 
     43 Ticket comments :: comment:1:ticket:2
    4444 Reports :: {1} or report:1
    4545 Milestones :: milestone:1.0
     
    4848 Revision log :: r1:3, [1:3] or log:@1:3, log:trunk@1:3, [2:5/trunk]
    4949 Diffs :: diff:@1:3, diff:plugins/0.12/mercurial-plugin@9128:9953,
    50           diff:tags/trac-0.9.2/wiki-default//tags/trac-0.9.3/wiki-default 
     50          diff:tags/trac-0.9.2/wiki-default//tags/trac-0.9.3/wiki-default
    5151          or diff:trunk/trac@3538//sandbox/vc-refactoring@3539
    5252 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)
     
    7979}}}
    8080|--------------------------------------------------------------------------------------
    81 |||| `wiki` is the default if the namespace part of a full link is omitted:  || 
     81|||| `wiki` is the default if the namespace part of a full link is omitted:  ||
    8282{{{#!td
    8383{{{
     
    193193This can be seen as a kind of InterWiki link specialized for targeting other Trac projects.
    194194
    195 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. 
     195Any 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.
    196196
    197197A 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].
    198 See InterTrac for the complete details. 
     198See InterTrac for the complete details.
    199199
    200200=== Server-relative links
     
    226226 * !wiki:"The whitespace convention"
    227227 * !attachment:'the file.txt' or
    228  * !attachment:"the file.txt" 
    229  * !attachment:"the file.txt:ticket:123" 
     228 * !attachment:"the file.txt"
     229 * !attachment:"the file.txt:ticket:123"
    230230
    231231Note that by using [trac:WikiCreole] style links, it's quite natural to write links containing spaces:
     
    278278When you're inside a given ticket, you can simply write e.g. !comment:3 to link to the third change comment.
    279279It is possible to link to a comment of a specific ticket from anywhere using one of the following syntax:
    280  - `comment:3:ticket:123` 
     280 - `comment:3:ticket:123`
    281281 - `ticket:123#comment:3` (note that you can't write `#123#!comment:3`!)
    282282It is also possible to link to the ticket's description using one of the following syntax:
     
    303303Besides 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.
    304304
    305 Example: 
     305Example:
    306306 - `ticket:5000-6000`
    307307 - `ticket:1,150`
     
    359359 * `export:/some/file@named-branch` - get latest revision of the specified file in `named-branch` (DVCS such as Git or Mercurial).
    360360
    361 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. 
     361This 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.
    362362
    363363If 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`).
     
    369369 - `log:/trunk/tools` - the latest revisions in `trunk/tools`
    370370 - `log:/trunk/tools@10000` - the revisions in `trunk/tools` starting from  revision 10000
    371  - `log:@20788,20791:20795` - list revision 20788 and the revisions from 20791 to 20795 
     371 - `log:@20788,20791:20795` - list revision 20788 and the revisions from 20791 to 20795
    372372 - `log:/trunk/tools@20788,20791:20795` - list revision 20788 and the revisions from 20791 to 20795 which affect the given path
    373373 - `log:/tools@named-branch` - the revisions in `tools` starting from the latest revision in `named-branch` (DVCS such as Git or Mercurial)