@UlrikeFischer You may recall some time ago I was playing with that multiple option (a la footmisc) for postnotes, which uses \lastkern as a "signal". To make it work I had to store \lastkern at the beginning of the note, otherwise it was lost somewhere, and I didn't know why. I'm taking a closer look at this now, and some bisecting shows the culprit is \MakeLinkTarget. I don't know if this is relevant in any way, if it's avoidable, or if you should care, but... I thought mentioning it.
@UlrikeFischer Both. See this bit: github.com/gusbrs/postnotes/blob/…. \@@_multiple_store_lastkern: is storing the value of \lastkern. I started moving it down, until it went past \MakeLinkTarget, when the tests started to fail. I have two for the feature, one with hyperref the other without (because of footmisc), both fail at that point. I think it is that \smash, as far as I get.
@JosephWright The current state for the matrix server is that the server is running, but I'm still doing some tests to ensure that we don't overload the server when it actually gets used.
@gusbrs Well every whatsits destroys \lastkern, e.g. \footnote{3}\label{blub}\footnote{4} does it too. But why is your anchor between the footnotes and not inside?
@UlrikeFischer I see, then it is what it is. This is the anchor of the mark (for the backlink), not of the content. It immediately precedes the mark. There's only label setting and assignments in between.
Normally, only files unknown to Git are removed, but if the -x option is specified, ignored files are also removed. This can,
for example, be useful to remove all build products
@DavidCarlisle yes. thanks. some are not ignored, but I didn't test with those. but clone is one command rather than two and avoids copying files only to delete them.