Key | Action | Notes |
Ctrl+o | toggle panes on/off | |
Ctrl+l | redraw screen | This is on all terminals |
Ctrl+PgUp | goto parent dir | |
Ctrl+Enter | copy selected filename to command line | %f is equivalent |
Ctrl+x+p | copy unselected panel's path to command line | %D is equivalent |
Ctrl+x ! | External panelize | Display paths returned from external command |
Shift+mouse | select text | |
Insert | toggle selection of highlighted file | |
* | toggle selection | |
+ | add pattern to selection | |
- | remove pattern from selection | |
F3 | view | |
F4 | edit | |
F5 | copy | |
F6 | rename | |
F7 | mkdir | |
F8 | remove | |
F9 | menu | |
F10 | Exit |
Google commented on different types of assertations in their testing framework ( Google Testing Blog: EXPECT vs. ASSERT) I have found assertations in my code very useful on many occasions; however, I do not see any need for the EXPECT function. If your code is broken then it is broken and there is no point in continuing and testing conditions which are not likely to be met. It is like with C++ compiler errors. The most important error is the firtst error. The rest of the erorrs is usually rubish and useless.
Comments