Adeodato Sim : Markdown links with newlines in the anchor text
Links in Markdown can be done in a couple ways. First, similarly to
HTML links, where you place the link next to the anchor text, like this:
There is a beta version of Markdown in experimental that almost fixes the problem. This version introduces a new but similar syntax for links: you can omit the second pair of empty brackets. And when using that newer syntax, there is code in the program to change newlines into a space when looking for the link definition. It is not applied to the code path of the old syntax, though, which is a pity. This is all explained in bug #459885, with a patch as well (that applies both to 1.0.1 and 1.0.2). You can find packages with that patch applied here.
I am a [Debian](http://www.debian.org) Developer.
Or, if you feel this clutters your paragraphs too much, you can choose
an alternate syntax, which I prefer (particulary handy for very long
links):
I am a [Debian][] Developer. Bla bla bla...
[debian]: http://www.debian.org
There is however a gotcha with this alternate syntax, namely, anchor
text with spaces in them. This works fine:
I study Computer Science in [this University][].
[this University]: http://www.ua.es
But this does not:
Some years ago, I started studying Computer Science in [this
University][]. Bla bla bla...
[this University]: http://www.ua.es
This actually happens quite a lot when formatting the paragraphs in the
editor, which made this otherwise-pleasant syntax almost a no-go for me.
(Well, to be honest you could use it like this, but still:
Some years ago, I started studying Computer Science in [this
University][uni]. Bla bla bla...
[uni]: http://www.ua.es
)
There is a beta version of Markdown in experimental that almost fixes the problem. This version introduces a new but similar syntax for links: you can omit the second pair of empty brackets. And when using that newer syntax, there is code in the program to change newlines into a space when looking for the link definition. It is not applied to the code path of the old syntax, though, which is a pity. This is all explained in bug #459885, with a patch as well (that applies both to 1.0.1 and 1.0.2). You can find packages with that patch applied here.
Otavio is currently busy preparing the first release of D-I for
lenny. He is still polishng the release schedule but, as part of the
process, I sent a call for translation updates today.
The starting point is: 59 activated languages (including English) but
'only' 18 of them are 100%.
For others:
I went back to work today after something like a total of 6 weeks off. (2
weeks vacation, 4 weeks unpaid leave).
The month of January went pretty quickly really. The week in hospital with
Sarah was a blur. The week and a half afterwards was also pretty much a
blur. Then we had the week where things went a bit backwards, and then we
had this week, a few days of which were spent up north at an inn in Little
River, Mendocino County. Heck, let's just call the entire month a blur and
be done with it.
Sarah's doing pretty well now. Surgery on the 3rd, discharged on the 9th,
back in the Emergency Room on the 21st with tachycardia. Concerns about the
incision weeping on the 21st, and again on the 28th. General increase in
pain on the 28th, along with a few sleepless nights preceding.
But now, with a doubling of her beta blockers, some antibiotics, pain
killers, anti-inflammatories and sleeping tablets, she's feeling a bit more
human again, if not like a human pill bottle.
The surgical folks want to see her again on Monday to follow up how the
incision is going since they prescribed the antibiotics. The weeping has
calmed down significantly, but hasn't gone away completely.
A couple more months to go before we can call her "recovered".
Recently I've been debugging a SQL Server 2005 replication setup, where the "Distribution clean up" job for the distributor database was failing. The error message in the agent history was:
Another design decision for "dammit" is how to handle dependency loops between header files -- these may be intentional, but most often are not, and I'd like to find these because they often lead to confusing error messages.
I'm really pleased to announce here that one of the projects
With 

* Laptop running Linux is yet dream for me!
A person that I deeply respect and who is very know in Latvian IT society recently said that he often uses a quote of mine in his presentations. I completely forgot that I ever said that, but it sounds very much like what I would say, so I wanted to write it down so that I do not forget about it again:
I hacked together a little timesaver for developers this morning: omni
completion for Launchpad bugs in Vim's debchangelog mode. To use it, install
vim 7.1-138+1ubuntu3 once it hits the mirrors, open up a
debian/changelog file, type "LP: #", and hit Ctrl-X Ctrl-O. It'll
think for a while and then give you a list of all the bugs open in Launchpad
against the package in question, from which you can select to insert the bug
number into your changelog.
Here's a screenshot to make it clearer:
Thanks to Stefano Zacchiroli for doing the same for Debian bugs back in
July.

On Sunday, the day before