Mark Woods
Mark Woods
But, this works... ```diff diff --git a/pkg/markdown/markdown.go b/pkg/markdown/markdown.go index 32313a15..f7eeab87 100644 --- a/pkg/markdown/markdown.go +++ b/pkg/markdown/markdown.go @@ -52,6 +52,9 @@ func Render(text string, opts ...glamour.TermRendererOption) (string, error) { // we need...
@mislav Yes, it is possible to check the terminal width and take that into account when setting the wrap limit. I've added a (very hacky) commit that does that, but...
btw, most of that code is copied from Glow, see https://github.com/charmbracelet/glow/blob/e0789536674a25eeced8a12bd2fa17a1b6ef01a1/main.go#L156-L173 I think ideally it would use `TerminalWidth()` from the `iostreams` package in gh-cli, but I struggled to get that...
FYI test failures are due to string equality assertions on output that was previously wrapped at 80, now 120. This can easily be fixed by just updating the assertions, but...
@samcoe While that will fix the rendering issues associated hard-wrapping (for people with terminal cols wide enough, presumably most people), and would be a welcome change, for many people it...
Oh, actually, maybe a better idea would be to make the wrap width a function of `io`, so you could call `WithWrap(io.WrapWidth())`, and then have `io.WrapWidth()` return terminal width or...
@samcoe makes sense, and solves both problems 👍
FWIW, I also find this very confusing. When I commit, I normally use the `--verbose` option so I see the changes I am committing while writing the commit message. The...
FYI, had a look at the plugin code to see how easy it would be to show the full diff when amending commits... It should be simple to extract the...
This works for me... ```vim " Disable bg and fg color highlighting of bad spelling in PaperColor autocmd VimEnter,ColorScheme * \ if get(g:, 'colors_name', v:null) ==# 'PaperColor' | \ hi...