config.source('C:\\Users\\USERNAME\\Sync\\qb\\config2.py')config.source2021-June-1 qutebrowser v2.2.3 released. To keep up with qutebrowser releases, see github.com/qutebrowser/qutebrowser/releases, lists.schokokeks.org/pipermail/qutebrowser/, or old.reddit.com/r/qutebrowser/.
2021-May-22
As of today, this evolving[1]
article
has been on
the web
for
2021-March-28 Expanded this article’s Calling a bash script from a Windows userscript and moved it to its own page. Check it out at www.ii.com/qutebrowser-userscripts-on-windows/.
2021-January-2 In this article, created 5.1 Environment variables.
This article assumes that you know the basics about the qutebrowser web browser. Some basics are discussed in Infinite Ink’s Getting Started with qutebrowser.
To get the most flexibility configuring qutebrowser, I recommend
that you use a config.py file.
To learn
how to create this file
and view
a list of
almost[2]
all possible
settings,
see Infinite Ink’s
qutebrowser’s Template config.py.
One way to edit your config.py is to
do the following.
In a plain text editor, open config.py.[3]
Edit the file.
Save your edits.
Within qutebrowser run the colon command :config-source.
Another way
to
edit your config.py is to do
the following
within qutebrowser.
Run the colon command :config-edit, which will open config.py
in the editor specified by the c.editor.command configuration setting.
Edit the file,
save your edits, and quit the editor. qutebrowser will automatically source
the newly edited config.py.
ℹ | Examples of |
config.sourceIf you want to use multiple configuration files
or put
some of
your
configuration
settings somewhere other
than qutebrowser’s
config
directory,[3]
you can put a line like the following in your config.py.
config.source('C:\\Users\\USERNAME\\Sync\\qb\\config2.py')This setting works on my Windows devices
(with USERNAME replaced with my user name).
ℹ | In
a qutebrowser config file,
backslash (\)
is a
metacharacter
and its normal meaning is to
escape the next character from its
normal
meaning.
To specify
an actual
backslash, use \\. |
If you create a key binding, you may want to start it with
a comma (,) because
@The-Compiler (Florian Bruhin),
qutebrowser’s main developer, has said
that
default key binding will never start with a comma.
To view all key bindings, run the following from within qutebrowser.
:bind
This lists both built-in and user-defined key bindings.
💡 | If you start all your user-defined key bindings with comma (,),
then
typing , in normal mode (also known as command mode) will pop up a list of your
user-defined bindings.
This is useful if you don’t remember all your
|
Here are
some of my
config.py settings.
Note that…
A line that begins with a hash (#) is a comment and is ignored by qutebrowser.
The highlighted
lines are useful for
editing config.py from within qutebrowser.
Doing this
is discussed
above
in
1.2. Using qutebrowser’s configured editor.
## In v2.0.0+, one of the following 2 settings is REQUIRED
# config.load_autoconfig(False)
config.load_autoconfig(True)
## In v2.0.0+, use next if you use Adblock Plus AND hosts blocking
c.content.blocking.method = 'both'
c.content.default_encoding = 'utf-8'
c.content.geolocation = False
## Display PDFs within qutebrowser
c.content.pdfjs = True
c.scrolling.bar = 'always'
c.zoom.default = '150%'
config.bind('<Ctrl-=>', 'zoom-in')
config.bind('<Ctrl-->', 'zoom-out')
## Next works on my Windows devices
c.editor.command = ['code.cmd', '-n', '{file}', '-w']
## Next works on my Windows devices (but is commented out for now)
# c.editor.command = ['gvim.bat', '-f', '{file}', '-c', 'normal {line}G{column0}l']
## I like my start page(s) and default page to be blank
c.url.start_pages = ["about:blank"]
c.url.default_page = "about:blank"
## I like to save web pages in MHTML format
## Thanks to the next key binding, I can use ,sm to do that
config.bind(',sm', 'set-cmd-text :download --mhtml')
## Next works on Windows
c.downloads.location.directory = '%USERPROFILE%\\Downloads-2021-Q2\\'
## Next works on Windows if %YEARQUARTER% environment variable exists
# c.downloads.location.directory = '%USERPROFILE%\\Downloads-%YEARQUARTER%\\'
c.downloads.location.suggestion = 'both'
## ,ya is my shortcut to “yank asciidoc-formatted link”
config.bind(',ya', 'yank inline {url:pretty}[{title}]')
## ,ym is my shortcut to “yank markdown-formatted link”
## ym (without a leading comma) also works because it is built-in
config.bind(',ym', 'yank inline [{title}]({url:pretty})')
## next is a note to self about how to bind JavaScript code to a key shortcut
# config.bind(',hw', "jseval alert('Hello World')")
‼ | When specifying
an editor
command in config.py, such as
in
the
two
highlighted
lines
above,
you
must specify the full executable name, including
any
file extension
(.cmd,
.bat,
or
.whatever). |
Sometimes
environment variables work in a config.py file. For example,
the following settings, which are in
my settings in the previous section,
both work.
c.downloads.location.directory = '%USERPROFILE%\\Downloads-2021-Q2\\' c.downloads.location.directory = '%USERPROFILE%\\Downloads-%YEARQUARTER%\\'
But sometimes environment variables do not work. For example, I have not been able
to figure out how to use an environment variable in
either of the following
config.py settings.
config.source('C:\\Users\\USERNAME\\Sync\\qb\\config2.py')
config.bind(',t', 'spawn -u "C:\\Users\\USERNAME\\Sync\\qb\\tumblelog-wrapper.cmd"')
qutebrowser variables can be used in the arguments of a qutebrowser command. Here is an excerpt from qutebrowser.org/doc/help/commands.html:
{url} expands to the URL of the current page
{url:pretty} expands to the URL in decoded format
{url:host}, {url:domain}, {url:auth}, {url:scheme},
{url:username},
{url:password}, {url:host}, {url:port}, {url:path} and {url:query}
expand to the respective parts of the current URL
{title} expands to the current page’s title
{clipboard} expands to the clipboard contents
{primary} expands to the primary selection contents
💡 | To see the difference between
To view what was yanked
by
|
qutebrowser’s default is:
c.content.javascript.enabled = True
If you want to surf the web without
JavaScript,[4]
put the following in your config.py:
c.content.javascript.enabled = False
If you go to a website that you trust and want to turn on JavaScript, run the following command in qutebrowser:
tsh
This means toggle scripting for the current host during the current qutebrowser session. If you want to make this permanent for this host, use capital letter S, i.e.:
tSh
If you want to include subdomains of the current host, use capital letter H, i.e., one of the following.
tsH tSH
ℹ | t means toggle so if JavaScript is True, a
t[Ss][Hh]
command will change it to False. |
If you use tSh or tSH
to
permanently allow JavaScript on a host, this
permanence is stored in
a file named
autoconfig.yml
in your qutebrowser config directory.
The next qutebrowser session will not know
about
autoconfig.yml
settings unless
one of
the following
equivalent
lines is in your config.py.
config.load_autoconfig(True) config.load_autoconfig()
This section is now part of Infinite Ink’s qutebrowser Userscripts on Windows.
Within qutebrowser, you can display all your
non-default
config.py
and
autoconfig.yml
settings with
any of the following three equivalent commands.
:config-diff :open qute://configdiff o qute://configdiff
Starting with v1.9.0, sometimes — although rarely — qutebrowser crashes. Unfortunately, once a single crash happens, more crashes regularly happen. The fix for this depends on the qutebrowser version.
This type of crash is
not happening much, if at all,
in qutebrowser v2.0.0+.
If
it does happen, you can put the following in your config.py.
c.qt.workarounds.remove_service_workers = True
In qutebrowser v1.14.1 and older, do the following.
Quit qutebrowser.
Rename
C:\Users\USERNAME\AppData\Roaming\qutebrowser\data\webengine\Service Worker\
to
C:\Users\USERNAME\AppData\Roaming\qutebrowser\data\webengine\Service Worker-2021-06-15-CRASH\
(with USERNAME and 2021-06-15 replaced with my user name and the
Service Worker
directory’s date stamp).
Restart qutebrowser.
Information about this is in:
For more about qutebrowser, see Infinite Ink’s…
config.py does not include the config.source configuration setting, which is discussed above in 2. Compartmentalizing your config.py.:version command from within qutebrowser.