After boarding is complete, I sometimes walk to the business class purser and ask for today's paper. Since I usually fly in the evenings, Lufthansa stewards never deny this request for they are not going to need the paper anymore -- there's nothing more boring than old news. On Swiss flights, I always get a categorical "no" as the answer, the reason being that only business class passengers get papers. It's worth to note that Lufthansa has shelves with papers in the gate area, so I only rarely have to ask the in-flight crew, usually only when the Financial Times wasn't available for grabs. Swiss doesn't consider this an important service.
Cheap economy tickets are not rebookable. However, I cannot afford to spend twice or thrice the amount for a ticket, just to be flexible. I have often arrived at airports early. If I am on a Lufthansa flight, I can usually get switched to an earlier flight for free, or for the rebooking fee of 35 EUR. Swiss has never made a compromise. I have had to spend additional nights in a place just because there weren't any seats in my booking class, even though the flight was nearly empty. I know that Swiss is actually performing according to the rules. But one reason why I like Lufthansa so much is because they often bend the rules to please their passengers, no matter whether they are students or high-shot managers. Since Swiss wants to see themselves as the luxury airline, they have no concept of people who can't afford to pay shitloads. Typical Swiss, in some ways.
Lufthansa serves meals even on short flights if you fly between 18:00 and 21:00 hours. Swiss offers sandwiches whose consistency suggest they should be used to lessen the impact in case the airplane goes down, not eaten.
Lufthansa has great Florida orange juice. Swiss has some cheap crap from the supermarket.
Lufthansa serves free alcoholic beverages (incl. beer). Swiss charges Swiss prices (4 EUR for a 0,33 litre can of beer).
# find "foo" followed by whitespace and "bar", even across lines $ vim $SOMETHING 'g/foo\_s*bar/' # words ending in "bar" $ vim $SOMETHING 'g/bar\>/' # words starting with "foo" $ vim $SOMETHING 'g/\<foo/'... and more. What does $SOMETHING have to be set to? Update: Neil Moore suggests the following shell function:
vgrep () local S="$1"; shift vim -es +"argdo g/$S" +':q!' "$@"This works. I shall be posting any improvements I make over the next couple of weeks in another blog post. If there are any. But I suppose options like -i and -v might be good to have.
cirrus:~/.var/vim> ls -l drwxrwx--- 2 madduck madduck 6 2005-09-27 14:54 view/ -rw------- 1 madduck madduck 198580452 2006-01-20 21:12 viminfo -rw------- 1 madduck madduck 182227200 2006-01-20 18:35 viminfo.tmp -rw------- 1 madduck madduck 0 2006-01-20 18:35 viminfx.tmp -rw------- 1 madduck madduck 0 2006-01-20 18:34 viminfy.tmp -rw------- 1 madduck madduck 0 2006-01-20 18:33 viminfz.tmpSo something corrupted viminfo, vim's scratchpad, which explains it all. Thanks to those who have expressed their condolescences.
lapse:~> ps up 18139
USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND
madduck 18139 2.6 26.8 225460 214645 pts/10 S+ 01:23 0:01 vim
^^^^^^ ^^^^^^
I don't claim I understand memory management. But what the heck is going on?
If I start vim without my configuration (vim -u NONE), the problem goes
away. However, starting vim on another machine (remote, via non-X-forwarding
SSH) with the same configuration, it uses a few megabytes, no more.
lapse:~> host -t aaaa ethereal.net.nyud.net. 217.237.151.97 ethereal.net.nyud.net AAAA record not found at www-proxy.M1.srv.t-online.de, server failureServer failure? Fuck off! What's even worse is that one single request causes their servers to send back about 1'500 ServFail messages. And all this just because electricsheep uses curl, which tries IPv6 before it falls back to IPv4. How na ve.
| [*] | to set things straight with Wouter's post: I thought it kind of sounded like I was going to present my doctoral thesis at FOSDEM 2006. Unfortunately, that is not (yet) the case. My proposal was accepted, but I haven't been able to start yet, so what I was planning to do for the conference was to pick two ideas I had for Debian workflow improvement and present them alongside a short overview of the current workflow. This fulfills two goals for me. One, I am forced to write down these ideas, and two, I get them out into the open for people to discuss, develop, and/or slam them. |
Nobody expects the Finnish Inquisition: Confessions of a package torturer
Debian-Volatile - behind the scenes
Improving workflow in Debian through process integration
reuse and improvethese tools, to better integrate them, and to make them more accessible by providing abstraction wrappers with interfaces intuitive to Debian developers. It is further the intent for these tools to be optional and fully compatible to existing practices, thus not forcing developers to adapt. The research starts with process analysis and studies of the work habits on the side of the developers, and targets the final output of tools, which implement improved workflow in Debian package management through meaningful integration of existing (and proven) methods
Debtags, and what you can do with it today
Inside the Debian menu system
Debian Installer internals
The Debian GNU/kFreeBSD port
#!/bin/zsh -e send() echo $@ >&p echo "sending: $@" >&2 recv() read line <&p echo "received: $line" >&2 echo $line coproc openssl s_client -connect pop.googlemail.com:995 while ! recv grep -q '^\+OK'; do sleep 0.001; done send user $1 recv > /dev/null send pass $2 recv > /dev/null send stat set -- recv for i in 1..$2 ; do send dele $i recv > /dev/null done send quit recv > /dev/null exit 0and off I go. The POP3 server only ever gives you access to a few hundreds of your mails, so I figured I'd just call this script a couple of times, until my inbox would be a little less full. (I should have used python and a POP3 module for this. :)) Yeah, but forget it. Deleting messages from the POP server doesn't delete the messages from the inbox. Not even If I set it in my preferences. Great. New Gmail account created, my mission: fill their servers to the brim. Update: apparently the bug has been fixed. Now messages deleted via POP3 are moved to the trash, where they remain for 30 days, or until I manually delete them. Magnificent, back to the old problem. Will you please give me 5Gb additional space, Google?
cirrus:~> GET http://ftp-master.debian.org/ziyi_key_2006.asc gpg --import
gpg: key 2D230C5F: public key "Debian Archive Automatic Signing Key (2006)
<ftpmaster<@t>debian.org>" imported
gpg: Total number processed: 1
gpg: imported: 1
cirrus:~> gpg --check-sigs --fingerprint 2D230C5F
pub 1024D/2D230C5F 2006-01-03 [expires: 2007-02-07]
Key fingerprint = 0847 50FC 01A6 D388 A643 D869 0109 0831 2D23 0C5F
uid Debian Archive Automatic Signing Key (2006) <ftpmaster<@t>debian.org>
sig!3 2D230C5F 2006-01-03 Debian Archive Automatic Signing Key
(2006) <ftpmaster<@t>debian.org>
sig! 2A4E3EAA 2006-01-03 Anthony Towns <aj<@t>azure.humbug.org.au>
sig! 4F368D5D 2006-01-03 Debian Archive Automatic Signing Key
(2005) <ftpmaster<@t>debian.org>
sig! 29982E5A 2006-01-04 Steve Langasek <vorlon<@t>dodds.net>
sig! FD6645AB 2006-01-04 Ryan Murray <rmurray<@t>cyberhqz.com>
sig! AB2A91F5 2006-01-04 James Troup <james<@t>nocrew.org>
and then I check the trust path from my key to at least one of the keys
used to sign the archive key. Only if I find an acceptable path will I then
tell APT to trust the key:
cirrus:~> gpg --export -a 2D230C5F sudo apt-key add - OkNote that the key is signed with the previous archive key, so theoretically you can just build on your previous trust. Until Debian finally gets a proper PKI in place, this seems like the best way to do it.
Next.