From owner-freebsd-questions@FreeBSD.ORG Thu Jan 12 21:00:43 2012 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 8E2881065670 for ; Thu, 12 Jan 2012 21:00:43 +0000 (UTC) (envelope-from perrin@apotheon.com) Received: from oproxy3-pub.bluehost.com (oproxy3.bluehost.com [IPv6:2605:dc00:100:2::a3]) by mx1.freebsd.org (Postfix) with SMTP id 59B898FC1A for ; Thu, 12 Jan 2012 21:00:43 +0000 (UTC) Received: (qmail 1294 invoked by uid 0); 12 Jan 2012 21:00:43 -0000 Received: from unknown (HELO box543.bluehost.com) (74.220.219.143) by oproxy3.bluehost.com with SMTP; 12 Jan 2012 21:00:43 -0000 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=apotheon.com; s=default; h=In-Reply-To:Content-Type:MIME-Version:References:Message-ID:Subject:To:From:Date; bh=N3pjIZ0P2dMK60QYANrjQP1S2suJmVlCtbzdQrm0epw=; b=KN6KaxNg3QP8adNw9J22W4YzOq1UXiJzREJWLNMsQE41zT8qzkVpnam+kr4cXkpvCvQ6ORb3lBYdYtUXy59cc653NDlIoxpKbmOrm28NDhRbYhU8kc7SPrAvUfUm9XbB; Received: from c-24-8-180-234.hsd1.co.comcast.net ([24.8.180.234] helo=localhost) by box543.bluehost.com with esmtpsa (TLSv1:AES128-SHA:128) (Exim 4.76) (envelope-from ) id 1RlRlK-0003Tx-Hs for freebsd-questions@freebsd.org; Thu, 12 Jan 2012 14:00:42 -0700 Date: Thu, 12 Jan 2012 14:00:42 -0700 From: Chad Perrin To: freebsd-questions@freebsd.org Message-ID: <20120112210042.GB5977@hemlock.hydra> Mail-Followup-To: freebsd-questions@freebsd.org References: <20120104165405.GF8500@hemlock.hydra> <8C0EEF92-18FD-45A8-90EF-F26EC8762704@googlemail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <8C0EEF92-18FD-45A8-90EF-F26EC8762704@googlemail.com> User-Agent: Mutt/1.5.21 (2010-09-15) X-Identified-User: {2737:box543.bluehost.com:apotheon:apotheon.com} {sentby:smtp auth 24.8.180.234 authed with perrin@apotheon.com} Subject: Re: Browser X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 12 Jan 2012 21:00:43 -0000 On Wed, Jan 04, 2012 at 08:48:35PM +0000, Peter Harrison wrote: > > First impressions of xxxterm are that it's very good. The keybinding is > quite as good as uzbl or vimperator on firefox, but it's live-able > with, and it seems to have fewer performance or configuration > downsides. I've been using xxxterm basically since this email -- not exclusively, but increasingly heavily, especially after a recent release (possibly prompted by a question I posted to the xxxterm discussion forum) added some more buffer commands for tab navigation. I have actually taken to installing independently of the software management system on one system, though I'm using the version in ports on another (less-used) system. It is surprisingly easy to add buffer commands in source (and recompile) when needed, and (the rest of the time) keybinding setup in the config file is even easier. There are some capabilities of Firefox on which I rely for specific purposes, including SOCKS proxy support and some stuff I get via the extension system, that are not supported by xxxterm. If I could get everything else I use with Firefox in xxxterm, solving the SOCKS proxy problem would be a relatively easy fix (via external tools), but because I need Firefox for those other purposes as well I have not bothered. What I am finding is that creative use of Sessions in xxxterm makes my "workflow" with two xxxterm instances running much preferable for the vast majority of purposes to any workflow I've been able to get working in Firefox. I keep one xxxterm instance just for the main_session Session, for opening random pages, and the other instance for use with other Sessions as needed. All in all, I'm much happier with xxxterm than with Firefox, and only lament the fact that there are a couple things I would like to be able to do with xxxterm that I (so far) only get from Firefox. I'll look into the possibility of implementing some of them (such as functionality similar to the HTTPS Everywhere extension, preferably compatible with the URI list used by HTTPS Everywhere so that a separate list need not be maintained) for xxxterm, and contributing patches to that effect, when I find time. -- Chad Perrin [ original content licensed OWL: http://owl.apotheon.org ]