Changes between Version 1 and Version 2 of TracLinks
- Timestamp:
- 2007-12-19T17:55:53Z (17 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
TracLinks
v1 v2 1 1 = Trac Links = 2 [[TracGuideToc]] 3 2 4 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 5 … … 10 12 * Ticket comments: '''!comment:ticket:1:2''' 11 13 * Reports: '''!{1}''' or '''!report:1''' 12 * Changesets: '''!r1''', '''![1]''', '''!changeset:1''' or (restricted) '''![1/trunk]''', '''!changeset:1/trunk''' 14 * Changesets: '''!r1''', '''![1]''', '''!changeset:1''' or (restricted) '''![1/trunk]''', '''!changeset:1/trunk''', '''![2:5/trunk]''' 13 15 * Revision log: '''!r1:3''', '''![1:3]''' or '''!log:@1:3''', '''!log:trunk@1:3''' 14 16 * 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''' … … 23 25 * Ticket comments: comment:ticket:1:2 24 26 * Reports: {1} or report:1 25 * Changesets: r1, [1], changeset:1, or (restricted) [1/trunk], changeset:1/trunk 27 * Changesets: r1, [1], changeset:1, or (restricted) [1/trunk], changeset:1/trunk, [2:5/trunk] 26 28 * Revision log: r1:3, [1:3] or log:@1:3, log:trunk@1:3 27 29 * 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 … … 47 49 Display: [ticket:1 This is a link to ticket number one]. 48 50 49 If the title is beomitted, only the id (the part after the colon) is displayed:51 If the title is omitted, only the id (the part after the colon) is displayed: 50 52 51 53 {{{ … … 77 79 78 80 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 81 if the path points to a directory and otherwise open the log view. 82 83 It's also possible to link directly to a specific revision of a file like this: 84 - `source:/some/file@123` - link to the file's revision 123 85 - `source:/some/file@head` - link explicitly to the latest revision of the file 86 87 If the revision is specified, one can even link to a specific line number: 88 - `source:/some/file@123#L10` 89 - `source:/tag/0.10@head#L10` 90 91 Finally, one can also highlight an arbitrary set of lines: 92 - `source:/some/file@123:10-20,100,103#L99` - highlight lines 10 to 20, and lines 100 and 103. 93 ''(since 0.11)'' 94 95 == export: links == 96 97 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: 98 * `export:/some/file` - get the HEAD revision of the specified file 99 * `export:123:/some/file` - get revision 123 of the specified file 100 * `export:/some/file@123` - get revision 123 of the specified file 101 102 This can be very useful for displaying HTML documentation with correct stylesheets and images, in case that has been checked in the repository. 103 104 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`. 83 105 84 106 == search: and query: links ==