msrd0

When I copy your input into a new crate and run `cargo doc2readme`, I get this output ``` | Header1 | Header2 | | --- | --- | | A...

Works for me with and without this option

I don't think there's much I can do here. Your output makes me think that pulldown-cmark didn't recognize your input as a table, so without more details, I have to...

I was also testing with the latest release. If you provide further details I'm happy to reopen the issue.

Oh I see, there's some problem with the indentation. **Workaround**: Put an extra space at the beginning of the line, like so ```rust #![doc = concat!(" blahblah = \"", env!("CARGO_PKG_VERSION"),...

Well, maybe the derive macro is unneccessarily strict then, as `T: Default` is required in the current version: https://docs.rs/bollard/0.8.0/bollard/exec/struct.CreateExecOptions.html#impl-Default It's not a big deal, just a minor inconvenience, so if...

@dmgolembiowski I'm using this code as a workaround: ```rust fn offset(&self, at: proc_macro2::LineColumn) -> usize { let line_offset: usize = self .code .split('\n') .take(at.line - 1) .map(|line| line.chars().count() + 1)...

@zesterer There exists a way to use this crate by calculating the offset from the line and column information from proc-macro. I'd still prefer a way to just pass the...

Line wrapping by default for some languages like LaTeX would be extremely helpful. I find it quite annoying to do manual linebreaks for natural language paragraphs, where I want all...

Well, the sharp is comming from `{{readme}}` section of my template. It's probably because lines starting with a sharp and followed by a whitespace are supposed to be ignored in...