Archive for the ‘Computing’ Category.
6th June 2005, 10:00 am
The next stable version of [Debian][] codenamed Sarge was
supposed to be released today… They have either done it in a
really quiet way, or not at all — I fear that they missed their
target date again.
It’s a shame, for I guess there are still some server admins out there
who are waiting for a new stable version of Debian — I’ve been
running the “testing” distribution for a long time and I’m very
satisfied with the stability of it.
My original plan was to stick with Sarge and thus obtain a system
which would be stable and only receive security updates. I’m actually
not sure anymore if I’ll do that, or if I’ll keep moving along with
“testing”. Any Debian users out there — what do you plan to do?
4th June 2005, 07:31 pm
I’ve installed a new version of [GNU][] [Emacs][] on my [Debian][]
system. The cool thing about this version is that is has supprot for
multi-tty which means that it can show frames om multiple different
kinds of TTYs.
Normally you can start your Emacs in X and use emacsclient to
quickly bring up a new frame. This works fine — but in fact it’s a
little too much, for you always get a new frame (in the X environment)
when using emacsclient. If you are logged in using something like
SSH, then what you really want is to have emacsclient show a frame
on your terminal.
This is exactly what the Emacs multi-tty support project gives
you! Starting emacsclient with the $DISPLAY variable set gives you
a new frame in X, as you would expect. But if this variable is unset
(as it is in a SSH session without X forwarding) then you get your new
frame in the console. You then of course have access to Emacs just as
you left it, including all the buffers.
So I can now just leave my Emacs running at my computer, and to check
mail I just SSH to my box and connect to the running Emacs process.
There I just switch to my [Gnus][] buffer instead of having to kill it
first. Very sweet!
Oh, and by the way: the author says that emacsclient starts up
faster than vi… In fact, I think I’ll make vi a symlink to
emacsclient from now on… ;-)
2nd June 2005, 11:19 pm
You can now leave comments on all the pages here and not just on posts. “Pages” are [WordPress][] terminology for static things, such as my [PHP Tutorial][], and “posts” are the date-based stuff like what you’re reading now.
31st May 2005, 10:43 pm
Having just read the very interesting and throughout explaination by
Michel Fortin of his problems with the WordPress filters
when trying to get [PHP Markdown][] right, I think it’s amazing that
it works at all!
His experience together with the recent discussion started by
Denis de Bernardy about the plugin system (and specifically the
hooks offered to plugins) seems to suggest that the whole system could
use some rethinking. (And when doing so, then please document it! :-)
31st May 2005, 08:45 pm
I’ve installed a couple of cool plugins for WordPress on my site:
The Subscribe to Comments plugin lets you do exactly that:
subscribe to new comments on specific posts. It’s enabled by
default — but you of course have the choice to opt-out at any moment.
Please let me know if you find the notifications helpful or not, or if
you would rather see an opt-in solution instead.
A simple Permalink Redirect plugin that will enforce the
structure of my permalinks. Right now it only handles the
permalinks of posts, but I hope to see it updated to support
pages as well.
Finally a little funny plugin: WP-GoogleStats keeps track of
when the Googlebot pays my humble site a visit. You can see
the time of the last visit at the bottom of each page.
Tell me what you think of the new plugins!