uzbl. A browser that adheres to the unix philosophy.

riivo · 2009-11-09 20:03:17

securitybreach, doesn't libwebkit 1.1.15.3 give you segfault?

ArchDuke · 2009-11-10 17:41:36

Wow the new release/phase is really nice. I just wanted to give a shout out to those who are making it happen.

securitybreach · 2009-11-10 23:31:47

riivo wrote:

securitybreach, doesn't libwebkit 1.1.15.3 give you segfault?

Nope.

UPDATE: you can also use a new webkit version if you compile enchant with "--disable-zemberek"

http://www.uzbl.org/news.php?id=17

Basically you have to build the enchant package with ABS http://wiki.archlinux.org/index.php/ABS
and add --disable-zemberek to the ./configure line. Then run makepkg and install it with pacman -U packagename.pkg.tar.gz. After, that it works great.The way I understood it is a problem with the package enchant and one of its language sets.

Thanks

Last edited by securitybreach (2009-11-11 01:06:42)

yvonney · 2009-11-11 01:20:52

I am reading this better again. I think it will answer some:

http://www.uzbl.org/readme.php

XDG basedir spec
http://standards.freedesktop.org/basedi … c-0.6.html

1) thinking to install libwebkit latest in AUR
I'm have instaled 20091108-experimental and thought to install a very recent libwebkit.
The two in AUR are the -light one and the -newest one.
Both seem to want gtk-doc and appear to have new dependencies.

The question is: find a light version to avoid unecessaries. (gnome stuff etc.)
The latest libwebkit having more dependencies?
And aside: I guess there's a way to only download a package via pacman (that's not in AUR) and alter the PKGBUILD and then install.

2) I Installed latest experimental 20091108

Though, prior to that to clear out old version I did:

find / -name uzbl

Then: I deleted or renamed the folders of everything found. The /usr/share/uzbl stuff and what I'd
ignorantly put in ~/.config/uzbl and ~..local/share/uzbl weeks ago.

That means I have cleaned out everthing from the old version right?

As I would like to have as much, 'default' as possible at this point, and in my home folder.
I would very much like to know if I can take the entire: /usr/share/uzbl/examples/data/uzbl folder
and put in into:

 ~/.local/share ?   
um, or would that be the ~/.config ? 
or,  both?

Initially, to get going right are there other files I should move etc. AFTER I've assumedly done
the best thing and moved the example uzbl folder to the right location.

VERY interested!!!!!

oh, where do I put lich's uzbl-default.css file? and what do I rename/change?

I love uzbl: maybe there's a way to have a script that removes the need for firefox's 
scrapbook add-on. Maybe a PDF creation script and some way to view/database them,  
OR?

Sorry. I have read much though not had time to do my very best.

Last edited by yvonney (2009-11-19 17:48:08)

securitybreach · 2009-11-11 03:16:29

