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 | | If a default repository has been configured, 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)]^. |
| 7 | At the top-level of the repository browser is the '''Repository Index''', listing all the configured repositories. |
| 8 | Each repository has a name which is used as a path prefix in a "virtual" file hierarchy encompassing all the available repositories. |
| 9 | 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 are also listed, in a '''Default Repository''' section placed before the repository index. If the default repository is the only repository associated with the Trac environment, then the '''Repository Index''' will be omitted. This means that after upgrading a single-repository Trac of version 0.11 (or earlier) to a multi-repository Trac (0.12), the repository browser will look and feel the same, that single repository becoming automatically the "default" repository. |
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. |
| 15 | Clicking on the revision number of a file or directory will take you to the TracRevisionLog for that file. |
| 16 | Note that there's also a ''Revision Log'' navigation link that will do the same for the path currently being examined. |
| 17 | Clicking on the ''diff'' icon after revision number will display the changes made to the files modified in that revision. |
38 | | The color bar next to the ''Age'' column gives a visual indication of the age |
39 | | of the last change to a file or directory, following the convention that |
40 | | '''[[span(style=color:#88f,blue)]]''' is oldest and '''[[span(style=color:#f88,red)]]''' |
41 | | is newest, but this can be [TracIni#browser-section configured]. |
| 22 | The color bar next to the ''Age'' column gives a visual indication of the age of the last change to a file or directory, following the convention that '''[[span(style=color:#88f,blue)]]''' is oldest and '''[[span(style=color:#f88,red)]]''' is newest, but this can be [TracIni#browser-section configured]. |
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'` (open) to toggle between expanded and collapsed state of the selected |
| 29 | If you're using a Javascript enabled browser, you'll be able to expand and collapse directories in-place by clicking on the arrow head at the right side of a directory. Alternatively, the [trac:TracAccessibility keyboard] can also be used for this: |
| 30 | - use `j` and `k` to select the next or previous entry, starting with the first |
| 31 | - `o` ('''o'''pen) to toggle between expanded and collapsed state of the selected |
58 | | - `'v'` (view, visit) and `'<Enter>'`, same as above |
59 | | - `'r'` can be used to force the reload of an already expanded directory |
60 | | - `'A'` can be used to directly visit a file in annotate (blame) mode |
61 | | - `'L'` to view the log 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 . |
63 | | |
64 | | {{{#!comment |
65 | | MMM: I guess that some keys are upper case and some lower to avoid conflicts with browser defined keys. |
66 | | I find for example in Firefox and IE on windows that 'a' works as well as 'A' but 'l' does not work for 'L'. |
67 | | cboos: 'l' is reserved for Vim like behavior, see #7867 |
68 | | }}} |
| 33 | - `v` ('''v'''iew, '''v'''isit) and `<Enter>`, same as above |
| 34 | - `r` can be used to force the '''r'''eload of an already expanded directory |
| 35 | - `a` can be used to directly visit a file in '''a'''nnotate (blame) mode |
| 36 | - `l` to view the '''l'''og for the selected entry |
| 37 | If no row has been selected using `j` or `k` these keys will operate on the entry under the mouse. |
71 | | - The `svn:needs-lock` property will be displayed |
72 | | - Support for the `svn:mergeinfo` property showing the merged and eligible information |
73 | | - Support for browsing the `svn:externals` property |
74 | | (which can be [TracIni#svn:externals-section configured]) |
75 | | - The `svn:mime-type` property is used to select the syntax highlighter for rendering |
76 | | the file. For example, setting `svn:mime-type` to `text/html` will ensure the file is |
77 | | highlighted as HTML, regardless of the file extension. It also allows selecting the character |
78 | | encoding used in the file content. For example, if the file content is encoded in UTF-8, |
79 | | set `svn:mime-type` to `text/html;charset=utf-8`. The `charset=` specification overrides the |
80 | | default encoding defined in the `default_charset` option of the `[trac]` section |
81 | | of [TracIni#trac-section trac.ini]. |
| 40 | - The `svn:needs-lock` property will be displayed. |
| 41 | - Support for the `svn:mergeinfo` property showing the merged and eligible information. |
| 42 | - Support for browsing the `svn:externals` property, which can be [TracIni#svn:externals-section configured]. |
| 43 | - 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]. |