| 4 | | The Trac repository browser can be used to browse directories |
| 5 | | and specific revisions of files stored in the repository of the configured |
| 6 | | version control system. |
| | 4 | The Trac repository browser can be used to browse specific revisions of directories |
| | 5 | and files stored in the repositories associated with the Trac environment. |
| | 6 | |
| | 7 | ''(since 0.12)'': |
| | 8 | At the top-level of the repository browser is the '''Repository Index''', |
| | 9 | listing all the configured repositories. |
| | 10 | Each repository has a name which is used as a path prefix in a |
| | 11 | "virtual" file hierarchy encompassing all the available repositories. |
| | 12 | One of the repositories can be configured with an empty name; this is the default repository. When such a default repository is present, its top-level files and directories |
| | 13 | are also listed, in a '''Default Repository''' section placed before the |
| | 14 | repository index. If the default repository is the only repository associated |
| | 15 | with the Trac environment the '''Repository Index''' will be omitted ^[#note-multirepos (1)]^. |
| 14 | | by clicking on the directory names. Clicking on a file name will show |
| 15 | | the contents of the file. Clicking on the revision number of a file or |
| 16 | | directory will take you to the TracRevisionLog for that file. |
| 17 | | Note that there's also a ''Revision Log'' navigation link that will do |
| 18 | | the same for the path currently being examined. |
| | 23 | by clicking on the directory names. |
| | 24 | Clicking on a file name will show the contents of the file. |
| | 25 | Clicking on the revision number of a file or directory will take |
| | 26 | you to the TracRevisionLog for that file. |
| | 27 | Note that there's also a ''Revision Log'' navigation link that will do the |
| | 28 | same for the path currently being examined. |
| | 29 | Clicking on the ''diff'' icon after revision number will display the changes made |
| | 30 | to the files modified in that revision. |
| | 31 | Clicking on the ''Age'' of the file - will take you to that changeset in the timeline. |
| 34 | | The precise meaning and content of this menu depends on your backend. |
| 35 | | For Subversion, this list contains by default a few branches (`trunk` and any sub-folder of the latest `branches` top-level folder) and a few tags (any sub-folder of the latest `tags` top-level folder). This can be [TracIni#svn-section configured] for more advanced cases. |
| | 46 | The precise meaning and content of this menu depends on your repository backend. |
| | 47 | For Subversion, this list contains by default the top-level trunk directory |
| | 48 | and sub-directories of the top-level branches and tags directories |
| | 49 | (`/trunk`, `/branches/*`, and `/tags/*`). This can be [TracIni#svn-section configured] |
| | 50 | for more advanced cases. |
| 37 | | If you're using a Javascript enabled brower, you'll be able to expand and collapse folders in-place by clicking on the arrow head at the right side of a folder. Alternatively, the [trac:TracKeys keyboard] can also be used for this: use 'j' and 'k' to go to the next or previous entry, and 'o' (or 'Enter') to toggle between expanded and collapsed state of the selected folder or for visiting the selected file. |
| | 52 | If you're using a Javascript enabled browser, you'll be able to expand and |
| | 53 | collapse directories in-place by clicking on the arrow head at the right side of a |
| | 54 | directory. Alternatively, the [trac:TracKeys keyboard] can also be used for this: |
| | 55 | - use `j` and `k` to select the next or previous entry, starting with the first |
| | 56 | - `o` ('''o'''pen) to toggle between expanded and collapsed state of the selected |
| | 57 | directory or for visiting the selected file |
| | 58 | - `v` ('''v'''iew, '''v'''isit) and `<Enter>`, same as above |
| | 59 | - `r` can be used to force the '''r'''eload of an already expanded directory |
| | 60 | - `a` can be used to directly visit a file in '''a'''nnotate (blame) mode |
| | 61 | - `l` to view the '''l'''og for the selected entry |
| | 62 | If no row has been selected using `j` or `k` these keys will operate on the entry under the mouse. |
| 39 | | For the Subversion backend, some additional features are available: |
| 40 | | - Support for the `svn:needs-lock` property |
| 41 | | - Support for the `svn:externals` property (which can be [TracIni#svn:externals-section configured]) |
| 42 | | - The `svn:mime-type` property is used to select the syntax highlighter for rendering the file. For example, setting `svn:mime-type` to `text/html` will ensure the file is highlighted as HTML, regardless of the file extension. It also allows selecting the character encoding used in the file content. For example, if the file content is encoded in UTF-8, set `svn:mime-type` to `text/html;charset=utf-8`. The `charset=` specification overrides the default encoding defined in the `default_charset` option of the `[trac]` section of [TracIni#trac-section trac.ini]. |
| | 64 | |
| | 65 | For the Subversion backend, some advanced additional features are available: |
| | 66 | - The `svn:needs-lock` property will be displayed |
| | 67 | - Support for the `svn:mergeinfo` property showing the merged and eligible information |
| | 68 | - Support for browsing the `svn:externals` property |
| | 69 | (which can be [TracIni#svn:externals-section configured]) |
| | 70 | - The `svn:mime-type` property is used to select the syntax highlighter for rendering |
| | 71 | the file. For example, setting `svn:mime-type` to `text/html` will ensure the file is |
| | 72 | highlighted as HTML, regardless of the file extension. It also allows selecting the character |
| | 73 | encoding used in the file content. For example, if the file content is encoded in UTF-8, |
| | 74 | set `svn:mime-type` to `text/html;charset=utf-8`. The `charset=` specification overrides the |
| | 75 | default encoding defined in the `default_charset` option of the `[trac]` section |
| | 76 | of [TracIni#trac-section trac.ini]. |
| | 77 | {{{#!comment |
| | 78 | MMM: I found this section a bit hard to understand. I changed the first item as I understood that well. |
| | 79 | but I think the other items could be changed also |
| | 80 | cboos: in the meantime, I've added the ''advanced'' word as a hint this can be a bit complex... |
| | 81 | }}} |
| | 82 | |
