601 reputation
1517
bio website blog.codekills.net
location Toronto, Canada
age 26
visits member for 5 years, 1 month
seen Oct 1 at 16:57

pycon.ca, python, http, vim, javascript, postgres, bash, actionscript, motorcycles, mercurial, toronto, startups

Twitter: http://twitter.com/wolever
Email: david@wolever.net
Blog: http://blog.codekills.net
GPG: B230230D
GitHub: https://github.com/wolever
Bitbucket: https://bitbucket.org/wolever
StackOverflow: http://stackoverflow.com/users/71522/wolever
Resume: http://careers.stackoverflow.com/wolever
LinkedIn: http://www.linkedin.com/in/wolever
Reddit: http://www.reddit.com/user/wolever
Callsign: VA3WVR


Oct
16
revised VirtualBox incredibly slow (CPU bound) with Debian host and guest
added 216 characters in body; edited tags
Oct
16
awarded  Yearling
Oct
15
revised VirtualBox incredibly slow (CPU bound) with Debian host and guest
added 104 characters in body
Oct
15
comment VirtualBox incredibly slow (CPU bound) with Debian host and guest
1 gig. When I check free -m it shows that I've got pleanty free and I'm not swapping (the host is headless Deb 6, so it's only running the core system, ssh and virtualbox).
Oct
14
comment VirtualBox incredibly slow (CPU bound) with Debian host and guest
The disks are set to “grow”… But if that were my issue, I would expect to see a bit of disk I/O on the host… No? Oh well, maybe I'll try that later.
Oct
14
comment VirtualBox incredibly slow (CPU bound) with Debian host and guest
Since asking, I have updated to the current 4.1.4 binary from virtualbox.org… But unfortunately it looks like I'm still having the same sorts of issues.
Oct
13
asked VirtualBox incredibly slow (CPU bound) with Debian host and guest
Aug
26
comment Chrome: remove URL from autocomplete which doesn't show up in history?
@Keltari: the question you linked to is not relevant: the solution there is to remove the offending site from my history, but I've already done that.
Aug
26
awarded  Critic
Aug
26
comment Chrome: remove URL from autocomplete which doesn't show up in history?
I did not clear my history, I only removed the offending URLs. As you can see from the screenshot, searching the history for gihub.com doesn't return anything, but it still appears in the omnibar suggestions.
Aug
26
asked Chrome: remove URL from autocomplete which doesn't show up in history?
Aug
11
comment Simplest way to run an authenticated SMTP server on Linux?
There are two reasons I'd rather not use them: 0) they won't let me use an arbitrary port (and ISPs around here block smtp/smtp+tls), 1) I believe they will require that I validate the source addresses (which is a problem for me, as I use a bunch of different “from” addresses).
Aug
11
asked Simplest way to run an authenticated SMTP server on Linux?
Jul
20
comment Make Chrome's omni bar search past URLs?
Hhmm… Possibly. It looks like typing the domain is the key… Although I guess you're still out of luck if you need to type more than just the domain to find what you want.
Jul
20
comment Make Chrome's omni bar search past URLs?
To clarify, I do sort of get something like that for some things (eg, img.skitch.com/20110720-knhgs3ia3nr3wj2uassaiy3fgg.png ), but it's not very consistent (ex, img.skitch.com/20110720-m2e97utpxe223hi7mpw6b1mak7.png ) and it often doesn't show me what I want (ex, the File.html example in my original post).
Jul
20
comment Make Chrome's omni bar search past URLs?
What happens if you go to help.adobe.com/en_US/FlashPlatform/reference/actionscript/3/… — does it show up in your omni bar after that?
Jul
20
asked Make Chrome's omni bar search past URLs?
Jul
10
comment Firefox: use ctrl-n and ctrl-p to select the next/previous item in the Awesome Bar
Also: bugzilla.mozilla.org/show_bug.cgi?id=354637
Jul
10
comment Firefox: use ctrl-n and ctrl-p to select the next/previous item in the Awesome Bar
Related: support.mozilla.com/en-US/questions/802233
Jul
10
comment Chrome: switch tabs with exactly one key?
Nope. The plugins that I use in Safari and Firefox simply ignore the keystroke if you're in a text field. And can you be more specific by “not how Chrome currently works”? Is there any reason plugins couldn't simply check the originalTarget of the key press event to determine if it's an input?