165 | | You can ask for a list of running queries (with their name and Query Id) using "Running queries" menu item (shortcut: {{{C-c C-r s r}}}). |
166 | | It is also possible to kill/stop a query with a specific Query ID using "Kill running query" (shortcut: {{{C-c C-r s k}}}). |
| 171 | You can ask for a list of running queries (with their name and Query Id) using |
| 172 | "Running queries" menu item (shortcut: {{{C-c C-r s r}}}).It is also possible to |
| 173 | kill/stop a query with a specific Query ID using "Kill running query" (shortcut: {{{C-c C-r s k}}}). |
| 174 | |
| 175 | You can also run metric queries (Run metric query, shortcut: {{{C-c C-r m q}}}) |
| 176 | from "Semantic Query" menu or ask for the list of bad smalls found in the code |
| 177 | (Show bad smells, shortcut: {{{C-c C-r s b}}}). See the following page for |
| 178 | further information: [wiki:MetricQuery]. |
| 179 | |
| 180 | Other menu items available from "Semantic Query": Go to definition (jump to the |
| 181 | definition of the function, shortcut: {{{M-.}}}) and Find function references |
| 182 | (shortcut: {{{C-c C-r q r}}}). |
| 183 | |
| 184 | === Dependency analysis === |
| 185 | |
| 186 | There are three available types of dependency analysis in RefactorErl: module, function and |
| 187 | function block dependency analysis. For details check the following page: wiki:Dependency. |
| 188 | |
| 189 | If you would like to get information about dependencies between modules or functions, use |
| 190 | the menu "Module and function dependencies". The parameters are similar to the ones described |
| 191 | here: wiki:Dependency. |
| 192 | |
| 193 | To gather information about module group and function block dependencies, you should use menu |
| 194 | group titled "Function block dependency analysis". It contains a submenu named "Default FB |
| 195 | analysis" where you can start the analysis itself and set its options (see wiki:Dependency), |
| 196 | and another submenu called "Define FBs with regexps" where it is possible to define module |
| 197 | groups using regular expressions. |
| 198 | |
| 199 | === Duplicated code analysis === |
| 200 | |
| 201 | In the Duplicated code analysis sub menu you can search for duplicated code with default |
| 202 | parameters (Search duplicated codes...) or in advanced mode (Advanced search) where it |
| 203 | is possible to modify the default values. See wiki:DuplicateCodeAnalysis for further |
| 204 | information. In Advanced search mode you can specify the name of a duplicated code |
| 205 | analysis ran with specific options. This name can be used to load older results (saved in |
| 206 | dets). |
| 207 | |
| 208 | With "Show duplicates" you can load saved analysis result. You just have to type in the |
| 209 | name of the result which was either specified by you or generated by RefactorErl. Generated |
| 210 | names start with the string "Temp...". The Emacs interface always shows the name of a result |
| 211 | in a buffer titled "Duplicated code information" which is shown after clicking the Analise |
| 212 | button (advanced mode) or starting an analysis from "Search duplicated codes..." or loading |
| 213 | up some older results with "Show duplicates". |