webkit_web_context_set_process_model(wc,
WEBKIT_PROCESS_MODEL_MULTIPLE_SECONDARY_PROCESSES);
- p = g_build_filename(g_get_user_config_dir(), __NAME__, "web_extensions",
+ p = g_build_filename(g_get_user_data_dir(), __NAME__, "web_extensions",
NULL);
webkit_web_context_set_web_extensions_directory(wc, p);
g_free(p);
const gchar *entry = NULL;
GDir *scriptdir = NULL;
- base = g_build_filename(g_get_user_config_dir(), __NAME__, "user-scripts",
+ base = g_build_filename(g_get_user_data_dir(), __NAME__, "user-scripts",
NULL);
scriptdir = g_dir_open(base, 0, NULL);
if (scriptdir != NULL) {
const gchar *basedir, *file, *absfile;
GDir *dir;
- basedir = g_build_filename(g_get_user_config_dir(), __NAME__, "certs", NULL);
+ basedir = g_build_filename(g_get_user_data_dir(), __NAME__, "certs", NULL);
dir = g_dir_open(basedir, 0, NULL);
if (dir != NULL) {
file = g_dir_read_name(dir);
while (file != NULL) {
- absfile = g_build_filename(g_get_user_config_dir(), __NAME__, "certs",
+ absfile = g_build_filename(g_get_user_data_dir(), __NAME__, "certs",
file, NULL);
cert = g_tls_certificate_new_from_file(absfile, NULL);
# USER-SUPPLIED JAVASCRIPT FILES
After a page has been successfully loaded, the directory
-_~/.config/lariza/user-scripts_ will be scanned and each file in it ending with
-*.js* will be run as a JavaScript file in the context of said page.
+_~/.local/share/lariza/user-scripts_ will be scanned and each file in it ending
+with *.js* will be run as a JavaScript file in the context of said page.
*lariza* comes with the following scripts:
them, though, make sure to link them to the directory mentioned above.
# WEB EXTENSIONS
-On startup, WebKit checks _~/.config/lariza/web_extensions_ for any *.so*
+On startup, WebKit checks _~/.local/share/lariza/web_extensions_ for any *.so*
files. See
<http://blogs.igalia.com/carlosgc/2013/09/10/webkit2gtk-web-process-extensions/>
this blog post for further information on these extensions.
you should do is try to add the appropriate CAs to your system-wide store.
If you wish to add simple exceptions, you can grab the certificate and store it
-in the directory _~/.config/lariza/certs_. The filename must be equal to the
-hostname:
+in the directory _~/.local/share/lariza/certs_. The filename must be equal to
+the hostname:
$ echo | openssl s_client -connect foo.de:443 | openssl x509 >foo.de
*~/.config/lariza/adblock*
Adblock patterns. See *lariza-usage*(1).
-*~/.config/lariza/certs*
+*~/.local/share/lariza/certs*
Directory where trusted certificates are stored. See *lariza-usage*(1).
-~/.config/lariza/user-scripts
+~/.local/share/lariza/user-scripts
Directory to store user-supplied JavaScript snippets. See *lariza-usage*(1).
~/.local/share/lariza/web_extensions