Neither libwebkits require any gnome-libs just gtk2 and a couple more (just read the AUR pages http://aur.archlinux.org/packages.php?O … Search=Go)

I run only XMonad with no kde or gnome libs and I use libwebkit-git version/Uzbl-git. As long as you follow my preivous post about rebuilding the package enchant, you will no problem. Also, there was no need to rename all uzbl folders, you could of just copied the files from /usr/share/uzbl/examples/config to ~/.config/uzbl/ and the data ones in that dir to ~/.local/share/uzbl. You then would have only the defaults for the version of Uzbl you installed.

Thanks

Last edited by securitybreach (2009-11-11 03:23:16)

yvonney · 2009-11-11 03:33:05

I have stayed with the pre-problem version of libwebkit to date as I needed gtk-doc for either of the -newest or -light later versions. Did you install gtk-doc to get the latest version from AUR to build. I will find out probably myself when I do the enchant addline: --disable-zemberek build and then libwebkit-git. I tried the -light and the -newest yet not the -git version. Shoulda done the -git version like you. funny I missed it, it wasn't version dated I don't think, though I guess -git's git, as in latest.

I run xmonad and scrotwm

Also: Did see/read-about the enchant tips though and thanks again!

The renaming (file or folder) is something I do as a temporary thing when I'm not sure I want to delete as I may want to compare. Sorry to not be clear earlier on that.

you could of just copied the files from /usr/share/uzbl/examples/config to ~/.config/uzbl/
and the data ones in that dir to ~/.local/share/uzbl. You then would have only defaults

The above comment of your is of interest. I should study the XDG basedir spec and also try to get your defaults only files move correct.

I need to be sure I have the: 'data ones' as you said chosen correctly andI guess it's a config folder.

Here's my two paths to folders:

/usr/share/uzbl/examples/config/uzbl  
[has just 2 files, config and cookies in it.]

/usr/share/uzbl/examples/data/uzbl  
[i assume all the folders and files in here are the 'data' ones?]

I love to get things right. No sure what's what, exactly.

Last edited by yvonney (2009-11-15 22:50:25)

securitybreach · 2009-11-11 03:55:38

/usr/share/uzbl/examples/config/uzbl = ~/.config/uzbl

/usr/share/uzbl/examples/data/uzbl = ~/.local/share/uzbl

Hope that helps

Thanks

yvonney · 2009-11-11 04:19:14

clear and apparently quite straight-forward.
I couldn't be sure, quite, last version nor this one.
That'll probably be useful to others that aren't quite sure as well. nice!

Last edited by yvonney (2009-11-11 04:27:00)

Dieter@be · 2009-11-11 07:56:16

i highly recommend, when using uzbl-browser to remove all your old scripts in your $XDG_DATA_HOME unless you're sure they do not come by default (i.e. are not in $PREFIX/share/uzbl/examples/data/uzbl)
the reason: uzbl-browser can do (and is configured to do so by default) "$PATH-like" expansion of your @scripts_dir. in other words, if the script is in $XDG_DATA_HOME it will use it, otherwise it will fallback automatically to the one in $PREFIX/share/uzbl/examples/data/uzbl

securitybreach · 2009-11-11 15:44:13

Thanks, good to know.

Thanks

hatten · 2009-11-11 22:53:48

I tried to change the link follower to use the home row instead of numbers, but it didn't quite work like it should. First i tried copying the whole file from the wiki, http://www.uzbl.org/wiki/configurable-jump , but that one didn't work with pages that got more than 10 links. If i would press hta for a link it wouldn't accept more than h and then start loading a page.

After that i tried following the instructions, and that didn't work at all. I'm not especially familiar with javascript so i bet it is a syntax error. this is what my file looked like after i had edited it.

/* This is the basic linkfollowing script.
 * Its pretty stable, only using numbers to navigate.
 *
 * TODO: Some pages mess around a lot with the zIndex which
 * lets some hints in the background.
 * TODO: Some positions are not calculated correctly (mostly
 * because of uber-fancy-designed-webpages. Basic HTML and CSS
 * works good
 * TODO: Still some links can't be followed/unexpected things
 * happen. Blame some freaky webdesigners ;)
 */

//Just some shortcuts and globals
var uzblid = 'uzbl_link_hint';
var uzbldivid = uzblid + '_div_container';
var doc = document;
var win = window;
var links = document.links;
var forms = document.forms;
var trans = ['h', 'u', 't', 'e', 'n', 'o', 's', 'a', 'd', 'i'];
//Make onlick-links "clickable"
try {
    HTMLElement.prototype.click = function() {
        if (typeof this.onclick == 'function') {
            this.onclick({
                type: 'click'
            });
        }
    };
} catch(e) {}
//Catch the ESC keypress to stop linkfollowing
function keyPressHandler(e) {
    var kC = window.event ? event.keyCode: e.keyCode;
    var Esc = window.event ? 27 : e.DOM_VK_ESCAPE;
    if (kC == Esc) {
        removeAllHints();
    }
}
//Calculate element position to draw the hint
//Pretty accurate but on fails in some very fancy cases
function elementPosition(el) {
    var up = el.offsetTop;
    var left = el.offsetLeft;
    var width = el.offsetWidth;
    var height = el.offsetHeight;
    while (el.offsetParent) {
        el = el.offsetParent;
        up += el.offsetTop;
        left += el.offsetLeft;
    }
    return [up, left, width, height];
}
//Calculate if an element is visible
function isVisible(el) {
    if (el == doc) {
        return true;
    }
    if (!el) {
        return false;
    }
    if (!el.parentNode) {
        return false;
    }
    if (el.style) {
        if (el.style.display == 'none') {
            return false;
        }
        if (el.style.visibility == 'hidden') {
            return false;
        }
    }
    return isVisible(el.parentNode);
}
//Calculate if an element is on the viewport.
function elementInViewport(el) {
    offset = elementPosition(el);
    var up = offset[0];
    var left = offset[1];
    var width = offset[2];
    var height = offset[3];
    return up < window.pageYOffset + window.innerHeight && left < window.pageXOffset + window.innerWidth && (up + height) > window.pageYOffset && (left + width) > window.pageXOffset;
}
//Removes all hints/leftovers that might be generated
//by this script.
function removeAllHints() {
    var elements = doc.getElementById(uzbldivid);
    if (elements) {
        elements.parentNode.removeChild(elements);
    }
}
//Generate a hint for an element with the given label
//Here you can play around with the style of the hints!
function generateHint(el, label) {
    var pos = elementPosition(el);
    var hint = doc.createElement('div');
    hint.setAttribute('name', uzblid);
    label = '' + label;
    var s = '';
    for(var x = 0; x < label.length; x++){
        s += trans[label[x]];
    }
    label = s;
    hint.innerText = label;
    hint.style.display = 'inline';
    hint.style.backgroundColor = '#B9FF00';
    hint.style.border = '2px solid #4A6600';
    hint.style.color = 'black';
    hint.style.fontSize = '9px';
    hint.style.fontWeight = 'bold';
    hint.style.lineHeight = '9px';
    hint.style.margin = '0px';
    hint.style.padding = '1px';
    hint.style.position = 'absolute';
    hint.style.zIndex = '1000';
    hint.style.left = pos[1] + 'px';
    hint.style.top = pos[0] + 'px';
    var img = el.getElementsByTagName('img');
    if (img.length > 0) {
        hint.style.left = pos[1] + img[0].width / 2 + 'px';
    }
    hint.style.textDecoration = 'none';
    hint.style.webkitBorderRadius = '6px';
    // Play around with this, pretty funny things to do :)
    hint.style.webkitTransform = 'scale(1) rotate(0deg) translate(-6px,-5px)';
    return hint;
}
//Here we choose what to do with an element if we
//want to "follow" it. On form elements we "select"
//or pass the focus, on links we try to perform a click,
//but at least set the href of the link. (needs some improvements)
function clickElem(item) {
    removeAllHints();
    if (item) {
        var name = item.tagName;
        if (name == 'A') {
            item.click();
            window.location = item.href;
        } else if (name == 'INPUT') {
            var type = item.getAttribute('type').toUpperCase();
            if (type == 'TEXT' || type == 'FILE' || type == 'PASSWORD') {
                item.focus();
                item.select();
            } else {
                item.click();
            }
        } else if (name == 'TEXTAREA' || name == 'SELECT') {
            item.focus();
            item.select();
        } else {
            item.click();
            window.location = item.href;
        }
    }
}
//Returns a list of all links (in this version
//just the elements itself, but in other versions, we
//add the label here.
function addLinks() {
    res = [[], []];
    for (var l = 0; l < links.length; l++) {
        var li = links[l];
        if (isVisible(li) && elementInViewport(li)) {
            res[0].push(li);
        }
    }
    return res;
}
//Same as above, just for the form elements
function addFormElems() {
    res = [[], []];
    for (var f = 0; f < forms.length; f++) {
        for (var e = 0; e < forms[f].elements.length; e++) {
            var el = forms[f].elements[e];
            if (el && ['INPUT', 'TEXTAREA', 'SELECT'].indexOf(el.tagName) + 1 && isVisible(el) && elementInViewport(el)) {
                res[0].push(el);
            }
        }
    }
    return res;
}
//Draw all hints for all elements passed. "len" is for
//the number of chars we should use to avoid collisions
function reDrawHints(elems, chars) {
    removeAllHints();
    var hintdiv = doc.createElement('div');
    hintdiv.setAttribute('id', uzbldivid);
    for (var i = 0; i < elems[0].length; i++) {
        if (elems[0][i]) {
            var label = elems[1][i].substring(chars);
            var h = generateHint(elems[0][i], label);
            hintdiv.appendChild(h);
        }
    }
    if (document.body) {
        document.body.appendChild(hintdiv);
    }
}
//Put it all together
function followLinks(follow) 
if(follow){
    var i = '';
    for(var x = 0; x < follow.length; x++){
        i += '' + trans.indexOf(follow[x]);
    }
    follow = i;
}
   {
    var s = follow.split('');
    var linknr = parseInt(follow, 10);
    if (document.body) document.body.setAttribute('onkeyup', 'keyPressHandler(event)');
    var linkelems = addLinks();
    var formelems = addFormElems();
    var elems = [linkelems[0].concat(formelems[0]), linkelems[1].concat(formelems[1])];
    var len = (elems[0].length + '').length;
    var oldDiv = doc.getElementById(uzbldivid);
    var leftover = [[], []];
    if (linknr + 1 && s.length == len && linknr < elems[0].length && linknr >= 0) {
        clickElem(elems[0][linknr]);
    } else {
        for (var j = 0; j < elems[0].length; j++) {
            var b = true;
            var label = j + '';
            var n = label.length;
            for (n; n < len; n++) {
                label = '0' + label;
            }
            for (var k = 0; k < s.length; k++) {
                b = b && label.charAt(k) == s[k];
            }
            if (b) {
                leftover[0].push(elems[0][j]);
                leftover[1].push(label);
            }
        }
        reDrawHints(leftover, s.length);
    }
}
followLinks('%s');

Dieter@be · 2009-11-15 10:01:54

all the different linkfollowing scripts are really getting out of hand imho.
see http://lists.uzbl.org/pipermail/uzbl-de … 00473.html

hatten · 2009-11-15 10:22:15

Got it working with follow_numbers_configurable.js, thanks.

Lich · 2009-11-18 11:26:42

Problem with my css is fixed. It was only the uzbl wiki's "fault". It was escaping my "file://", turning it into "file:". Make the necessary adjustments and you can enjoy my dark style in all it's glory

brisbin33 · 2009-11-18 14:48:59

hey i just wanted to stop by and say nice job with the latest 'version'.

i switched from exp to master some months ago when the new config syntax dropped and (even after updating my config) the thing just didn't work. at that point it just felt really sluggish and i was blown away at how fast chrome was... so i switched.

last week i pleasantly found that the updated master branch was just as fast as chrome and i'm now happily back with uzbl.

thanks devs.

securitybreach · 2009-11-18 16:25:36

Lich wrote:

Problem with my css is fixed. It was only the uzbl wiki's "fault". It was escaping my "file://", turning it into "file:". Make the necessary adjustments and you can enjoy my dark style in all it's glory

I still can not get the colors to show only certain things turn dark:

Here is my lich.css http://pastebin.com/f5ee09f55 and my uzbl/config: http://pastebin.com/f49892b2e

Any ideal why my background is still white?

Thanks

BTW I am running Uzbl-git version 20091107-2

Last edited by securitybreach (2009-11-19 02:32:26)

Lich · 2009-11-19 09:42:30

securitybreach wrote:

Lich wrote:
Problem with my css is fixed. It was only the uzbl wiki's "fault". It was escaping my "file://", turning it into "file:". Make the necessary adjustments and you can enjoy my dark style in all it's glory
I still can not get the colors to show only certain things turn dark:
http://thumbnails24.imagebam.com/5659/b … 581383.gif

http://thumbnails21.imagebam.com/5659/e … 581408.gif

Here is my lich.css http://pastebin.com/f5ee09f55 and my uzbl/config: http://pastebin.com/f49892b2e
Any ideal why my background is still white?

Thanks
BTW I am running Uzbl-git version 20091107-2

I have no idea why this is happening, I am using experimental though, not the new one, the one before the latest -git release. Your setup seems fine...I seriouslly don't know what may be causing this. Did you try asking in #uzbl? Maybe Dieter and Rob have some hints?

jt512 · 2009-11-21 00:01:39

I have tried using the current stable and experimental uzbl packages in the AUR, and with neither can I get the uzbl-tabbed-specific key bindings to work. For example, in uzbl-tabbed, 'gn' does not open a new tab. Has anyone else had trouble with this? Does anybody know how to get them to work?

Jay

Last edited by jt512 (2009-11-21 00:02:09)

securitybreach · 2009-11-21 00:27:31

From the Uzbl website news:

Hilights:
splitup and better separation of concerns: uzbl-core, uzbl-browser and uzbl-tabbed.
Basically:
Uzbl-core is the old uzbl, minus the built-in event handling, and minus the keyboard interface. (statusbar is still there, but more flexible)
Uzbl-browser is a complete, "working out of the box" browser implementation based on uzbl-core and many of the scripts we already knew. It handles a lot of the events from uzbl-core, it also handles
keyboard input, it updates the statusbar when appropriate, and also some more things.. (read on)
Uzbl-tabbed is the old uzbl-tabbed, but refactored to work with the new uzbl-browser. (note: this is not done yet. uzbl-tabbed is broken in this release, you'll have to wait a bit or try out jake's C++ tab manager)

http://www.uzbl.org/news.php?id=18

Thanks

Last edited by securitybreach (2009-11-21 00:29:56)

brisbin33 · 2009-11-24 19:16:15

FYI: i've converted [well, tried to convert] the README to a manpage. after the thankgiving weekend i'll try to reach out the the team and see if they approve/want it, but for now i figured i'd post it here (i've compulsively typed man uzbl enough to find it useful).

