Mark Woods

@mhinz I've reworked these commits after I found some time to RTFM :-) I think this PR is in a good state now, if you'd like to take a look....

@mhinz This has now been simplified to just use Vim's built in `getcompletion()` function for file completions.

Cool, thanks for confirming I was not going mad :-) I've added a PR https://github.com/charmbracelet/glamour/pull/162 with a small change for this.

FWIW, expand space has also stopped working for me. The output from :DelimitMateTest does show expand space not working though. ```delimitMate Report ================== * Options: ( ) default, (g) global,...

@Raimondi thanks, and apologies for the false alarm :-) Having removed the `` mapping from my vimrc, expand space is working as expected... ```delimitMate Report ================== * Options: ( )...

@PLBMR @mislav I've just looked at this too as I've run into a similar issue, I have markdown files set to hard-wrap 80 in vim by default (the wisdom of...

@PLBMR There is already a `TerminalWidth()` function in `pkg/iostreams/iostreams.go`, but I'm not sure something that simple would be appropriate for rendering markdown which has not already been hard-wrapped. For example,...

FWIW, this seems to be the code in [glow](https://github.com/charmbracelet/glow) that sets the default width for rendering... ``` // Detect terminal width if isTerminal && width == 0 && !cmd.Flags().Changed("width") {...

This change works around the issue, but I needed to set the word wrap width to 145 to allow for block quoted text... ```diff diff --git a/pkg/markdown/markdown.go b/pkg/markdown/markdown.go index 32313a15..6baa9c70...

Sorry, that change breaks formatting of `gh reference` command as it appends to the opts and therefore overwrites the width provided by `markdown.Render(cmd.Long, markdown.WithIO(io), markdown.WithWrap(wrapWidth))`, but I think it's on...