| 45 | | In practice though, it's very intuitive and simple to use, and we've found the "link trail" extremely helpful to better understand what's |
| 46 | | happening in a project or why a particular change was made. |
| | 57 | Display: [ticket:1] |
| | 58 | |
| | 59 | `wiki` is the default if the namespace part of a full link is omitted (''since version 0.10''): |
| | 60 | |
| | 61 | {{{ |
| | 62 | [SandBox the sandbox] |
| | 63 | }}} |
| | 64 | |
| | 65 | Display: [SandBox the sandbox] |
| | 66 | |
| | 67 | 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. |
| | 68 | |
| | 69 | The following sections describe the individual link types in detail, as well as several notes advanced usage of links. |
| | 70 | |
| | 71 | == attachment: links == |
| | 72 | |
| | 73 | The link syntax for attachments is as follows: |
| | 74 | * !attachment:the_file.txt creates a link to the attachment the_file.txt of the current object |
| | 75 | * !attachment:wiki:MyPage:the_file.txt creates a link to the attachment the_file.txt of the !MyPage wiki page |
| | 76 | * !attachment:ticket:753:the_file.txt creates a link to the attachment the_file.txt of the ticket 753 |
| 49 | | The default behavior for a source:/some/path link is to open the directory browser if the path points |
| 50 | | to a directory and otherwise open the log view. It's also possible to link directly to a specific |
| 51 | | revision of a file like this: source:/some/file#123 or like this to link to the latest revision: |
| 52 | | source:/some/file#latest. |
| | 79 | |
| | 80 | The default behavior for a source:/some/path link is to open the directory browser |
| | 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`. |
| | 105 | |
| | 106 | == search: and query: links == |
| | 107 | |
| | 108 | See TracSearch#SearchLinks and TracQuery#UsingTracLinks |
| | 109 | |
| | 110 | == !SubWiki links == |
| | 111 | To create a SubWiki link to a SubWiki-page just use a '/': |
| | 112 | {{{ |
| | 113 | [wiki:WikiPage/SubWikiPage]. |
| | 114 | }}} |
| | 115 | |
| | 116 | == InterWiki links == |
| | 117 | |
| | 118 | 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. |
| | 119 | |
| | 120 | == InterTrac links == |
| | 121 | |
| | 122 | Any of the above form of Trac links could be written in one Trac environment and actually refer to resources present in another Trac environment, provided the Trac link is prefixed by the name of that other Trac environment followed by a colon. That other Trac environment must be registered. See InterTrac for details. |
| | 123 | |
| | 124 | |
| | 125 | == Server-relative links == |
| | 126 | |
| | 127 | It is often useful to be able to link to objects on your server that have no built-in |
| | 128 | Trac linking mechanism, such as static resources, a `/register` page, etc. This |
| | 129 | can be achieved by simply using either an absolute path from the server root, |
| | 130 | or a relative link from the URL of the current page: |
| | 131 | |
| | 132 | {{{ |
| | 133 | [../newticket newticket] |
| | 134 | [/ home] |
| | 135 | }}} |
| | 136 | |
| | 137 | Display: [../newticket newticket] [/ home] |
| | 138 | |
| | 139 | == Quoting space in TracLinks == |
| | 140 | |
| | 141 | Immediately after a TracLinks prefix, targets containing space characters should |
| | 142 | be enclosed in a pair of quotes or double quotes. |
| | 143 | Examples: |
| | 144 | * !wiki:"The whitespace convention" |
| | 145 | * !attachment:'the file.txt' or |
| | 146 | * !attachment:"the file.txt" |
| | 147 | * !attachment:"ticket:123:the file.txt" |
