Default mappings are not comprehensive
See original GitHub issueSurfingKeys: 0.9.67
Browser: Chrome
Context
I love that you have provided the default mappings by exposing the ‘createDefaultMappings’ function, but this does not include all mappings. For example, the mappings for j
, gg
, G
, and many others are not defined here, and appear to be hard-coded directly in the source code. It would be much better if instead of hard coding these mappings that they were provided as a function somehow, and then hooked up in the default mappings file, so that people like myself that want to use extremely non-standard mappings do not have to fork this repo in order to do this.
Issue Analytics
- State:
- Created 3 years ago
- Reactions:1
- Comments:6
Top Results From Across the Web
KB5014754—Certificate-based authentication changes on ...
In this mode, if a certificate fails the strong (secure) mapping criteria (see Certificate mappings), authentication will be denied. Audit events. The May...
Read more >Elasticsearch problem with pre-defined mapping and then ...
I create index exactly before indexing with specifying default mapping and setting.
Read more >Mapping | Elasticsearch Guide [8.5] | Elastic
Elasticsearch 7.0.0 and later no longer accept a default mapping. See Removal of mapping types. Experiment with mapping options.
Read more >Mapping update rejected by primary - how to solve ... - Opster
The very first time Elasticsearch finds a new field whose mapping is not pre-defined inside the index, it automatically tries to guess the...
Read more >[Beginner's guide] Understanding mapping with Elasticsearch ...
When a user does not define the mapping in advance, Elasticsearch creates or updates the mapping as needed by default. This is known...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
As a workaround to avoid recursive mapping I remap the default keybindings by prepending
__
to each of them and save them in a list (sayg_defaults
). Then I callunmapAllExcept(g_defaults)
and redefine my own bindings.@xendk See the following example. (I don’t really unmap and remap all keys. Just the ones I need. And right there are keys we cannot remap. And no, I don’t really know Javascript.)