Marek

> Could you try: `# python -c "with open('/dev/yourDevice', 'wb') as p:; p.write(bytearray(1024))"` > > And if that fails, which it should, try: `# dd if=/dev/zero of=/dev/yourDevice bs=1 count=1024` >...

This happens to me with Iosevka, and I can't figure out why either.

I get it with Rust every now and then.

> I found these likely variables and set them accordingly, but to no avail: [...] I also tried setting the same variables, but I still can't get error lints for...

This is my config for `rustic` in `doom/config.el` (simplified): ```lisp (after! rustic (setq lsp-rust-all-features t lsp-rust-features "all")) ``` I based it on https://emacs-lsp.github.io/lsp-mode/page/lsp-rust-rls/#lsp-rust-all-features and https://emacs-lsp.github.io/lsp-mode/page/lsp-rust-rls/#lsp-rust-features. What I'm trying to do...

> compare it with the lsp-mode interaction That would help. Is there a way I can actually see the communication between lsp-mode and rust-analyzer?

Other folks struggle with the same issue here https://www.reddit.com/r/swaywm/comments/m8amyy/using_win_key_as_accelkey_in_firefox/.

https://github.com/ZcashFoundation/redjubjub/pull/108#issuecomment-847800004

I'm also not sure about this because even though the identifiers are longer, the dealer is not able to take in a number bigger than 255.

I assume that `i` simply goes from `1` to `n`, and that the dealer will use `id_i` to evaluate the polynomial in order to obtain the private key. Is this...