Feature wishlist for WebExtensions port

[bovine3dom]

See #705 first. I'd like to use this issue specifically to understand what features people would miss from Vimperator, so that we can try to ensure that any WebExtensions port/successor contains them. What follows is my personal opinion:

High priority

• user remappable keys to arbitrary commands (e.g. bind s ogoogle )
• moving around page
• link hinting mode
• insert/passthrough mode
• find in page mode
• history navigation
• tab switching / navigation (:buffer style)
• opening/closing URLs / tabs / windows
• consistent UX: e.g, works on about:newtab, about:home, hopefully others.

Medium priority

• bookmarks
• hide Firefox GUI
• window switching

Low priority

• download UI (can't use about:downloads unless Firefox devs change their minds).
• :js
• VIMPERATOR_INIT

Please disagree with me below 😄.

[whirm]

The external editor functionality (CTL+I) Is super useful to me, I use it very often to edit all sorts of stuff in Emacs.

[cmcaine]

Emacs!? Ban this sick filth.

…

On 1 March 2017 12:39:17 GMT+00:00, Elric Milon ***@***.***> wrote: The external editor functionality (CTL+I) Is super useful to me, I use it very often to edit all sorts of stuff in Emacs. -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: #729 (comment)

[whirm]

I use it with Spacemacs/evil if that offends you any less ;)

[cmcaine]

Slightly ;P We can do this with the runtime.nativeConnect API, but users who want to use it will have to install a couple of files for us: a simple shell script and a .json file telling Firefox that we're allowed to talk to that shell script. On windows we need a registry key, a json file and a batch file, but same principle. If we get a Filesystem API that lets us write to disk, we might be able to install it automatically on *nix.

…

On Wed, Mar 01, 2017 at 04:46:24AM -0800, Elric Milon wrote: I use it with Spacemacs/evil if that offends you any less ;) -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: #729 (comment)

[MoSal]

• Extended hints.
• :set gui
• :tab* commands.
• :style* commands.
• :bmark (with -keyword and -title).
• :bdelete (with arg).
• :restart

[gkatsev]

Looks like a decent list but needs to be reconciled with what is possible and not possible with web-ext. For example, hiding the firefox GUI is probably not going to be possible even with the new theming support.

Also, can you elaborate some more about "moving around the page"?

[bovine3dom]

I mean hjkl, ^D, ^U etc.

I think it makes sense to work out which features we desire most, and then talk about feasibility after, so we know how hard to fight, and where we can make compromises more easily.

The theming, for example, is something we can lobby for, and if we must, we could make our own WebExtensions API to hide GUI which can be used in the developer edition only.

[gkatsev]

Oh, of course, those kind of movement.

We probably should prioritize things by web-ext support as well. So, high things should be core vimperator stuff and those that web-ext supports (well, key bindings are an exception to something we need to have regardless of web-ext support).

[nachoparker]

thanks for the list
ctrl+I is awesome. It is good to see that there is a way
I also use ctrl+t quite a bit. really handy

The theming, for example, is something we can lobby for, and if we must, we could make our own WebExtensions API to hide GUI which can be used in the developer edition only.

Agree, when the rest is mature, we shouldn't be too scared of changing FF itself. Just small changes close always to upstream.

We probably should prioritize things by web-ext support as well.

Definitely.. I would focus on what we can do easily first, then start the extreme tweaks ;)

[cmcaine]

I think this bug will be most useful to implementers as a list of desired features, without concern for whether they can be implemented or not. Just tell us what you would miss from Vimperator if it was gone.

Let implementers worry about filtering by feasibility - feasibility will be a moving target, anyway.

[nachoparker]

Some more

• o and O to open url/search (modifying current in upper case)
• t and T to open a new tab( modifying current in upper case)
• d to close a tab
• p and P to open URL in clipboard in tab (current or newr
• u to bring back a closed tab
• CTRL+D CTRL+U CTRL+E CTRL+Y
• vimlike jumps (G, gg, '' ...)
• quick marks
• maps keys to javascript code (low priority, but I use it a lot also)
• find (/) with hlsearch support, n and N to navigate results
• CTRL H and CTRL L to navigate history

well, some have already been said

[KamphuisAlex]

Those are the important ones I would say.

I would however like to add support for custom search engines, e.g. use yt for searching on youtube just like is possible in the normal address-bar and in vimperator now.

[gkatsev]

@cmcaine makes sense. We can then filter things later.

[MoSal]

Are we supposed to list everything?

More features:

• :set complete
• :set encoding
• :zoom (with value)