firefox is update to 57.0

[zhengyi5403]

No description provided.

[timacs]

Unfortunately, KeySnail doesn't support Firefox57+. See the updated README of the project.

[jagrg]

This is very sad news. Thanks @mooz and contributors for the great work, and please let us know if anything changes.

[maxh-]

Sad indeed but a great thanks to @mooz. Well, onwards and... maybe not upwards, but there are some Webextension-compatible plugins alread. Saka-key is the one I use and while it's not Keysnail, one can configure it to be pretty Emacs-y.

[nico202]

@maxh- can you share your saka-key config?

[Txellenne]

Sad, indeed (and upset, sorry). & Of course thankful to @mooz for this so great contribution it was a great experience. That said, any (one would know to tell about any) tip on customise key-bindings to vimium-ff so making it closest to Emacs'? I'd appreciate it.

[pierrelegall]

Firstly, thank you to all the contributors of this repository, it was a helpful and well made Firefox extension.

I tried Saka Key but I am not fully satisfied. It hassle me because:

• it does not allow to set key bindings for text inputs (see this issue)
• it does not override browser key bindings (see this issue)

However, note two big +1:

• it catches keys bypassing the page listeners
• it comes with the « click with your keyboard » feature built-in (similar to the HoK plugin for Keysnail), wich is a must have

You can find my Emacs-y configuration here.

[P-Seebauer]

Farewell and a big thank you to all the contributers.

[deadcyclo]

So long, and thanks for all the fish. I'ts been a great run, and I really appreciate all of the hard work that when in to keysnail, and I'll miss it dearly

Personally, I'm moving away from Firefox. They have moved in a very bad direction with their latest release. The only reason I've stuck with Firefox, as it was getting slower, and worse for every release, was due to their great API that allowed us lots of control. By changing this, FF no longer has anything to offer power users such as myself.

My choice of browser fell on Vivaldi, the fairly new (released in 2015) project created by von Tetzchner (the founder of Opera). I'ts webkit based, and supports chrome-plugins, but allows you a wide range of configurations and settings, rather than Chromes "this is it - take it or leave it" philosophy. This is mainly important because I can hide all of the menus and stuff, leaving me with something that basically looks like the good old conkeror. Furthermore I can change, or remove any keybindings in the browser that I don't like, or that collide with bindings I want to use with my keysnail replacement.

I've replaced keysnail with surfingkeys. I'ts actually made for vi-users, but it is robust, very feature rich (much more so than any other such plug-in I've seen), and most important it allows key chaining, so you can make it very "emacsy". The only two minor issues I ahve is
a) It uses it's own editor for editing forms, urls, etc, which is vi-like. I'm not sure if I like that, but I'm fairly certain I can emacsfy the editor if I want to (though learning some more vi-basics probably would be a good idea anyhow, so I might just leave it be)
b) I really liked the plug-in system that keysnail had. You can sort of accomplish this in surfingkeys as well by adding your code in the config file, which works fine. But I have yet to find a way to make my custom code run in the context of the extension, so I gain access to the chrome extension-only code stuff such as manipulating tabs. But I've only been using it for a few days, so it might be possible. If not I would have to decide if I can live without that possiblity, or if I want to fork the project and add my own features directly.

My conclusion so far is that Vivaldi is far superior to firefox, and surfingkeys is an adequate replacement for keysnail (but oh how I will miss keysnail).

[P-Seebauer]

Slight note for those of you that miss emacs editing in text-boxes and the like (linux-gtk only settings, sorry for getting your hopes up):

This article describes how to set emacs bindings for text editing in gtk3. With that enabled, more emacs-keybindings will work inside of Firefox (Ctrl-a, M-f), too. Ctrl-n and Ctrl-p still don't work.

[nmsalgueiro]

I've moved to Waterfox just so I could keep this extension working.

[wvxvw]

Sad news: as of today, Waterfox doesn't support KeySnail anymore :(

[ncaq]

Hint.

To use

• brookhong/Surfingkeys: Map your keys for web surfing, expand your browser with javascript and keyboard.

and

• Linux: mooz/xkeysnail: Yet another keyboard remapping tool for X environment
• Windows: keyhac: User Manual

then get to great UX as keysnail.

[wvxvw]

@ncaq Surfingkeys works... for like 50% of the keybdingings, maybe. It's not a real alternative and especially not for Emacs.

I don't want to mess with the X settings because it can lead to all sorts of inconveniences / it's already overloaded for me with a bunch of stuff / I don't want it to run Python. (Just as an example, say, you accidentally / absentmindedly remap a key that's used in your password in such a way that there's no way to type the password. That will be quite an annoyance.

[ncaq]

@wvxvw

absentmindedly remap a key that's used in your password in such a way that there's no way to type the password. That will be quite an annoyance.

xkeynsnail have escape_next_key setting.
for instance https://github.com/ncaq/.xkeysnail-ncaq/blob/33efe314e970c52c263e624b1b5a4f4ca21609e0/config.py#L19
This is "escape" xkeysnail temporary.