Changes between Version 1 and Version 2 of TracLinks
- Timestamp:
- Sep 16, 2005, 12:03:53 AM (19 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
TracLinks
v1 v2 5 5 pages, milestones and source files) from anywhere WikiFormatting is used. 6 6 7 TracLinks are generally of the form ''' item:id''' (where ''id'' represents the7 TracLinks are generally of the form '''type:id''' (where ''id'' represents the 8 8 number, name or path of the item) though some frequently used kinds of items 9 also have short-hand , alternative, notations.9 also have short-hand notations. 10 10 11 11 Some examples: … … 37 37 }}} 38 38 39 Display: 39 Display: [ticket:1 This is a link to ticket number one]. 40 40 41 [ticket:1 This is a link to ticket number one]. 41 If the title is be omitted, only the id (the part after the colon) is displayed: 42 42 43 It might seem a simple enough concept at a glance, but actually allows quite a complex network of information. 43 {{{ 44 [ticket:1] 45 }}} 44 46 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. 47 Display: [ticket:1] 48 49 It might seem a simple enough concept at a glance, but actually allows 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. 47 50 48 51 == source: links == … … 61 64 and any other text fields explicitly marked as supporting WikiFormatting. 62 65 63 == Escaping TracLinks == 66 == Escaping Links == 67 64 68 To prevent parsing of a !TracLink, you can escape it by preceding it with a '!' (exclamation mark). 65 66 69 {{{ 67 70 !NoLinkHere.