i thought it was a good project for a first manpage as all the content was already in the README, it just needed to be formatted to work with man.

anyway, comments welcome; short of some brief googling and then trial and error i probably don't even know of all the 'manpage etiquettes' i might've broken.

to view it locally:

mkdir -p ./man/man1
wget -O ./man/man1/uzbl.1.gz http://pbrisbin.com:8080/shared/uzbl.1.gz
man -M ./man uzbl

to actually install it (not really recommended yet...)

wget -O ./uzbl.1.gz http://pbrisbin.com:8080/shared/uzbl.1.gz
sudo mv ./uzbl.1.gz /usr/share/man/man1/
man uzbl

Dieter@be · 2009-11-26 12:00:07

brisbin33 wrote:

FYI: i've converted [well, tried to convert] the README to a manpage. after the thankgiving weekend i'll try to reach out the the team and see if they approve/want it, but for now i figured i'd post it here (i've compulsively typed man uzbl enough to find it useful).
i thought it was a good project for a first manpage as all the content was already in the README, it just needed to be formatted to work with man.
anyway, comments welcome; short of some brief googling and then trial and error i probably don't even know of all the 'manpage etiquettes' i (...)

nice work! we need a manpage indeed. i just think we should have a way to automatically generate the manpage (they call this 'nroff' syntax or something like that?) based from our readme file (which is markdown), because maintaining two files that contain the same info is not fun

