Changes between Initial Version and Version 1 of TracLinks

11/12/08 10:30:00 (14 years ago)
trac (IP:



  • TracLinks

    v0 v1  
     1= Trac Links = 
     4TracLinks 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. 
     6TracLinks are generally of the form '''type:id''' (where ''id'' represents the 
     7number, name or path of the item) though some frequently used kinds of items 
     8also have short-hand notations. 
     10Some examples: 
     11 * Tickets: '''!#1''' or '''!ticket:1''' 
     12 * Ticket comments: '''!comment:ticket:1:2'''  
     13 * Reports: '''!{1}''' or '''!report:1''' 
     14 * Changesets: '''!r1''', '''![1]''', '''!changeset:1''' or (restricted) '''![1/trunk]''', '''!changeset:1/trunk''', '''![2:5/trunk]''' 
     15 * Revision log: '''!r1:3''', '''![1:3]''' or '''!log:@1:3''', '''!log:[email protected]:3''' 
     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/[email protected]//sandbox/[email protected]''' 
     17 * Wiki pages: '''!CamelCase''' or '''!wiki:CamelCase''' 
     18 * Milestones: '''!milestone:1.0''' 
     19 * Attachment: '''!attachment:ticket:944:attachment.1073.diff''' 
     20 * Files: '''!source:trunk/COPYING''' 
     21 * A specific file revision: '''!source:/trunk/[email protected]''' 
     22 * A particular line of a specific file revision: '''!source:/trunk/[email protected]#L25''' 
     24 * Tickets: #1 or ticket:1 
     25 * Ticket comments: comment:ticket:1:2  
     26 * Reports: {1} or report:1 
     27 * Changesets: r1, [1], changeset:1, or (restricted) [1/trunk], changeset:1/trunk, [2:5/trunk] 
     28 * Revision log: r1:3, [1:3] or log:@1:3, log:[email protected]:3 
     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/[email protected]//sandbox/vc-refactoring/[email protected] 
     30 * Wiki pages: CamelCase or wiki:CamelCase 
     31 * Milestones: milestone:1.0 
     32 * Attachment: attachment:ticket:944:attachment.1073.diff 
     33 * Files: source:trunk/COPYING 
     34 * A specific file revision: source:/trunk/[email protected] 
     35 * A particular line of a specific file revision: source:/trunk/[email protected]#L25 
     37'''Note:''' The wiki:CamelCase form is rarely used, but it can be convenient to refer to 
     38pages whose names do not follow WikiPageNames rules, i.e., single words, 
     39non-alphabetic characters, etc. See WikiPageNames for more about features specific 
     40to links to Wiki page names. 
     42Trac links using the full (non-shorthand) notation can also be given a custom 
     43link title like this: 
     46[ticket:1 This is a link to ticket number one]. 
     49Display: [ticket:1 This is a link to ticket number one]. 
     51If the title is omitted, only the id (the part after the colon) is displayed: 
     57Display: [ticket:1] 
     59`wiki` is the default if the namespace part of a full link is omitted (''since version 0.10''): 
     62[SandBox the sandbox] 
     65Display: [SandBox the sandbox] 
     67TracLinks 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. 
     69The following sections describe the individual link types in detail, as well as several notes advanced usage of links. 
     71== attachment: links == 
     73The 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 
     78== source: links == 
     80The default behavior for a source:/some/path link is to open the directory browser  
     81if the path points to a directory and otherwise open the log view. 
     83It's also possible to link directly to a specific revision of a file like this: 
     84 - `source:/some/[email protected]` - link to the file's revision 123 
     85 - `source:/some/[email protected]` - link explicitly to the latest revision of the file 
     87If the revision is specified, one can even link to a specific line number: 
     88 - `source:/some/[email protected]#L10` 
     89 - `source:/tag/[email protected]#L10` 
     91Finally, one can also highlight an arbitrary set of lines: 
     92 - `source:/some/[email protected]:10-20,100,103#L99` - highlight lines 10 to 20, and lines 100 and 103. 
     93''(since 0.11)'' 
     95== export: links == 
     97To 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/[email protected]` - get revision 123 of the specified file 
     102This can be very useful for displaying HTML documentation with correct stylesheets and images, in case that has been checked in the repository. 
     104If 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`. 
     106== search: and query: links == 
     108See TracSearch#SearchLinks and TracQuery#UsingTracLinks 
     110== !SubWiki links == 
     111To create a SubWiki link to a SubWiki-page just use a '/': 
     113 [wiki:WikiPage/SubWikiPage]. 
     116== InterWiki links == 
     118Other 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. 
     120== InterTrac links == 
     122Any 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.  
     125== Server-relative links == 
     127It is often useful to be able to link to objects on your server that have no built-in 
     128Trac linking mechanism, such as static resources, a `/register` page, etc. This 
     129can be achieved by simply using either an absolute path from the server root,  
     130or a relative link from the URL of the current page: 
     133[../newticket newticket] 
     134[/ home] 
     137Display: [../newticket newticket] [/ home] 
     139== Quoting space in TracLinks == 
     141Immediately after a TracLinks prefix, targets containing space characters should 
     142be enclosed in a pair of quotes or double quotes. 
     144 * !wiki:"The whitespace convention" 
     145 * !attachment:'the file.txt' or 
     146 * !attachment:"the file.txt"  
     147 * !attachment:"ticket:123:the file.txt"  
     149== Where to use TracLinks == 
     150You can use TracLinks in: 
     152 * Source code (Subversion) commit messages 
     153 * Wiki pages 
     154 * Full descriptions for tickets, reports and milestones 
     156and any other text fields explicitly marked as supporting WikiFormatting. 
     158== Escaping Links == 
     160To prevent parsing of a !TracLink, you can escape it by preceding it with a '!' (exclamation mark). 
     162 !NoLinkHere. 
     163 ![42] is not a link either. 
     167 !NoLinkHere. 
     168 ![42] is not a link either. 
     171See also: WikiFormatting, TracWiki, WikiPageNames, InterTrac, InterWiki 
RDS Support Home
About PCA
Reference Data Services (RDS)
Meetings and Conferences
ISO 15926
Special Interest Groups
Technical Advisory Board
Norwegian Continental Shelf Std