Changes between Version 2 and Version 3 of TracLinks

Timestamp:

01/10/14 11:40:42 (11 years ago)

Author:

trac

Comment:

--

TracLinks

@@ -26 +26 @@
  Ticket comments :: `comment:1:ticket:2`
  Reports :: `{1}` or `report:1`
+ Milestones :: `milestone:1.0`
+ Attachment :: `attachment:example.tgz` (for current page attachment), `attachment:attachment.1073.diff:ticket:944` (absolute path)
  Changesets :: `r1`, `[1]`, `changeset:1` or (restricted) `[1/trunk]`, `changeset:1/trunk`
  Revision log :: `r1:3`, `[1:3]` or `log:@1:3`, `log:trunk@1:3`, `[2:5/trunk]`
- Diffs :: `diff:@1:3`, `diff:tags/trac-0.9.2/wiki-default//tags/trac-0.9.3/wiki-default` 
+ Diffs :: `diff:@1:3`, `diff:plugins/0.12/mercurial-plugin@9128:9953`,
+          `diff:tags/trac-0.9.2/wiki-default//tags/trac-0.9.3/wiki-default` 
           or `diff:trunk/trac@3538//sandbox/vc-refactoring@3539`
- Milestones :: `milestone:1.0`
- Attachment :: `attachment:example.tgz` (for current page attachment), `attachment:attachment.1073.diff:ticket:944` (absolute path)
- Files :: `source:trunk/COPYING`
- A specific file revision :: `source:/trunk/COPYING@200`
- A particular line of a specific file revision :: `source:/trunk/COPYING@200#L25`
+ Files :: `source:trunk/COPYING`, `source:/trunk/COPYING@200` (at version 200), `source:/trunk/COPYING@200#L25` (at version 200, line 25)
 }}}
 {{{#!td
@@ -42 +41 @@
  Ticket comments :: comment:1:ticket:2 
  Reports :: {1} or report:1
+ Milestones :: milestone:1.0
+ Attachment :: attachment:example.tgz (for current page attachment), attachment:attachment.1073.diff:ticket:944 (absolute path)
  Changesets :: r1, [1], changeset:1 or (restricted) [1/trunk], changeset:1/trunk
  Revision log :: r1:3, [1:3] or log:@1:3, log:trunk@1:3, [2:5/trunk]
- Diffs :: diff:@1:3, diff:tags/trac-0.9.2/wiki-default//tags/trac-0.9.3/wiki-default 
+ Diffs :: diff:@1:3, diff:plugins/0.12/mercurial-plugin@9128:9953,
+          diff:tags/trac-0.9.2/wiki-default//tags/trac-0.9.3/wiki-default 
           or diff:trunk/trac@3538//sandbox/vc-refactoring@3539
- Milestones :: milestone:1.0
- Attachment :: attachment:example.tgz (for current page attachment), attachment:attachment.1073.diff:ticket:944 (absolute path)
- Files :: source:trunk/COPYING
- A specific file revision :: source:/trunk/COPYING@200
- A particular line of a specific file revision :: source:/trunk/COPYING@200#L25
+ Files :: source:trunk/COPYING, source:/trunk/COPYING@200 (at version 200), source:/trunk/COPYING@200#L25 (at version 200, line 25)
 }}}
 
@@ -111 +109 @@
 
 === Relative links ===
