Maja Kądziołka

Based on your "steps to reproduce", I have created the following files: `repro.rs`: ```rust use std::error::Error; use std::fs::File; use std::io::prelude::*; fn main() -> Result { { let mut file =...

Sounds great! I'd like to remark that I do use the boot disk ID provided by the BIOS. The hairest issue I can see is the fact that I like...

> Also, as far as a "safe copy" - the same initial sectors could be copied to a different cylinder, or even to the other head (of a double-sided drive),...

Because of how filesystem caching works, the file stays in RAM during the first build, and the graphics are not touched during most incremental builds. I don't think this is...

`Vec::deserialize` is not magic. You should have no trouble adapting [the implementation](https://docs.rs/serde/latest/src/serde/de/impls.rs.html#1005-1094) to insert directly into a `BitFlags` instead of going through the `Vec`. Attempting to *parse* both an integer...

In the meantime, I implemented this on my side with some JavaScript: ```html window.addEventListener('load', function() { for (const ref of document.getElementsByClassName('footnote-reference')) { const hash = ref.children[0].hash.substring(1); const refhash = 'ref:'...

Hmm, the approach of the signal handler just setting some kind of flag won't work, as in the motivating case, the signal gets delivered while the gui agent is stuck...

> Self-pipe is safe, alarm isn’t. `alarm(2)` is listed in [`signal-safety(7)`](https://man7.org/linux/man-pages/man7/signal-safety.7.html), though? > Does the agent call fork() and then do anything that isn’t async-signal-safe before execve()? If so, that...

> But you do realize we are talking about handling premature Xorg exit here, right? At this point all grants are unmapped already. So, there is no point in complicating...

I pushed a much larger diff, that should handle all this properly.