]> git.gir.st - VimFx.git/blob - documentation/commands.md
Improve documentation for shortcut customization
[VimFx.git] / documentation / commands.md
1 <!--
2 This is part of the VimFx documentation.
3 Copyright Simon Lydell 2015, 2016.
4 See the file README.md for copying conditions.
5 -->
6
7 # Commands
8
9 Most of VimFx’s commands are straight-forward enough to not need any
10 documentation. For some commands, though, there is a bit more to know.
11
12 In this document, many commands are referred to by their default shortcut. You
13 can of course [change those] if you like. (Read about [modes] to tell the
14 difference between _commands_ and _shortcuts._)
15
16 [change those]: shortcuts.md
17 [modes]: modes.md
18
19 ## Counts
20
21 Some commands support _counts._ That means that you can type a number before a
22 command and it will change its behavior based on that number—the count. For
23 example, typing `12x` would close 12 tabs.
24
25 (As opposed to Vim, you may only supply a count _before_ a command, not in the
26 middle of one. That’s because VimFx’s commands are simple sequences, while Vim’s
27 are operators and motions.)
28
29 ### `gu`
30
31 Goes _count_ levels up in the URL hierarchy.
32
33 ### `H` and `L`
34
35 Goes _count_ pages backward/forward in history.
36
37 ### Scrolling commands
38
39 Specifying a count make them scroll _count_ times as far.
40
41 ### `J`, `K`
42
43 Selects the tab _count_ tabs backward/forward.
44
45 If the count is greater than one they don’t wrap around when reaching the ends
46 of the tab bar, unless:
47
48 - the first tab is selected and `J` is used.
49 - the last tab is selected and `K` is used.
50
51 They only wrap around _once._
52
53 ### `gl`
54
55 Selects the _count_ most recently visited tab.
56
57 ### `gL`
58
59 Selects the _count_ oldest unvisited tab.
60
61 Tip: It might help to make “unread” tabs visually different through custom
62 [styling]:
63
64 ```css
65 // Unread, unvisited tabs (opened in the background). These are the ones that
66 // can be selected using `gL`.
67 .tabbrowser-tab[unread]:not([VimFx-visited]):not(#override) {
68 font-style: italic !important;
69 }
70
71 // Unread but previously selected tabs (that have changed since last select).
72 .tabbrowser-tab[unread][VimFx-visited]:not(#override) {
73 font-weight: bold !important;
74 }
75 ```
76
77 [styling]: styling.md
78
79 ### `gJ`, `gK`
80
81 Moves the current tab _count_ tabs forward/backward.
82
83 As opposed to `J` and `K`, pinned and non-pinned tabs are handled separately.
84 The first non-pinned tab wraps to the last tab, and the last tab wraps to the
85 first non-pinned tab, and vice versa for non-pinned tabs. Use `gp` to move a tab
86 between the pinned and non-pinned parts of the tab bar.
87
88 Other than the above, the count and wrap semantics work like `J` and `K`.
89
90 ### `g0`, `g^`, `g$`
91
92 `g0` selects the tab at index _count,_ counting from the start.
93
94 `g^` selects the tab at index _count,_ counting from the first non-pinned tab.
95
96 `g$` selects the tab at index _count,_ counting from the end.
97
98 ### `x`
99
100 Closes the current tab and _count_ minus one of the following tabs.
101
102 ### `X`
103
104 Restores the _count_ last closed tabs.
105
106 ### `I`
107
108 Passes on the next _count_ keypresses to the page, without activating VimFx
109 commands.
110
111 ### The hint commands
112
113 Explained in the their own section below.
114
115 ### `gi`
116
117 Explained in its own section below.
118
119
120 ## Scrolling commands
121
122 Firefox lets you scroll with the arrow keys, page down, page up, home, end and
123 space by default. VimFx provides similar scrolling commands (and actually
124 overrides `<space>`), but they work a little bit differently.
125
126 They scroll _the currently focused element._ If the currently focused element
127 isn’t scrollable, the largest scrollable element on the page (if any, and
128 including the entire page itself) is scrolled.
129
130 You can focus scrollable elements using the `ef` command (or the `f` command).
131 Scrollable browser elements, such as in the dev tools, can be focused using the
132 `eb` command. The right border of hint markers for scrollable elements is styled
133 to remind of a scroll bar, making them easier to recognize among hints for
134 links.
135
136 Note that `ef` and `f` do _not_ add a hint marker for the _largest_ scrollable
137 element (such as the entire page). There’s no need to focus that element, since
138 it is scrolled by default if no other scrollable element is focused, as
139 explained above. (This prevents the largest scrollable element from likely
140 eating your best hint char on most pages; see [The hint commands]).
141
142 [The hint commands]: #the-hint-commands--hints-mode
143
144 ### `g[` and `g]`
145
146 Each time you use `gg`, `G`, `0`, `$`, `/`, `a/`, `g/`, `n`, `N` or `'`, the
147 current scroll position is recorded in a list just before the scrolling command
148 in question is performed. You can then travel back to the scroll positions in
149 that list by using the `g[` command. Went too far back? Use the `g]` to go
150 forward again.
151
152 If the current scroll position already exists in the list, it is moved to the
153 end. This way, repeating `g[` you will scroll back to old positions only once.
154
155 Both `g[` and `g]` go _count_ steps in the list.
156
157 This feature is inspired by Vim’s _jump list._ Some people prefer changing the
158 shortcuts to `<c-o>` and `<c-i>` to match Vim’s.
159
160 ### Marks: `m` and `'`
161
162 Other than traditional scrolling, VimFx has _marks._ Press `m` followed by a
163 letter to associate the current scroll position with that letter. For example,
164 press `ma` to save the position into mark _a._ Then you can return to that
165 position by pressing `'` followed by the same letter, e.g. `'a`.
166
167 Note: Firefox has a `'` shortcut by default. It opens the Quick Find bar. VimFx
168 provides the `g/` shortcut instead.
169
170 #### Special marks
171
172 Just like Vim, VimFx has a few special marks. These are set automatically.
173
174 - `'`: Pressing `''` takes you to the scroll position before the last `gg`, `G`,
175 `0`, `$`, `/`, `a/`, `g/`, `n`, `N`, `'`, `g[` or `g]`.
176
177 - `/`: Pressing `'/` takes you to the scroll position before the last `/`, `a/`
178 or `g/`.
179
180 (You can change these marks by using the [`scroll.last_position_mark` and
181 `scroll.last_find_mark`][mark-options] options.)
182
183 [mark-options]: options.md#scroll.last_position_mark-and-scroll.last_find_mark
184
185 #### Minor notes
186
187 Unlike Vim, you may press _any_ key after `m`, and the scroll position will be
188 associated with that key (Vim allows only a–z, roughly).
189
190 Unlike Vim and Vimium, VimFx has no global marks. The reason is that they would
191 be a lot more complicated to implement and do not seem useful enough to warrant
192 that effort.
193
194 As mentioned above, `m` stores the _current scroll position._ Specifically, that
195 means the scroll position of the element that would be scrolled if the active
196 element isn’t scrollable; see [Scrolling commands] above.
197
198 [Scrolling commands]: #scrolling-commands-1
199
200
201 ## `gi`
202
203 `gi` focuses the text input you last used, or the first one on the page. Note
204 that a [prevented autofocus] still counts as having focused and used a text
205 input. This allows you to have your cake and eat it too: You can enable
206 autofocus prevention, and type `gi` when you wish you hadn’t.
207
208 `gi` takes a count. It then selects the `counth` text input on the page. Note
209 that `gi` and `1gi` are different: The latter _always_ focuses the first input
210 of the page, regradless of which input you used last.
211
212 After having focused a text input using `gi`, `<tab>` and `<s-tab>` will _only
213 cycle between text inputs,_ instead of moving the focus between _all_ focusable
214 elements as they usually do. (See also the [`focus_previous_key` and
215 `focus_next_key`] advanced options.)
216
217 [prevented autofocus]: options.md#prevent-autofocus
218 [`focus_previous_key` and `focus_next_key`]: options.md#focus_previous_key-and-focus_next_key
219
220
221 ## The hint commands / Hints mode
222
223 When invoking one of the hint commands (such as `f`, `et` or one of the [`v`
224 commands]) you enter Hints mode. In Hints mode, markers with hints are shown for
225 some elements. By typing the letters of a hint something is done to that
226 element, depending on the command. You can also **type the text of an element**
227 with a hint marker: See the [Hint characters] option for more information.
228
229 Another way to find links on the page is to use `g/`. It’s like the regular find
230 command (`/`), except that it searches links only.
231
232 Which elements get hints depends on the command as well:
233
234 - `f` and `af`: Anything clickable—links, buttons, form controls.
235 - `F`, `et`, `ew` and `ep`: Anything that can be opened in a new tab or
236 window—links.
237 - `yf`: Anything that has something useful to copy—links (their URL) and text
238 inputs (their text).
239 - `ef`: Anything focusable—links, buttons, form controls, scrollable elements,
240 frames.
241 - `ec`: Most things that have a context menu—images, links, videos and text
242 inputs, but also many textual elements.
243 - `eb`: Browser elements, such as toolbar buttons.
244
245 It might seem simpler to match the same set of elements for _all_ of the
246 commands. The reason that is not the case is because the fewer elements the
247 shorter the hints. (Also, what should happen if you tried to `F` a button?)
248
249 (You can also customize [which elements do and don’t get hints][hint-matcher].)
250
251 Another way to make hints shorter is to assign the same hint to all links with
252 the same URL. So don’t be surprised if you see the same hint repeated several
253 times.
254
255 VimFx also tries to give you shorter hints for elements that you are more likely
256 to click. This is done by the surprisingly simple rule: The larger the element,
257 the shorter the hint. To learn more about hint characters and hint length, read
258 about the [Hint characters] option.
259
260 Hints are added on top of the corresponding element. If they obscure the display
261 too much you can hold down ctrl and shift simultaneously to make them
262 transparent, letting you peek through them. (See [Styling] and the
263 [`hints.peek_through`] option if you’d like to change that.) The hints can also
264 sometimes cover each other. Press `<c-space>` and `<s-space>` to switch which
265 one should be on top.
266
267 Yet another way to deal with areas crowded with hint markers is to type part of
268 a marker’s element text. That will filter out hint markers whose elements
269 _don’t_ match what you’ve typed. Pagination links are good examples, like these
270 (fake) ones: [1](#1) [2](#2) [3](#3) [4](#4) [5](#5) [6](#6). It’s very hard to
271 tell which hint to use to go to page three. But if you type “3” things will be
272 much clearer. (It might even [auto-activate][Hint auto-activation] the hint
273 marker!)
274
275 When giving a count to a hint command, all markers will be re-shown after you’ve
276 typed the hint characters of one of them, _count_ minus one times. All but the
277 last time, the marker’s link will be opened in a new background tab. The last
278 time the command opens links as normal (in the current tab (`f`) or in a new
279 background (`F`) or foreground tab (`et`)).
280
281 Note that the hint command adds markers not only to links, but to buttons and
282 form controls as well. What happens the _count_ minus one times then? Buttons,
283 checkboxes and the like are simply clicked, allowing you to quickly check many
284 checkboxes in one go, for example. Text inputs cancel the command.
285
286 `af` works as if you’d supplied an infinite count to `f`. (In fact, the `af`
287 command is implemented by running the same function as for the `f` command,
288 passing `Infinity` as the `count` argument!) Therefore the `af` command does not
289 accept a count itself.
290
291 The `et`, `ef`, `yf` and `eb` commands do not accept counts.
292
293 Press `<up>` to increase the count by one. This is useful when you’ve already
294 entered Hints mode but realize that you want to interact with yet a marker. This
295 can be faster than going into Hints mode once more.
296
297 If you’ve pressed `f` but realize that you’d rather open a link in a new tab you
298 can hold ctrl while typing the last hint character. This is similar to how you
299 can press `<c-enter>` on a focused link to open it in a new tab (while just
300 `<enter>` would have opened it in the same tab). Hold alt to open in a new
301 foreground tab. In other words, holding ctrl works as if you’d pressed `F` from
302 the beginning, and holding alt works as if you’d pressed `et`.
303
304 For the `F` and `et` commands, holding ctrl makes them open links in the same
305 tab instead, as if you’d used the `f` command. Holding alt toggles whether to
306 open tabs in the background or foreground—it makes `F` work like `et`, and `et`
307 like `F`. As mentioned in [Hint auto-activation], the best hint is highlighted
308 with a different color, and can be activated by pressing `<enter>`. Holding alt
309 or ctrl works there too: `<c-enter>` toggles same/new tab and `<a-enter>`
310 toggles background/foreground tab.
311
312 (Also see the advanced options [`hints.toggle_in_tab`] and
313 [`hints.toggle_in_background`].)
314
315 Finally, if the element you wanted to interact with didn’t get a hint marker you
316 can try pressing `<c-backspace>` while the hints are still shown. That will give
317 hint markers to all _other_ elements. Warning: This can be very slow, and result
318 in an overwhelming amount of hint markers (making it difficult to know which
319 hint to activate sometimes). See this as an escape hatch if you _really_ want to
320 avoid using the mouse at all costs. (Press `<c-backspace>` again to toggle back
321 to the previous hints.)
322
323 ### Mnemonics and choice of default hint command shortcuts
324
325 The main command is `f`. It comes from the Vimium and Vimperator extensions. The
326 mnemonic is “<strong>f</strong>ollow link.” It is a good key, because on many
327 keyboard layouts it is located right under where your left index finger rests.
328
329 The most common variations of `f` are centered around that letter: `F`, `yf` and
330 `af`. (Some users might want to swap `F` and `et`, though.) In Vim, it is not
331 uncommon that an uppercase letter does the same thing as its lowercase
332 counterpart, but with some variation (in this case, `F` opens links in new tabs
333 instead of in the current tab), and `y` usually means “yank” or “copy.” VimFx
334 also has this pattern that `a` means “all.”
335
336 You can think of the above commands as the “f commands.” That sounds like
337 “eff-commands” when you say it out loud, which is a way of remembering that the
338 rest of the `f` variations are behind the `e` key. That’s also a pretty good
339 key/letter, because it is close to `f` both alphabetically, and physically in
340 many keyboard layouts (and is pretty easy to type).
341
342 The second key after `e` was chosen based on mnemonics: There’s `et` as in
343 <strong>t</strong>ab, `ew` as in <strong>w</strong>indow, `ep` as in
344 <strong>p</strong>rivate window, `ef` as in <strong>f</strong>ocus, `ec` as in
345 <strong>c</strong>ontext menu and `eb` as in <strong>b</strong>rowser.
346
347 [`v` commands]: #the-v-commands--caret-mode
348 [hint-matcher]: api.md#vimfxsethintmatcherhintmatcher
349 [Hint characters]: options.md#hint-characters
350 [Hint auto-activation]: options.md#hint-auto-activation
351 [Styling]: styling.md
352 [`hints.peek_through`]: options.md#hints.peek_through
353 [`hints.toggle_in_tab`]: options.md#hints.toggle_in_tab
354 [`hints.toggle_in_background`]: options.md#hints.toggle_in_background
355
356
357 ## The `v` commands / Caret mode
358
359 The point of Caret mode is to copy text from web pages using the keyboard.
360
361 ### Entering Caret mode
362
363 Pressing `v` will enter Hints mode with hint markers for all elements with text
364 inside. When activating a marker, its element will get a blinking caret at the
365 beginning of it, and Caret mode will be entered.
366
367 The `av` command does the same thing as `v`, but instead of placing the caret at
368 the beginning of the element, it selects the entire element (it selects
369 <strong>a</strong>ll of the element).
370
371 The `yv` command brings up the same hint markers as `av` does, and then takes
372 the text that `av` would have selected and copies it to the clipboard. It does
373 not enter Caret mode at all.
374
375 The letter `v` was chosen for these shortcuts because that’s what Vim uses to
376 enter its Visual mode, which was an inspiration for VimFx’s Caret mode.
377
378 ### Caret mode commands
379
380 Caret mode uses [Firefox’s own Caret mode] under the hood. This means that you
381 can use the arrows keys, `<home>`, `<end>`, `<pageup>` and `<pagedown>`
382 (optionally holding ctrl) to move the caret as usual. Hold shift while moving
383 the caret to select text.
384
385 In addition to the above, VimFx provides a few commands inspired by Vim.
386
387 - `h`, `j`, `k`, `l`: Move the caret left, down, up or right, like the arrow
388 keys.
389
390 - `b`, `w`: Move the caret one word backward or forward, like `<c-left>` and
391 `<c-right>` but a bit “Vim-adjusted” (see the section on Vim below) in order
392 to be more useful.
393
394 - `0` (or `^`), `$`: Move the caret to the start or end of the line.
395
396 The above commands (except the ones moving to the start or end of the line)
397 accept a _count._ For example, press `3w` to move three words forward.
398
399 Press `v` to start selecting text. After doing so, VimFx’s commands for moving
400 the caret select the text instead of just moving the caret. Press `v` again to
401 collapse the selection again. (Note that after pressing `v`, only VimFx’s
402 commands goes into “selection mode,” while Firefox’s work as usual, requiring
403 shift to be held to select text.)
404
405 `o` moves the caret to the “other end” of the selection. If the caret is at the
406 end of the selection, `o` will move it to the start (while keeping the selection
407 intact), and vice versa. This let’s you adjust the selection in both ends.
408
409 Finally, `y` is a possibly faster alternative to the good old `<c-c>`. Other
410 than copying the selection to the clipboard, it also exits Caret mode, saving
411 you yet a keystroke. (`<escape>` is unsurprisingly used to exit Caret mode
412 otherwise.)
413
414 [Firefox’s own Caret mode]: http://kb.mozillazine.org/Accessibility_features_of_Firefox#Allow_text_to_be_selected_with_the_keyboard
415
416 ### Workflow tips
417
418 If you’re lucky, the text you want to copy is located within a single element
419 that contains no other text, such as the text of a link or an inline code
420 snippet. If so, using the `yv` command (which copies an entire element without
421 entering Caret mode) is the fastest.
422
423 If you want to copy _almost_ all text of an element, or a bit more than it, use
424 the `av` command (which selects an entire element). Then adjust the selection
425 using the various Caret mode commands. Remember that `o` lets you adjust both
426 ends of the selection.
427
428 In all other cases, use the `v` command to place the caret close to the text you
429 want to copy. Then move the caret in place using the various Caret
430 mode commands, hit `v` to start selecting, and move the again.
431
432 Use `y` to finish (or `<escape>` to abort). Alternatively, use the `<menu>` key
433 to open the context menu for the selection.
434
435 ### For Vim users
436
437 As seen above, Caret mode is obviously inspired by Vim’s Visual mode. However,
438 keep in mind that the point of Caret mode is to **copy text using the keyboard,
439 not mimicing Vim’s visual mode.** I’ve found that selecting text for _copying_
440 is different than selecting code for _editing._ Keep that in mind.
441
442 Working with text selection in webpages using code is a terrible mess full of
443 hacks. New commands will only be added if they _really_ are worth it.
444
445 A note on VimFx’s `b` and `w`: They work like Vim’s `b` and `w` (but a “word” is
446 according to Firefox’s definition, not Vim’s), except when there is selected
447 text and the caret is at the end of the selection. Then `b` works like Vim’s
448 `ge` and `w` works like Vim’s `e`. The idea is to keep it simple and only
449 provide two commands that do what you want, rather than many just to mimic Vim.
450
451
452 ## Ignore mode `<s-f1>`
453
454 Ignore mode is all about ignoring VimFx commands and sending the keys to the
455 page instead. Sometimes, though, you might want to run some VimFx command even
456 when in Ignore mode.
457
458 One way of doing that is to press `<s-escape>` to exit Ignore mode, run your
459 command and then enter Ignore mode again using `i`. However, it might be
460 inconvenient having to remember to re-enter Ignore mode, and sometimes that’s
461 not even possible, such as if you ran the `K` command to get to the next tab.
462
463 Another way is to press `<s-f1>` followed by the Normal mode command you wanted
464 to run. (`<s-f1>` is essentially the inverse of the `I` command, which passes
465 the next keypress on to the page. Internally they’re called “quote” and
466 “unquote.”) This is handy if you’d like to switch away from a [blacklisted]
467 page: Just press for example `<s-f1>K`.
468
469 `<s-f1>` was chosen as the default shortcut because on a typical keyboard `<f1>`
470 is located just beside `<escape>`, which makes it very similar to `<s-escape>`,
471 which is used to exit Ignore mode. Both of those are uncommonly used by web
472 pages, so they shouldn’t be in the way. If you ever actually do need to send any
473 of those to the page, you can prefix them with `<s-f1>`, because if the key you
474 press after `<s-f1>` is not part of any Normal mode command, the key is sent to
475 the page. (Another way is for example `<s-f1>I<s-escape>`.)
476
477 [blacklisted]: options.md#blacklist
478
479
480 ## Ex commands
481
482 Vim has something called “ex” commands. Want something similar in VimFx? True to
483 its spirit, VimFx embraces a standard Firefox feature for this purpose: The
484 [Developer Toolbar]. That link also includes instructions on how to extend it
485 with your own commands.
486
487 In the future VimFx might even ship with a few extra “ex” commands by default.
488 We’re open for suggestions!
489
490 [Developer Toolbar]: https://developer.mozilla.org/en-US/docs/Tools/GCLI
Imprint / Impressum