Add hotkeys for switching tabs

[chorizo.git] / man1 / lariza.usage.1

diff --git a/man1/lariza.usage.1 b/man1/lariza.usage.1
index 9db7a2cb50810fd0f1206c7871e179b63a1f76af..ebed6766d43e936913df2f42574af73765f38dd7 100644 (file)
--- a/man1/lariza.usage.1
+++ b/man1/lariza.usage.1
@@ -1,4 +1,4 @@
-.TH lariza 1 "2020-03-14" "lariza" "User Commands"
+.TH lariza 1 "2020-04-24" "lariza" "User Commands"
 .\" --------------------------------------------------------------------
 .SH NAME
 lariza.usage \- extended usage hints
@@ -51,6 +51,9 @@ Repeat the last search (backward).
 \fBMod1\fP + \fBc\fP
 Reload trusted certificates.
 .TP
+\fBMod1\fP + \fBa\fP / \fBMod1\fP + \fBs\fP
+Select tab to the left / right.
+.TP
 \fBF2\fP / \fBF3\fP
 Go backward and forward in current browser history.
 .P
@@ -126,16 +129,27 @@ Lines starting with \fB#\fP are ignored.
 .\" --------------------------------------------------------------------
 .SH "USER-SUPPLIED JAVASCRIPT FILES"
 After a page has been successfully loaded, the directory
-\fI~/.config\:/lariza\:/scripts\fP will be scanned and each file in it
-ending with \fB.js\fP will be run as a JavaScript file in the context of
-said page.
+\fI~/.config\:/lariza\:/user-scripts\fP will be scanned and each file in
+it ending with \fB.js\fP will be run as a JavaScript file in the context
+of said page.
 .P
 During development, you will most likely want to run \fBlariza\fP with
 $\fBLARIZA_ENABLE_CONSOLE_TO_STDOUT\fP enabled.
+.P
+\fBlariza\fP comes with the following scripts:
+.TP
+\fBhints.js\fP
+Press \fBf\fP (open link in current window) or \fBF\fP (open in new
+window) to activate link hints. After typing the characters for one of
+them, press \fBEnter\fP to confirm. Press \fBEscape\fP to abort.
+.P
+Those bundled scripts are automatically installed on \fBmake install\fP.
+To use them, though, make sure to link them to the directory mentioned
+above.
 .\" --------------------------------------------------------------------
 .SH "WEB EXTENSIONS"
-On startup, WebKit checks \fI~/.local/share/lariza/web_extensions\fP for
-any \fB.so\fP files. See
+On startup, WebKit checks \fI~/.config/lariza/web_extensions\fP for any
+\fB.so\fP files. See
 .UR http://\:blogs.igalia.com/\:carlosgc/\:2013/\:09/\:10/\:webkit2gtk-\:web-\:process-\:extensions/
 this blog post
 .UE
@@ -155,15 +169,15 @@ the GLib reference
 for more details. Lines starting with \fB#\fP are ignored.
 .P
 Those bundled web extensions are automatically compiled when you run
-\fBmake\fP. To use them, though, make sure to copy them to the directory
-mentioned above.
+\fBmake\fP and installed on \fBmake install\fP. To use them, though,
+make sure to link them to the directory mentioned above.
 .\" --------------------------------------------------------------------
 .SH "EXTERNAL URI HANDLER"
 \fBlariza\fP can launch an executable called
 \fIlariza-external-handler\fP. It will be passed the \(lqselected\(rq
 URI as a command line argument:
 .P
-.\f(CW
+\f(CW
 .nf
 $ lariza-external-handler -u https://github.com
 .fi
@@ -186,16 +200,16 @@ might simply load the current URI in a different browser. That's up to
 you.
 .\" --------------------------------------------------------------------
 .SH "TRUSTED CERTIFICATES"
-By default, \fBlariza\fP trusts whatever CAs are trusted by WebKit, i.e. by
-your GnuTLS installation. If you wish to trust additional certificates,
-such as self-signed certificates, the first thing you should do is try
-to add the appropriate CAs to your system-wide store.
+By default, \fBlariza\fP trusts whatever CAs are trusted by WebKit, i.e.
+by your GnuTLS installation. If you wish to trust additional
+certificates, such as self-signed certificates, the first thing you
+should do is try to add the appropriate CAs to your system-wide store.
 .P
 If you wish to add simple exceptions, you can grab the certificate and
 store it in the directory \fI~/.config/lariza/certs\fP. The filename
 must be equal to the hostname:
 .P
-.\f(CW
+\f(CW
 .nf
 \&$ echo | openssl s_client -connect foo.de:443 | openssl x509 >foo.de
 .fi
@@ -212,22 +226,6 @@ Note: This is NOT equal to certificate pinning. WebKit ignores
 user-specified certificates if the server's certificate can be validated
 by any system-wide CA.
 .\" --------------------------------------------------------------------
-.SH "USING LARIZA WITH TABBED"
-By default, \fBlariza\fP automatically launches an instance of suckless'
-\fBtabbed\fP(1).
-.P
-You can turn this feature off (see command line arguments) or you can
-specify a command line argument to embed \fBlariza\fP into an arbitrary
-container (XEMBED). Note that \fBlariza\fP will also automatically embed
-new windows in the same container.
-.P
-When using the automatically launched \fBtabbed\fP(1) instance, you
-can't use \fBtabbed\fP(1)'s \fBCtrl + Shift + Return\fP hotkey. This is
-because \fBtabbed\fP(1) is launched with \fB\-d\fP, so it knows nothing
-about \fBlariza\fP. However, \fBlariza\fP provides its own hotkey to
-launch a new window which will be embedded in the same instance of
-\fBtabbed\fP(1).
-.\" --------------------------------------------------------------------
 .SH "WEBKIT LOCAL STORAGE"
 WebKit does create files in your $\fBXDG_*\fP directories, i.e.
 \fI~/.local/share\fP or \fI~/.cache\fP. It's up to you what you want to