edit: and btw, you have a cool website. would be even cooler if you had a feed so I can track your new posts ("blog" kinda thing)

Last edited by Dieter@be (2009-11-26 12:05:59)

brisbin33 · 2009-11-28 01:16:22

Dieter@be wrote:

nice work! we need a manpage indeed. i just think we should have a way to automatically generate the manpage (they call this 'nroff' syntax or something like that?) based from our readme file (which is markdown), because maintaining two files that contain the same info is not fun

hmm, well i must've been doing it wrong, because i can't visualize automating what i did for that boring ass workday to get that manpage out of that readme (i did see someone on IRC ask about a program to convert whatever2nroff -- or groff? there weren't many responses...).

i did keep a copy of the readme as it was when i did the man i was planning on just diffing the current readme to it any time i updated and then updating the appropriate sections of my manpage.

Dieter@be wrote:

edit: and btw, you have a cool website. would be even cooler if you had a feed so I can track your new posts ("blog" kinda thing)

i appreciate the compliment, it would be a slow rss feed but a fun project to set it up... i'll look into it, thanks

hatten · 2009-11-28 09:11:24

Lich wrote:

securitybreach wrote:
Lich wrote:
Problem with my css is fixed. It was only the uzbl wiki's "fault". It was escaping my "file://", turning it into "file:". Make the necessary adjustments and you can enjoy my dark style in all it's glory
I still can not get the colors to show only certain things turn dark:
http://thumbnails24.imagebam.com/5659/b … 581383.gif

http://thumbnails21.imagebam.com/5659/e … 581408.gif

Here is my lich.css http://pastebin.com/f5ee09f55 and my uzbl/config: http://pastebin.com/f49892b2e
Any ideal why my background is still white?

Thanks
BTW I am running Uzbl-git version 20091107-2
I have no idea why this is happening, I am using experimental though, not the new one, the one before the latest -git release. Your setup seems fine...I seriouslly don't know what may be causing this. Did you try asking in #uzbl? Maybe Dieter and Rob have some hints?

I tried installing experimental, and no difference at all, there were still only a few things that got a darkened background

Dieter@be · 2009-11-28 10:22:58

brisbin33 wrote:

Dieter@be wrote:
nice work! we need a manpage indeed. i just think we should have a way to automatically generate the manpage (they call this 'nroff' syntax or something like that?) based from our readme file (which is markdown), because maintaining two files that contain the same info is not fun
hmm, well i must've been doing it wrong, because i can't visualize automating what i did for that boring ass workday to get that manpage out of that readme (i did see someone on IRC ask about a program to convert whatever2nroff -- or groff? there weren't many responses...).
i did keep a copy of the readme as it was when i did the man i was planning on just diffing the current readme to it any time i updated and then updating the appropriate sections of my manpage.

the manual approach works I guess, but automating things is always nicer.
there is a perl module to convert html to nroff man pages (http://linux.wareseeker.com/Programming … zip/325256). and markdown is designed to be converted into html, so maybe you could give that a try.

brisbin33 wrote:

Dieter@be wrote:
edit: and btw, you have a cool website. would be even cooler if you had a feed so I can track your new posts ("blog" kinda thing)
i appreciate the compliment, it would be a slow rss feed but a fun project to set it up... i'll look into it, thanks

Yeah for uzbl.org we use Dusty's mini-framework : http://www.zeroflux.org/projects/phatso
source code uzbl.org : http://github.com/Dieterbe/uzbl-website/

Nepherte · 2009-12-01 21:13:32

I've got a quick question: When I want to type a url, the url usually contains a '.' or a '/'. To get these keys in my keyboard layout, I have to use my shift key + another key to get them. The shift key however is considered as some modifier so instead of a '.' or a '/', I get '<Shift>.' and '<Shift>/'. How do I get the specified behavior?

Last edited by Nepherte (2009-12-01 21:13:49)

Arch Linux

#676 2009-11-09 20:03:17

Re: uzbl. A browser that adheres to the unix philosophy.

#677 2009-11-10 17:41:36

Re: uzbl. A browser that adheres to the unix philosophy.

#678 2009-11-10 23:31:47

Re: uzbl. A browser that adheres to the unix philosophy.

#679 2009-11-11 01:20:52

Re: uzbl. A browser that adheres to the unix philosophy.

#680 2009-11-11 03:16:29

Re: uzbl. A browser that adheres to the unix philosophy.

#681 2009-11-11 03:33:05

Re: uzbl. A browser that adheres to the unix philosophy.

#682 2009-11-11 03:55:38

Re: uzbl. A browser that adheres to the unix philosophy.

#683 2009-11-11 04:19:14

Re: uzbl. A browser that adheres to the unix philosophy.

#684 2009-11-11 07:56:16

Re: uzbl. A browser that adheres to the unix philosophy.

#685 2009-11-11 15:44:13

Re: uzbl. A browser that adheres to the unix philosophy.

#686 2009-11-11 22:53:48

Re: uzbl. A browser that adheres to the unix philosophy.

#687 2009-11-15 10:01:54

Re: uzbl. A browser that adheres to the unix philosophy.

#688 2009-11-15 10:22:15

Re: uzbl. A browser that adheres to the unix philosophy.

#689 2009-11-18 11:26:42

Re: uzbl. A browser that adheres to the unix philosophy.

#690 2009-11-18 14:48:59

Re: uzbl. A browser that adheres to the unix philosophy.

#691 2009-11-18 16:25:36

Re: uzbl. A browser that adheres to the unix philosophy.

#692 2009-11-19 09:42:30

Re: uzbl. A browser that adheres to the unix philosophy.

#693 2009-11-21 00:01:39

Re: uzbl. A browser that adheres to the unix philosophy.

#694 2009-11-21 00:27:31

Re: uzbl. A browser that adheres to the unix philosophy.

#695 2009-11-24 19:16:15

Re: uzbl. A browser that adheres to the unix philosophy.

#696 2009-11-26 12:00:07

Re: uzbl. A browser that adheres to the unix philosophy.

#697 2009-11-28 01:16:22

Re: uzbl. A browser that adheres to the unix philosophy.

#698 2009-11-28 09:11:24

Re: uzbl. A browser that adheres to the unix philosophy.

#699 2009-11-28 10:22:58

Re: uzbl. A browser that adheres to the unix philosophy.

#700 2009-12-01 21:13:32

Re: uzbl. A browser that adheres to the unix philosophy.

Board footer