-
-To create a link to a specific anchor in a page, use '#':
-{{{
- [#Relativelinks relative links] or [[#Relativelinks|relative links]]
-}}}
-Displays:
-  [#Relativelinks relative links] or [[#Relativelinks|relative links]]
-
-Hint: 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.
 
 To create a link to a [trac:SubWiki SubWiki]-page just use a '/':
@@ -152 +141 @@
 ''(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 since 0.11, such a link will stay in the wiki namespace and therefore link to a sibling page. 
 See [#Server-relativelinks] for the new syntax.
+
+=== Link anchors ===
+
+To create a link to a specific anchor in a page, use '#':
+{{{
+ [#Linkanchors Link anchors] or [[#Linkanchors|Link anchors]]
+}}}
+  [#Linkanchors Link anchors] or [[#Linkanchors|Link anchors]]
+
+Hint: 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.
+
+To create a link to the first or last occurrence of a term on a page, use a ''pseudo anchor'' starting with '#/' or '#?':
+{{{
+ [#/Milestone first occurrence of Milestone] or
+ [#?Milestone last occurrence of Milestone]
+}}}
+ [#/Milestone first occurrence of Milestone] or
+ [#?Milestone last occurrence of Milestone]
+This will also highlight all other matches on the linked page. By default only case sensitive matches are considered. To include case insensitive matches append '/i':
+{{{
+ [#/Milestone/i first occurrence of Milestone or milestone] or
+ [#?Milestone/i last occurrence of Milestone or milestone]
+}}}
+ [#/Milestone/i first occurrence of Milestone or milestone] or
+ [#?Milestone/i last occurrence of Milestone or milestone]
+
+''(since Trac 1.0)''
+
+Such anchors can be very useful for linking to specific lines in a file in the source browser:
+{{{
+ [trac:source:tags/trac-0.12/trac/wiki/api.py#L127 Line 127] or
+ [trac:source:tags/trac-0.12/trac/ticket/roadmap.py#L47 Line 47]
+}}}
+ [trac:source:tags/trac-0.12/trac/wiki/api.py#L127 Line 127] or
+ [trac:source:tags/trac-0.12/trac/ticket/roadmap.py#L47 Line 47]
+(Hint: The line numbers displayed in the source browser are links to anchors on the respective lines.)
+
+Since such links become outdated when the file changes, it can be useful to link using a '#/' pseudo anchor instead:
+{{{
+ [trac:source:trunk/trac/wiki/api.py#/IWikiSyntaxProvider IWikiSyntaxProvider] or
+ [trac:source:trunk/trac/env.py#/ISystemInfoProvider ISystemInfoProvider]
+}}}
+ [trac:source:trunk/trac/wiki/api.py#/IWikiSyntaxProvider IWikiSyntaxProvider] or
+ [trac:source:trunk/trac/env.py#/ISystemInfoProvider ISystemInfoProvider]
 
 === InterWiki links ===
@@ -258 +291 @@
  - `ticket:123#comment:description`
 
+=== htdocs: links ===
+
+Use `htdocs:path/to/file` to reference files in the `htdocs` directory of the Trac environment, the [TracEnvironment#DirectoryStructure web resource directory].
+
 === query: links ===
 
@@ -291 +328 @@
 === wiki: links ===
 
-See WikiPageNames and [#QuotingspaceinTracLinks quoting space in TracLinks] above.
+See WikiPageNames and [#QuotingspaceinTracLinks quoting space in TracLinks] above. It is possible to create a link to a specific page revision using the syntax WikiStart@1.
 
 === Version Control related links ===
+
+It should be noted that multiple repository support works by creating a kind of virtual namespace for versioned files in which the toplevel folders correspond to the repository names. Therefore, in presence of multiple repositories, a ''/path'' specification in the syntax of links detailed below should start with the name of the repository. If omitted, the default repository is used. In case a toplevel folder of the default repository has the same name as a repository, the latter "wins". One can always access such folder by fully qualifying it (the default repository can be an alias of a named repository, or conversely, it is always possible to create an alias for the default repository, ask your Trac administrator).
+
+For example, `source:/trunk/COPYING` targets the path `/trunk/COPYING` in the default repository, whereas `source:/projectA/trunk/COPYING` targets the path `/trunk/COPYING` in the repository named `projectA`. This can be the same file if `'projectA'` is an alias to the default repository or if `''` (the default repository) is an alias to `'projectA'`.
+
 ==== source: links ====
  ''aliases:'' `browser:`, `repos:`