root/projects/WinDictator/trunk/doc/TracLinks

Revision 19, 6.3 kB (checked in by edsuom, 1 year ago)

Importing windictator into the global FOSS repo

Line 
1 = Trac Links =
2 TracLinks 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.
3
4 TracLinks are generally of the form '''type:id''' (where ''id'' represents the
5 number, name or path of the item) though some frequently used kinds of items
6 also have short-hand notations.
7
8 Some examples:
9  * Tickets: '''!#1''' or '''!ticket:1'''
10  * Ticket comments: '''!comment:ticket:1:2'''
11  * Reports: '''!{1}''' or '''!report:1'''
12  * Changesets: '''!r1''', '''![1]''', '''!changeset:1''' or (restricted) '''![1/trunk]''', '''!changeset:1/trunk'''
13  * Revision log: '''!r1:3''', '''![1:3]''' or '''!log:@1:3''', '''!log:trunk@1:3'''
14  * 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'''
15  * Wiki pages: '''!CamelCase''' or '''!wiki:CamelCase'''
16  * Milestones: '''!milestone:1.0'''
17  * Attachment: '''!attachment:ticket:944:attachment.1073.diff'''
18  * Files: '''!source:trunk/COPYING'''
19  * A specific file revision: '''!source:/trunk/COPYING@200'''
20  * A particular line of a specific file revision: '''!source:/trunk/COPYING@200#L25'''
21 Display:
22  * Tickets: #1 or ticket:1
23  * Ticket comments: comment:ticket:1:2
24  * Reports: {1} or report:1
25  * Changesets: r1, [1], changeset:1, or (restricted) [1/trunk], changeset:1/trunk
26  * Revision log: r1:3, [1:3] or log:@1:3, log:trunk@1:3
27  * 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
28  * Wiki pages: CamelCase or wiki:CamelCase
29  * Milestones: milestone:1.0
30  * Attachment: attachment:ticket:944:attachment.1073.diff
31  * Files: source:trunk/COPYING
32  * A specific file revision: source:/trunk/COPYING@200
33  * A particular line of a specific file revision: source:/trunk/COPYING@200#L25
34
35 '''Note:''' The wiki:CamelCase form is rarely used, but it can be convenient to refer to
36 pages whose names do not follow WikiPageNames rules, i.e., single words,
37 non-alphabetic characters, etc. See WikiPageNames for more about features specific
38 to links to Wiki page names.
39
40 Trac links using the full (non-shorthand) notation can also be given a custom
41 link title like this:
42
43 {{{
44 [ticket:1 This is a link to ticket number one].
45 }}}
46
47 Display: [ticket:1 This is a link to ticket number one].
48
49 If the title is be omitted, only the id (the part after the colon) is displayed:
50
51 {{{
52 [ticket:1]
53 }}}
54
55 Display: [ticket:1]
56
57 `wiki` is the default if the namespace part of a full link is omitted (''since version 0.10''):
58
59 {{{
60 [SandBox the sandbox]
61 }}}
62
63 Display: [SandBox the sandbox]
64
65 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.
66
67 The following sections describe the individual link types in detail, as well as several notes advanced usage of links.
68
69 == attachment: links ==
70
71 The link syntax for attachments is as follows:
72  * !attachment:the_file.txt creates a link to the attachment the_file.txt of the current object
73  * !attachment:wiki:MyPage:the_file.txt creates a link to the attachment the_file.txt of the !MyPage wiki page
74  * !attachment:ticket:753:the_file.txt creates a link to the attachment the_file.txt of the ticket 753
75
76 == source: links ==
77
78 The default behavior for a source:/some/path link is to open the directory browser
79 if the path points to a directory and otherwise open the log view.
80 It's also possible to link directly to a specific revision of a file like this: source:/some/file@123
81 or like this to link to the latest revision: source:/some/file@latest.
82 If the revision is specified, one can even link to a specific line number: source:/some/file@123#L10
83
84 == search: and query: links ==
85
86 See TracSearch#SearchLinks and TracQuery#UsingTracLinks
87
88 == !SubWiki links ==
89 To create a SubWiki link to a SubWiki-page just use a '/':
90 {{{
91  [wiki:WikiPage/SubWikiPage].
92 }}}
93
94 == InterWiki links ==
95
96 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.
97
98 == InterTrac links ==
99
100 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.
101
102
103 == Server-relative links ==
104
105 It is often useful to be able to link to objects on your server that have no built-in
106 Trac linking mechanism, such as static resources, a `/register` page, etc. This
107 can be achieved by simply using either an absolute path from the server root,
108 or a relative link from the URL of the current page:
109
110 {{{
111 [../newticket newticket]
112 [/ home]
113 }}}
114
115 Display: [../newticket newticket] [/ home]
116
117 == Quoting space in TracLinks ==
118
119 Immediately after a TracLinks prefix, targets containing space characters should
120 be enclosed in a pair of quotes or double quotes.
121 Examples:
122  * !wiki:"The whitespace convention"
123  * !attachment:'the file.txt' or
124  * !attachment:"the file.txt"
125  * !attachment:"ticket:123:the file.txt"
126
127 == Where to use TracLinks ==
128 You can use TracLinks in:
129
130  * Source code (Subversion) commit messages
131  * Wiki pages
132  * Full descriptions for tickets, reports and milestones
133
134 and any other text fields explicitly marked as supporting WikiFormatting.
135
136 == Escaping Links ==
137
138 To prevent parsing of a !TracLink, you can escape it by preceding it with a '!' (exclamation mark).
139 {{{
140  !NoLinkHere.
141  ![42] is not a link either.
142 }}}
143
144 Display:
145  !NoLinkHere.
146  ![42] is not a link either.
147
148 ----
149 See also: WikiFormatting, TracWiki, WikiPageNames, InterTrac, InterWiki
150  
Note: See TracBrowser for help on using the browser.