Re: On raw strings in commit field

2022-01-01 Thread Liliana Marie Prikler
> Where is the Cantor-style diagonalization argument that you spoke of? You skipped over it, read again. The key point is that you're referencing the thing you think will be invalidated to create your scheme.

Re: Updating old blog posts?

2022-01-01 Thread Hartmut Goebel
Am 31.12.21 um 12:14 schrieb Liliana Marie Prikler: have a small notification directing them to a new blog post or the cookbook +1 -- Regards Hartmut Goebel | Hartmut Goebel | h.goe...@crazy-compilers.com | | www.crazy-compilers.com | compilers which you thought are

Re: On raw strings in commit field

2022-01-01 Thread Liliana Marie Prikler
Am Freitag, dem 31.12.2021 um 20:41 -0500 schrieb Mark H Weaver: > I disagree with the last line above.  What makes you think that I'm > presupposing that the tag does change? > > There's a difference between "presupposing that the tag does change" > and "not assuming that the tag will not

Re: On raw strings in commit field

2022-01-01 Thread Liliana Marie Prikler
Am Samstag, dem 01.01.2022 um 15:37 -0500 schrieb Mark H Weaver: > Liliana Marie Prikler writes: > > > > Where is the Cantor-style diagonalization argument that you spoke > > > of? > > You skipped over it, read again.  The key point is that you're > > referencing the thing you think will be

Re: EXWM

2022-01-01 Thread calcium
I was totally at lost when I started my emacs/exwm session and tried to `find-file' only to be redirected to an 'ido-find-file` with whom I don't know how to navigate. In the moment, it felt very intrusive for me and I was very afraid to be unable to control my emacs because I have set all my

Re: On raw strings in commit field

2022-01-01 Thread Bengt Richter
[0] https://cdn.quotesgram.com/img/31/40/532049644-676813c5150a0168ad089c40202f742e.jpg On +2022-01-01 12:12:33 +0100, Liliana Marie Prikler wrote: > Am Freitag, dem 31.12.2021 um 20:41 -0500 schrieb Mark H Weaver: > > I disagree with the last line above.  What makes you think that I'm > >

Re: On raw strings in commit field

2022-01-01 Thread Liliana Marie Prikler
Hi Timothy, Am Samstag, dem 01.01.2022 um 12:45 -0500 schrieb Timothy Sample: > If you want a concrete example to think through, there’s ‘eclib’.  > Our package says it’s version “20190909”, but that’s not what > upstream calls version “20190909”.  It looks like when we packaged > ‘eclib’, that

Re: On raw strings in commit field

2022-01-01 Thread Mark H Weaver
Liliana Marie Prikler writes: >> Where is the Cantor-style diagonalization argument that you spoke of? > You skipped over it, read again. The key point is that you're > referencing the thing you think will be invalidated to create your > scheme. I've carefully read your message at least 4

Re: On raw strings in commit field

2022-01-01 Thread Liliana Marie Prikler
Hi, Am Samstag, dem 01.01.2022 um 15:19 -0500 schrieb Mark H Weaver: > Hi Liliana, > > Liliana Marie Prikler writes: > > > Am Freitag, dem 31.12.2021 um 20:41 -0500 schrieb Mark H Weaver: > > > I disagree with the last line above.  What makes you think that > > > I'm presupposing that the tag

Re: On raw strings in commit field

2022-01-01 Thread Mark H Weaver
Hi Liliana, Liliana Marie Prikler writes: > Am Freitag, dem 31.12.2021 um 20:41 -0500 schrieb Mark H Weaver: >> I disagree with the last line above.  What makes you think that I'm >> presupposing that the tag does change? >> >> There's a difference between "presupposing that the tag does

Re: Updating old blog posts?

2022-01-01 Thread Leo Famulari
On Fri, Dec 31, 2021 at 12:14:10PM +0100, Liliana Marie Prikler wrote: > Given that time machine ownership is significantly higher among Guix > users than ordinary citizens, I think we should only update that blog > post to have a small notification directing them to a new blog post or > the

Re: On raw strings in commit field

2022-01-01 Thread Timothy Sample
Hi all, Liliana Marie Prikler writes: > Am Freitag, dem 31.12.2021 um 20:41 -0500 schrieb Mark H Weaver: > >> If upstream later indicates that version "1.2.3" is now commit YYZ, I >> don't think that invalidates our basis for continuing to associate >> version "1.2.3" with commit XYZ.  The