close
Warning:
Can't synchronize with repository "(default)" (/var/lib/svn/mod_papi does not appear to be a Subversion repository.). Look in the Trac log for more information.
- Timestamp:
-
Apr 20, 2011, 12:03:00 PM (15 years ago)
- Author:
-
trac
- Comment:
-
--
Legend:
- Unmodified
- Added
- Removed
- Modified
-
|
v1
|
v2
|
|
| 30 | 30 | The prefix is case insensitive. |
| 31 | 31 | |
| | 32 | When a TracLink is enclosed in brackets, the alias is expanded. That is, `[th:ticket:1]` is displayed as `trachacks:ticket:1`, since `th` is an alias for `trachacks`. If the TracLink is not enclosed in brackets, then the alias is displayed as it is typed. |
| | 33 | |
| 32 | 34 | For convenience, there's also some alternative short-hand form, |
| 33 | 35 | where one can use an alias as an immediate prefix |
| … |
… |
|
| 36 | 38 | |
| 37 | 39 | == Examples == |
| 38 | | |
| 39 | | {{{ |
| 40 | | #!comment |
| 41 | | Besides the other environments run by the same server process |
| 42 | | (called ''sibling'' environments), which are automatically detected, |
| 43 | | Support for sibling environments has been disabled. |
| 44 | | See http://thread.gmane.org/gmane.comp.version-control.subversion.trac.devel/157 |
| 45 | | }}} |
| 46 | 40 | |
| 47 | 41 | It is necessary to setup a configuration for the InterTrac facility. |
| … |
… |
|
| 57 | 51 | # -- Link to an external Trac: |
| 58 | 52 | trac.title = Edgewall's Trac for Trac |
| 59 | | trac.url = http://projects.edgewall.com/trac |
| 60 | | trac.compat = false |
| | 53 | trac.url = http://trac.edgewall.org |
| 61 | 54 | }}} |
| 62 | 55 | |
| … |
… |
|
| 69 | 62 | |
| 70 | 63 | Finally, the `.compat` option can be used to activate or disable |
| 71 | | a ''compatbility'' mode: |
| 72 | | * If the targeted Trac is running a version below milestone:0.10 |
| 73 | | (r3526 to be precise), then it doesn't know how to dispatch an InterTrac |
| | 64 | a ''compatibility'' mode: |
| | 65 | * If the targeted Trac is running a version below [trac:milestone:0.10 0.10] |
| | 66 | ([trac:r3526 r3526] to be precise), then it doesn't know how to dispatch an InterTrac |
| 74 | 67 | link, and it's up to the local Trac to prepare the correct link. |
| 75 | 68 | Not all links will work that way, but the most common do. |
| 76 | 69 | This is called the compatibility mode, and is `true` by default. |
| 77 | 70 | * If you know that the remote Trac knows how to dispatch InterTrac links, |
| 78 | | you can explicitely disable this compatibility mode and then ''any'' |
| | 71 | you can explicitly disable this compatibility mode and then ''any'' |
| 79 | 72 | TracLinks can become an InterTrac link. |
| 80 | 73 | |
| … |
… |
|
| 94 | 87 | * `trac:log:@3300:3330` trac:log:@3300:3330 |
| 95 | 88 | * `[trac 3300:3330]` [trac 3300:3330] |
| | 89 | * finally, to link to the start page of a remote trac, simply use its prefix followed by ':', inside an explicit link. Example: `[th: Trac Hacks]` (''since 0.11; note that the ''remote'' Trac has to run 0.11 for this to work'') |
| 96 | 90 | |
| 97 | 91 | The generic form `intertrac_prefix:module:id` is translated |
| … |
… |
|
| 102 | 96 | |
| 103 | 97 | ---- |
| 104 | | === Discussion === |
| 105 | | |
| 106 | | I think that the `trac` prefix could even be set as a default in the `[intertrac]` TracIni section. --CB |
| 107 | | |
| 108 | | ---- |
| 109 | 98 | See also: TracLinks, InterWiki |