J’ai de la peine à imaginer une situation où quelqu’un a vraiment besoin de manger de la viande plus qu’une fois par jour, donc ça devrait être au moins 2 repas sur 3 plutôt que 1 sur 4.

Mais bon, c’est quand même ça de pris.

IME, Android devices go the extra mile to not support SD cards formatted on another device (or with another OS). So maybe that’s what you’re seeing. The reason is probably some bogus “for your own security” crap.

If you find a solution, please let us know. I’m suffering from the same problem with my 2017 X1 Carbon

I don’t think it’s a question of willingness to understand, but one of disagreement about the seriousness of the problem. Not to mention the implict idea that a “verified boot” is the only way to get that result. E.g. it’s very easy to get to a “safe factory state” without that kind of locking, for example with an immutable boot loader, as is typically present in many ARM SoCs (Allwinner, Rockchip, …). In that case you can revert to a safe state by downloading a known good OS image (using a trusted machine) and installing that image using only the immutable bootloader.

So AFAICT, in practice a locked bootloader makes no difference to the most common attacks I’ve seen on my devices and that of friends&family. Seems like a far cry from your original claim that “This means that the most essential feature for your safety, the metaphorical lock on the front door of your house, is left broken and loose.”

But my point is that a remote attacker using privilege escalation can already do all of that even with a locked bootloader. “rootkits” don’t need an unlocked bootloader.

Sorry, but that page does not seem to say what you wrote. E.g. I can’t see how a remote attacker (such as a malign webpage, email, application, …) could take advantage of an unlocked bootloader without being able to see (and modify) all the data on your phone. IOW I think what you write applies only to an attacker who has physically taken your phone (temporarily).

Your links are all broken (because of “…” elision)

Can someone point me at technical info about the risks of having an unlocked bootloader? From where I stand, the risks seem completely irrelevant (to take advantage of an unlocked bootloader, the attacker would need to have full access to your OS already). AFAIK, locking of bootloaders was never designed to protect the user, but only to let cell-phone providers restrict what phone users can do.

#OffByOne

Ouais, et en plus tout semble indiquer que le PQ va venir au pouvoir (bien logiquement) juste après la CAQ. Malheureusement, tout indique aussi qu’ils ne vont rien nettoyer.

I don’t know of any mirrors that are “official”, but I do know some people maintain mirrors via rsync (rsync service on elpa.gnu.org was added specifically in response to such requests, IIRC to maintain a mirror on the other side of China’s firewall). As for validation, (Non)GNU ELPA signs all the packages and the archive-contents file (with a key distributed alongside Emacs), so it should “just work”.

The question is: are they going to do something about it?

Encore des mesures anti-musulmans. Avec le PQ et leurs pubs anti-immigrants, c’est une course au racisme à vomir!

Time to reindent lines is something that tends to increase, as indentation quality is improved over the years (and as the need increases to support ever more syntactic features of the indented language).
But it really depends more on the text being indented and the mode in use than on the version of Emacs, IME.

A possible option is to stick to Debian 13, but use a hand-built kernel, since Debian 13 still includes the i386 port. Of course, it also depends on your exact CPU and other hardware as well as what you want to run in it.

Ce serait pas caritatif, ce serait du simple gros bon sens, vu que c’est moins cher.

You make it sound like optical mouses were a no-brainer, but they were very much non trivial: it required both ingenuity and fairly sophisticated tech to make them work well.

[ The problem I have which which-key is that it applies only after a prefix. ]
Mutating a keymap with setc[ad]r is evil! Since you bind that map to a prefix, why not use (menu-item "dummy" KEYMAP :filter FUNCTION) instead?
[ The problem with this trick is that it can be used only after a prefix. 🙃 ]

Donner-leur un logement, ça coûte moins cher!