Andy Russell

Yep, we're limited by pulldown-cmark here. For vim-markdown-composer you could try using an external renderer that does have support, though: https://github.com/euclio/vim-markdown-composer/blob/5b79f425ebd28216d9aa472be3ba07cda41d9b24/doc/markdown-composer.txt#L31

https://github.com/markdown-it/markdown-it/issues/62#issuecomment-76346499

Looks like stringifying the expression is [the approach that structopt uses](https://github.com/TeXitoi/structopt/blob/master/examples/enum_in_args.rs#L20).

Probably a bug introduced by match default bindings. You can work around this by upgrading to the latest stable with [rustup](https://rustup.rs/).

rebased.

According to https://github.com/fmtlib/fmt/issues/2811, the `std::tm` formatter intentionally no longer supports system-defined specifiers like `%-I`.

Hmm. I'll get a VM going later and see if I can debug (running Arch Linux atm). Are you using a window manager with EWMH enabled?

Yep, I managed to track it down to [this line](https://github.com/gtk-rs/gir/blob/c148542ce89b0bf7cbb9f5ef4179c96a45d022df/src/analysis/rust_type.rs#L382). Not sure if it's safe to remove completely or if it needs to be smarter, though.

Sorry, let me clarify. To use your example of a 160x120 pixel buffer, I would like the ability to force the scale of the buffer display to 1x or 2x,...

I'll probably have a pull request going for this by the weekend. As a first step it'll only support checking which files are different than the ones posted already, but...