Changes between Version 6 and Version 7 of TracLinks


Ignore:
Timestamp:
10/12/21 10:39:25 (3 years ago)
Author:
trac
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • TracLinks

    v6 v7  
    3232 Revision log :: `r1:3`, `[1:3]` or `log:@1:3`, `log:trunk@1:3`, `[2:5/trunk]`
    3333 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` 
     34          `diff:tags/trac-0.9.2/wiki-default//tags/trac-0.9.3/wiki-default`
    3535          or `diff:trunk/trac@3538//sandbox/vc-refactoring@3539`
    3636 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)
     
    4040 Parent page :: [..]
    4141 Tickets :: #1 or ticket:1
    42  Ticket comments :: comment:1:ticket:2 
     42 Ticket comments :: comment:1:ticket:2
    4343 Reports :: {1} or report:1
    4444 Milestones :: milestone:1.0
     
    4747 Revision log :: r1:3, [1:3] or log:@1:3, log:trunk@1:3, [2:5/trunk]
    4848 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 
     49          diff:tags/trac-0.9.2/wiki-default//tags/trac-0.9.3/wiki-default
    5050          or diff:trunk/trac@3538//sandbox/vc-refactoring@3539
    5151 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)
     
    7878}}}
    7979|--------------------------------------------------------------------------------------
    80 |||| `wiki` is the default if the namespace part of a full link is omitted:  || 
     80|||| `wiki` is the default if the namespace part of a full link is omitted:  ||
    8181{{{#!td
    8282{{{
     
    135135
    136136But in practice you often won't need to add the `../` prefix to link to a sibling page.
    137 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.
     137For 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 top-level page.
    138138This makes it easy to copy or move pages to a sub-hierarchy by [[WikiNewPage#renaming|renaming]] without having to adapt the links.
    139139
     
    148148  [#Linkanchors Link anchors] or [[#Linkanchors|Link anchors]]
    149149
    150 Hint: 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.
     150Hint: when you hover 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.
    151151
    152152To create a link to the first or last occurrence of a term on a page, use a ''pseudo anchor'' starting with '#/' or '#?':
     
    192192This can be seen as a kind of InterWiki link specialized for targeting other Trac projects.
    193193
    194 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. 
    195 
    196 A 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].
    197 See InterTrac for the complete details. 
     194Any 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.
     195
     196A 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].
     197See InterTrac for the complete details.
    198198
    199199=== Server-relative links
     
    225225 * !wiki:"The whitespace convention"
    226226 * !attachment:'the file.txt' or
    227  * !attachment:"the file.txt" 
    228  * !attachment:"the file.txt:ticket:123" 
     227 * !attachment:"the file.txt"
     228 * !attachment:"the file.txt:ticket:123"
    229229
    230230Note that by using [trac:WikiCreole] style links, it's quite natural to write links containing spaces:
     
    277277When you're inside a given ticket, you can simply write e.g. !comment:3 to link to the third change comment.
    278278It is possible to link to a comment of a specific ticket from anywhere using one of the following syntax:
    279  - `comment:3:ticket:123` 
     279 - `comment:3:ticket:123`
    280280 - `ticket:123#comment:3` (note that you can't write `#123#!comment:3`!)
    281281It is also possible to link to the ticket's description using one of the following syntax:
     
    302302Besides 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.
    303303
    304 Example: 
     304Example:
    305305 - `ticket:5000-6000`
    306306 - `ticket:1,150`
     
    358358 * `export:/some/file@named-branch` - get latest revision of the specified file in `named-branch` (DVCS such as Git or Mercurial).
    359359
    360 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. 
     360This 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.
    361361
    362362If 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`).
     
    368368 - `log:/trunk/tools` - the latest revisions in `trunk/tools`
    369369 - `log:/trunk/tools@10000` - the revisions in `trunk/tools` starting from  revision 10000
    370  - `log:@20788,20791:20795` - list revision 20788 and the revisions from 20791 to 20795 
     370 - `log:@20788,20791:20795` - list revision 20788 and the revisions from 20791 to 20795
    371371 - `log:/trunk/tools@20788,20791:20795` - list revision 20788 and the revisions from 20791 to 20795 which affect the given path
    372372 - `log:/tools@named-branch` - the revisions in `tools` starting from the latest revision in `named-branch` (DVCS such as Git or Mercurial)