Changes between Version 1 and Version 2 of TracLinks


Ignore:
Timestamp:
Sep 16, 2005, 12:03:53 AM (15 years ago)
Author:
trac
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • TracLinks

    v1 v2  
    55pages, milestones and source files) from anywhere WikiFormatting is used.
    66
    7 TracLinks are generally of the form '''item:id''' (where ''id'' represents the
     7TracLinks are generally of the form '''type:id''' (where ''id'' represents the
    88number, name or path of the item) though some frequently used kinds of items
    9 also have short-hand, alternative, notations.
     9also have short-hand notations.
    1010
    1111Some examples:
     
    3737}}}
    3838
    39 Display:
     39Display: [ticket:1 This is a link to ticket number one].
    4040
    41 [ticket:1 This is a link to ticket number one].
     41If the title is be omitted, only the id (the part after the colon) is displayed:
    4242
    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}}}
    4446
    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.
     47Display: [ticket:1]
     48
     49It 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.
    4750
    4851== source: links ==
     
    6164and any other text fields explicitly marked as supporting WikiFormatting.
    6265
    63 == Escaping TracLinks ==
     66== Escaping Links ==
     67
    6468To prevent parsing of a !TracLink, you can escape it by preceding it with a '!' (exclamation mark).
    65 
    6669{{{
    6770 !NoLinkHere.