Changes between Initial Version and Version 1 of TracLinks

Dec 13, 2008, 4:14:33 PM (15 years ago)



  • TracLinks

    v1 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.
     10== Where to use TracLinks ==
     11You can use TracLinks in:
     13 * Source code (Subversion) commit messages
     14 * Wiki pages
     15 * Full descriptions for tickets, reports and milestones
     17and any other text fields explicitly marked as supporting WikiFormatting.
     19Some examples:
     20 * Tickets: '''!#1''' or '''!ticket:1'''
     21 * Ticket comments: '''!comment:ticket:1:2'''
     22 * Reports: '''!{1}''' or '''!report:1'''
     23 * Changesets: '''!r1''', '''![1]''', '''!changeset:1''' or (restricted) '''![1/trunk]''', '''!changeset:1/trunk''', '''![2:5/trunk]'''
     24 * Revision log: '''!r1:3''', '''![1:3]''' or '''!log:@1:3''', '''!log:trunk@1:3'''
     25 * 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'''
     26 * Wiki pages: '''!CamelCase''' or '''!wiki:CamelCase'''
     27 * Parent page: '''![..]'''
     28 * Milestones: '''!milestone:1.0'''
     29 * Attachment: '''!attachment:ticket:944:attachment.1073.diff'''
     30 * Files: '''!source:trunk/COPYING'''
     31 * A specific file revision: '''!source:/trunk/COPYING@200'''
     32 * A particular line of a specific file revision: '''!source:/trunk/COPYING@200#L25'''
     34 * Tickets: #1 or ticket:1
     35 * Ticket comments: comment:ticket:1:2
     36 * Reports: {1} or report:1
     37 * Changesets: r1, [1], changeset:1, or (restricted) [1/trunk], changeset:1/trunk, [2:5/trunk]
     38 * Revision log: r1:3, [1:3] or log:@1:3, log:trunk@1:3
     39 * 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
     40 * Wiki pages: CamelCase or wiki:CamelCase
     41 * Parent page: '''[..]'''
     42 * Milestones: milestone:1.0
     43 * Attachment: attachment:ticket:944:attachment.1073.diff
     44 * Files: source:trunk/COPYING
     45 * A specific file revision: source:/trunk/COPYING@200
     46 * A particular line of a specific file revision: source:/trunk/COPYING@200#L25
     48'''Note:''' The wiki:CamelCase form is rarely used, but it can be convenient to refer to
     49pages whose names do not follow WikiPageNames rules, i.e., single words,
     50non-alphabetic characters, etc. See WikiPageNames for more about features specific
     51to links to Wiki page names.
     53Trac links using the full (non-shorthand) notation can also be given a custom
     54link title like this:
     57[ticket:1 This is a link to ticket number one].
     60Display: [ticket:1 This is a link to ticket number one].
     62If the title is omitted, only the id (the part after the colon) is displayed:
     68Display: [ticket:1]
     70`wiki` is the default if the namespace part of a full link is omitted (''since version 0.10''):
     73[SandBox the sandbox]
     76Display: [SandBox the sandbox]
     78TracLinks 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.
     81== Advanced use of TracLinks ==
     83=== Relative links ===
     85To create a link to a specific anchor in a page, use '#':
     87 [#Relativelinks relative links]
     90  [#Relativelinks relative links]
     92Hint: 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.
     94To create a link to a SubWiki-page just use a '/':
     96 WikiPage/SubWikiPage or ./SubWikiPage
     99To link from a SubWiki page to a parent, simply use a '..':
     101  [..]
     104To link from a SubWiki page to a sibling page, use a '../':
     106  [../Sibling see next sibling]
     109''(Changed in 0.11)'' Note that in Trac 0.10, using e.g. `[../newticket]`  may have worked for linking to the /newticket top-level URL, but now in 0.11 it will stay in the wiki namespace and link to a sibling page. See [#Server-relativelinks] for the new syntax.
     111=== InterWiki links ===
     113Other 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.
     115=== InterTrac links ===
     117This can be seen as a kind of InterWiki link specialized for targeting other Trac projects.
     119Any type 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, under its name or an alias. See InterTrac for details.
     121A distinctive advantage of InterTrac links over InterWiki links is that the shorthand form of Trac links usually have a way to understand the InterTrac prefixes. For example, links to Trac tickets can be written #T234 (if T was set as an alias for Trac), links to Trac changesets can be written [trac 1508].
     123=== Server-relative links ===
     125It is often useful to be able to link to objects in your project that
     126have no built-in Trac linking mechanism, such as static resources, `newticket`,
     127a shared `/register` page on the server, etc.
     129To link to resources inside the project, use either an absolute path from the project root,
     130or a relative link from the URL of the current page (''Changed in 0.11''):
     133[/newticket Create a new ticket]
     134[/ home]
     137Display: [../newticket newticket][[comment(FIXME that's the 0.10 syntax)]]  [/ home]
     139To link to another location on the server (outside the project), use the '//location' link syntax (''Changed in 0.11''):
     142[//register Register Here]
     145Display: [//register Register Here]
     147=== Quoting space in TracLinks ===
     149Immediately after a TracLinks prefix, targets containing space characters should
     150be enclosed in a pair of quotes or double quotes.
     152 * !wiki:"The whitespace convention"
     153 * !attachment:'the file.txt' or
     154 * !attachment:"the file.txt"
     155 * !attachment:"ticket:123:the file.txt"
     157=== Escaping Links ===
     159To prevent parsing of a !TracLink, you can escape it by preceding it with a '!' (exclamation mark).
     161 !NoLinkHere.
     162 ![42] is not a link either.
     166 !NoLinkHere.
     167 ![42] is not a link either.
     170=== Parameterized Trac links ===
     172The Trac links target Trac resources which have generally more than one way to be rendered, according to some extra parameters. For example, a Wiki page can accept a `version` or a `format` parameter, a report can make use of dynamic variables, etc.
     174Any Trac links can support an arbitrary set of parameters, written in the same way as they would be for the corresponding URL. Some examples:
     175 - `wiki:WikiStart?format=txt`
     176 - `ticket:1?version=1`
     177 - `[/newticket?component=module1 create a ticket for module1]`
     180== TracLinks Reference ==
     181The following sections describe the individual link types in detail, as well as several notes advanced usage of links.
     183=== attachment: links ===
     185The link syntax for attachments is as follows:
     186 * !attachment:the_file.txt creates a link to the attachment the_file.txt of the current object
     187 * !attachment:wiki:MyPage:the_file.txt creates a link to the attachment the_file.txt of the !MyPage wiki page
     188 * !attachment:ticket:753:the_file.txt creates a link to the attachment the_file.txt of the ticket 753
     190=== query: links ===
     192See TracQuery#UsingTracLinks and [#ticket:links].
     194=== search: links ===
     196See TracSearch#SearchLinks
     198=== ticket: links ===
     200Besides 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.
     203 - `ticket:5000-6000`
     204 - `ticket:1,150`
     206''(since Trac 0.11)''
     208=== timeline: links ===
     210Links to the timeline can be created by specifying a date in the ISO:8601 format. The date can be optionally followed by a time specification. The time is interpreted as being UTC time, but alternatively you can specify your local time, followed by your timezone if you don't want to compute the UTC time.
     213 - `timeline:2008-01-29`
     214 - `timeline:2008-01-29T15:48`
     215 - `timeline:2008-01-29T16:48Z+01`
     217''(since Trac 0.11)''
     219=== wiki: links ===
     221See WikiPageNames and [#QuotingspaceinTracLinks quoting space in TracLinks] above.
     223=== Version Control related links ===
     224==== source: links ====
     226The default behavior for a source:/some/path link is to open the directory browser
     227if the path points to a directory and otherwise open the log view.
     229It's also possible to link directly to a specific revision of a file like this:
     230 - `source:/some/file@123` - link to the file's revision 123
     231 - `source:/some/file@head` - link explicitly to the latest revision of the file
     233If the revision is specified, one can even link to a specific line number:
     234 - `source:/some/file@123#L10`
     235 - `source:/tag/0.10@head#L10`
     237Finally, one can also highlight an arbitrary set of lines:
     238 - `source:/some/file@123:10-20,100,103#L99` - highlight lines 10 to 20, and lines 100 and 103.
     239''(since 0.11)''
     241==== export: links ====
     243To 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:
     244 * `export:/some/file` - get the HEAD revision of the specified file
     245 * `export:123:/some/file` - get revision 123 of the specified file
     246 * `export:/some/file@123` - get revision 123 of the specified file
     248This can be very useful for displaying HTML documentation with correct stylesheets and images, in case that has been checked in the repository.
     250If 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`.
     252==== log: links ====
     254The `log:` links are used to display revision ranges. In its simplest form, it can link to the latest revisions from the specified path, but it can also support displaying an arbitrary set of revisions.
     255 - `log:/` - the latest revisions starting at the root of the repository
     256 - `log:/trunk/tools` - the latest revisions in `trunk/tools`
     257 - `log:/trunk/tools@10000` - the revisions in `trunk/tools` starting from  revision 10000
     258 - `log:@20788,20791:20795` - list revision 20788 and the 20791 to 20795 revision range
     259 - `log:/trunk/tools@20788,20791:20795` - list revision 20788 and the revisions from the 20791 to 20795 range which affect the given path
     261There are short forms for revision ranges as well:
     262 - `[20788,20791:20795]`
     263 - `[20788,20791:20795/trunk/tools]`
     264 - `r20791:20795` (but not `r20788,20791:20795` nor `r20791:20795/trunk`)
     266Finally, note that in all of the above, a revision range can be written indifferently `x:y` or `x-y`.
     269See also: WikiFormatting, TracWiki, WikiPageNames, InterTrac, InterWiki