33 lines
1.2 KiB
HTML
33 lines
1.2 KiB
HTML
|
<!DOCTYPE html>
|
||
|
|
<html>
|
||
|
|
<head>
|
||
|
|
<meta charset="utf-8">
|
||
|
|
<title>Let's Hint some words</title>
|
||
|
|
</head>
|
||
|
|
<body>
|
||
|
|
<h1>Word hints</h1>
|
||
|
|
|
||
|
|
<h2>Smart hints</h2>
|
||
|
|
<p>In qutebrowser, urls can not only be hinted with letters and
|
||
|
|
numbers, but also with <a href="../words.txt">words</a>. When there is
|
||
|
|
a sensible url text available, qutebrowser will even use that
|
||
|
|
text to create a <a href="../smart.txt">smart</a> hint.</p>
|
||
|
|
|
||
|
|
<h2>Filled hints</h2>
|
||
|
|
<p>When no smart hints are available, because the hint text is
|
||
|
|
<a href="../l33t.txt">too</a> short or <a href="../l33t.txt">l33t</a> to
|
||
|
|
use, words from a dictionary will be used.</p>
|
||
|
|
|
||
|
|
<h2>Hint conflicts</h2>
|
||
|
|
<p>Of course, hints have to be unique. For instance, all hints
|
||
|
|
below should get a different hint, whether they're smart or
|
||
|
|
not:</p>
|
||
|
|
<ul>
|
||
|
|
<li><a href="../hinting.txt">hinting</a> should be a smart hint</li>
|
||
|
|
<li><a href="../l33t.txt">word</a> is a prefix of words</li>
|
||
|
|
<li><a href="../l33t.txt">3</a> is too 1337</li>
|
||
|
|
<li><a href="../l33t.txt">4</a> is too 1337</li>
|
||
|
|
</ul>
|
||
|
|
</body>
|
||
|
|
</html>
|