aboutsummaryrefslogtreecommitdiffstats
AgeCommit message (Collapse)Author
2016-02-20Simplify command-option parsing.Stephen Blott
2016-02-20moveToNewWindow accepts a count.Stephen Blott
This make `moveToNewWindow` accept a count. For example, `3W` to move three tabs to (the same) new window. The tabs chosen are the current tab, then those to the right of the current tab, and then those to the left of the current tab. `999W` moves *all* tabs to a new window. It's not clear why you would want to do that. An alternative would be to leave the last tab behind.
2016-02-20Merge pull request #2002 from smblott-github/move-to-chrome.sessionsStephen Blott
Move wholly to chrome.sessions.
2016-02-20Move wholly to chrome.sessions.Stephen Blott
This strips out the legacy pre-chrome.sessions code. The API has been in Chrome since version 37, and we probably don't really need to support older versions than that.
2016-02-20Add `count` command option.Stephen Blott
Examples: map j scrollDown count=10 map q removeTab count=999
2016-02-20Refactor command-option parsing.Stephen Blott
When we introduced command options (for mapping keys to custom-search engines), the parsing was done in the Vomnibar code. This moves the parsing to `commands.coffee`, which is where it should always have been. This is a preliminary step with a view to adding a new `count` command option.
2016-02-20Merge pull request #2000 from smblott-github/hide-HUD-in-insert-mode-onlyStephen Blott
hideHUD option applies to insert mode only.
2016-02-20Correctly set `settingsVersion`.Stephen Blott
This fixes an error in #1950. There, we need to detect new installs, and did so by checking `settingsVersion`. However, `settingsVersion` is *always* truthy. So the "new install" code never triggers. Here, the default value for `settingsVersion` is falsy. Note, we *always* set `settingsVersion` when the extension is loaded. So `settingsVersion` is always set.
2016-02-20hideHUD option applies to insert mode only.Stephen Blott
This makes the `hideHud` option apply only to insert mode (when entered with `i`). Fixes #1953. Fixes #487. We could rename the option itself and add migration code, but that seems overkill. An alternative would be to remove this option entirely.
2016-02-18Tweak README.md.Stephen Blott
2016-02-18Note new filtered-hints coption in README.txt.Stephen Blott
2016-02-18Merge pull request #1950 from smblott-github/filtered-hints--wait-for-enterStephen Blott
For filtered hints, wait for <Enter> before activating link
2016-02-18Wait-for-enter: default to "true" for new users.Stephen Blott
For existing users, the default is "false"; but for new users wait-for-enter defaults to "true".
2016-02-18Wait-for-enter: better wording on options page.Stephen Blott
2016-02-18Wait-for-enter: hold flash in typing protector.Stephen Blott
2016-02-18Wait-for-enter: add necessary option support.Stephen Blott
2016-02-18Wait-for-enter: for filtered hints.Stephen Blott
This affects filtered hints only. If a hint is triggered because the user typed the link text, then: - highlight the link - but wait until the user types `Enter` before activating the link.
2016-02-18Fix typo in README.md.Stephen Blott
2016-02-18Note passNextKey in README.md.Stephen Blott
2016-02-18Merge pull request #1985 from smblott-github/pass-next-keyStephen Blott
New command: Pass next key
2016-02-18PassNextKey; exclude single-character mappings.Stephen Blott
Consider: map q passNextKey This works fine in normal mode. However, in insert mode, when the user types "q" they expect "q" to be input. Any other behaviour would be pretty weird. Here, we filter out such mappings before the front end sees them. So, with: map q passNextKey map <c-]> passNextKey both mappings work in normal mode, but only the second works in insert mode. This is probably the behaviour likely to cause least user confusion.
2016-02-18PassNextKey; minor tweak.Stephen Blott
2016-02-18PassNextKey; fix tests.Stephen Blott
Oversight from 116ac2c2a279f8497ffd5396f43ac4fd7fd5de67.
2016-02-18PassNextKey; allow multiple mappings.Stephen Blott
This allows: map a passNextKey map b passNextKey (Previously, we only picked up the first mapping.)
2016-02-18PassNextKey; handle pass-next-key in insert mode.Stephen Blott
(First "fully" functional version.)
2016-02-18PassNextKey; move key parsing to keyboard_utils.coffee.Stephen Blott
Previously, key event parsing was embedded in the normal-mode key handlers. Here, we move it to a new function (getKeyCharString) in KeyboardUtils so that it can also be used from elsewhere... In particular for detecting the pass-next-key key in insertmode.
2016-02-18PassNextKey; store key mapping in settings.Stephen Blott
We need the key mapped to passNextKey in the front end so that we can activate pass-next-key from within insert mode too (without the need to consult the background page).
2016-02-18PassNextKey; initial implementation.Stephen Blott
This implements a passNextKey command (initially for normal mode only), as discussed in #1955.
2016-02-16Merge pull request #1994 from mrmr1993/correct-loop-types-2Stephen Blott
Use `for own ... of` instead of `for ... of`
2016-02-16Use `for own ... of` instead of `for ... of`mrmr1993
2016-02-14Merge pull request #1991 from smblott-github/nuke-some-migrationsStephen Blott
Nuke some legacy migration code.
2016-02-14Merge pull request #1993 from smblott-github/filtered-hints-word-splitStephen Blott
Split filtered hints on non-word and hint characters.
2016-02-14Split filtered hints on non-word and hint characters.Stephen Blott
This affects the scoring system for filtered link hits, and therefore affects their usability. Example link text: "We open all day", say 7Eleven Previously: "We open all day", say 7Eleven With this PR: we open all day say Eleven Previously: the typed text `we` and `day` would receive poor scores (not the start of a word, and not a whole word. Now, these get high scores, so are more likely to be selected as the active link. Also, `7Eleven` cannot be typed (because `7` is a hint character). With this PR, the typed text `we` `day` now get high scores, as they should.
2016-02-12Nuke some legacy migration code.Stephen Blott
These migrations are at least ten months old (since release).
2016-02-12Note visitPreviousTab command in README.md.Stephen Blott
2016-02-12Merge pull request #1984 from smblott-github/previous-tabStephen Blott
New command: visit previous tab.
2016-02-11Merge pull request #1977 from mrmr1993/help-dialog-uicomponentStephen Blott
Move help dialog to a UIComponent
2016-02-11Change HelpDialog. to @ for methods inside the HelpDialog objectmrmr1993
2016-02-11Only load help dialog iframe when the dialog is to be shownmrmr1993
2016-02-11Add a comment explaining why HelpDialog has seemingly redundant fieldsmrmr1993
2016-02-11Show vomnibar above the help dialog, remove an unnecessary CSS rulemrmr1993
2016-02-11Tidy up detection for the current page and context belonging to usmrmr1993
2016-02-10BgUtils; two fixes...Stephen Blott
- handle case where there's only one tab - also focus the selected tab's window
2016-02-09BgUtils; implement visitPreviousTab.Stephen Blott
Implements visitPreviousTab (as discussed in #1955).
2016-02-09BgUtils; move tabRecency to bg_tiles.coffee.Stephen Blott
Certain background-page utilities are actually shared, and are therefore best placed in place that reflects that. Here, tabRecency is moved to the new gb_utils.coffee in preparation for implementing a go-to-previous-tab command. In particular, it is no longer appropriate that tabRecency be embedded within the completion code. logMessage() from main.coffee is also a candidate for moving to bg_utils.coffee.
2016-02-05Stop options page link from blurring the help dialog iframemrmr1993
2016-02-04Revert "Tweaks to #1966."Stephen Blott
This reverts commit 4874362d8f14d2cdf712a4c01ac756f2dd6f6e4c.
2016-02-04Tweaks to #1966.Stephen Blott
2016-02-03Hide help dialog when clicking outside of itmrmr1993
2016-02-03Fix closing the help dialogmrmr1993
generated by cgit v1.2.3 (git 2.25.1) at 2026-04-06 03:55:30 +0000