This document contains a list of frequently asked questions. If you question is not listed or properly answered below, you can ask your question on r/vieb or via a github issue. Feel free to ask questions on the subreddit or on github if you can't figure it out.
On Windows you would download releases ending in .exe
or win.zip
.
On Linux you download either the AppImage or your distribution's native format (e.g. deb for Debian/Ubuntu and so on).
For Mac, there are two zipped Apps, one for x64 and one for ARM64.
It's important to make sure that you download the right architecture for your system.
If it's a Raspberry Pi or similar, pick ARM64 for your distribution,
otherwise, you probably need the regular release (AMD64, x86_64 or simply no suffix).
If it's a zip/tar.gz archive that you downloaded, you can extract it and double-click the executable. On Windows, you can simply double-click on the ".exe" file to run the program. If you are using Linux, you can download the AppImage to be able to do the same. For most other download options, you need to use your distribution's package manager, usage should be similar to other packages of the same type. See these instructions for opening on Mac.
This could be due to a number of things, if using Linux, you probably need to enable unprivileged containers. There are instructions on the arch wiki how to enable this. If this doesn't help, try starting Vieb from a terminal or cmd window, to check for startup errors. Also, you can start Vieb with "vieb --debug" to view the internal debugging tools of Vieb.
Vieb is Chromium/Electron based and implements a wide range of features aimed to FEEL like Vim. For a list of features, see the homepage. See this issue for my motivation of starting Vieb. A proper comparison and migration guides haven't been made yet.
As you probably noticed, by default Vieb does not have any mouse support outside of Insert mode.
In Vieb, you can do everything with the keyboard, even things you normally would need to use the mouse for.
However, you can enable the mouse across Vieb with the :set mouse
command.
This should bring back most of the familiar mouse movements on the page and the tabs,
but Vieb still requires using the keyboard for most actions.
If you're new to Vieb or Vim in general, using the mouse can help,
but it's no substitute for reading the :help
page and learning to use Vieb (or Vim for that matter) properly.
Finally, if you plan to keep using the mouse, you might as well save that setting to disk using "mkviebrc" (see :h mkviebrc
for help).
See this issue for more background information,
basically Google blocks everything that isn't Chrome or Firefox.
You can use :set firefoxmode=google
within Vieb to mimic Firefox when visiting Google pages,
most people that I heard back from reported that it works with firefoxmode enabled.
Same as Vim. From normal mode, type :qa
then Enter. (This assumes the default mappings and commands.)
See this issue for the rationale and other options.
Same as Vim, there is a strong mode separation. See this issue for my answer to a similar question.
No, Vieb does not automatically update, nor does it check for any of that in the background.
Vieb will ONLY make requests when opened pages fetch new resources
OR when you specifically ask it to (either via navigation or with custom settings).
Checking for updates can be done by opening the :version
page and specifically clicking "Check for updates".
Alternatively, you can watch the github repository
or subscribe to the official Vieb subreddit.