Michael

block-joining a variable with a list as the name results in an unsplittable ring

1

I'm doing some weird macro things and encountered this, I think it's not stringifying the variable name until it's evaluated or displayed. ### Constructing the variable in the normal way...

crash when switching visualizer to album art

1

- add visualizer.lua to the mpv scripts - set `mode` to `novideo` or `force` - play a audio track - switch to the album art - Segmentation fault (core dumped)...

the pathological multiplier is defined as ``` max(w, h) / min(w, h) × w × h ``` substituting for all possible orderings of `w` and `h`: - `w < h`:...

Would be nice to be able to add things to a chunk's env after loading it (in my case the `AsChunk` implementation adds its own things to the env, and...

```rs use kdl::{KdlDocument, KdlEntry, KdlNode, KdlValue}; use std::str::FromStr; fn main() { let mut node = KdlNode::new("what"); node.entries_mut().push(KdlEntry::new(KdlValue::RawString( "\"#\nkdl-injection \"no way!!\"//".into(), ))); let mut doc = KdlDocument::new(); doc.nodes_mut().push(node); println!("{doc}"); println!( "{}...

Inline latex gets triggered by $ ... $ , causing a lot of unintentional latex

1

### Expected behaviour content surrounded by $'s probably should be rendered normally ### Actual behaviour it gets rendered as inline latex, which removes the $'s and spaces, making it hard...

if there is zero or one session file then the default target index of `1` (not `0`) will cause the `targets` list to be indexed out-of-bounds, causing a panic

false positive "variable does not need to be mutable" report when mutating a variable with a pattern in a closure

1

**rust-analyzer version**: `rust-analyzer version: 1.83.0-nightly (fa724e5 2024-09-27)` (also occurs with the vscode bundled rust-analyzer) **rustc version**: `rustc 1.83.0-nightly (fa724e5d8 2024-09-27)` **editor or extension**: VSCode (rust-analyzer `v0.3.2121`) **relevant settings**: `"rust-analyzer.diagnostics.experimental.enable": true`...

Feature Request: downcasting `Log`, but for real

2

Seems #399 was already closed (4.5 years ago, for bad usecase & maybe backwards compatibility reasons?), but I have an actual use! My logger writes a message on panic, but...