Github messages for voidlinux
 help / color / mirror / Atom feed
From: borjator <borjator@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [ISSUE] glow stopped displaying colors properly with a pager
Date: Fri, 21 Jan 2022 22:56:50 +0100	[thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-35168@inbox.vuxu.org> (raw)

[-- Attachment #1: Type: text/plain, Size: 1363 bytes --]

New issue by borjator on void-packages repository

https://github.com/void-linux/void-packages/issues/35168

Description:
<!-- Don't request update of package. We have a script for that. https://alpha.de.repo.voidlinux.org/void-updates/void-updates.txt . However, a quality pull request may help. -->
### System

* xuname:  
  *Void 5.15.9_1 x86_64 GenuineIntel uptodate rFFFFF*
* package:  
  *glow-1.4.1_1*

### Expected behavior

`glow -p` displays formatted Markdown with colors in my pager (less)

### Actual behavior

It shows a lot of color codes without interpreting them:
`ESC[38;5;228;48;5;63;1mESC[0mESC[38;5;228;48;5;63;1mESC[0m  ESC[38;5;228;48;5;63;1m ESC[0mESC[38;5;228;48;5;63;1mHelloESC[0mESC[38;5;228;48;5;63;1m ESC[0mESC[38;5;252mESC[38;5;252m`

### Steps to reproduce the behavior

1. Create a simple Markdown file: `echo "# Hello" > hello.md`
2. Display it with glow with a pager: `glow -p hello.md`

I'm not completely sure if this is a glow bug since I've tried a bunch of different things:

- The previous version of _glow_
- Older versions of _less_ (my favourite pager)
- I can confirm the same happens with _most_ my second favourite pager
- I've tried to use a different terminal (_xterm_ instead of _xst_)
- I tested using a different `TERM` environment variable just in case

Anything else I could try?

             reply	other threads:[~2022-01-21 21:56 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-21 21:56 borjator [this message]
2022-01-22  8:10 ` demostanis
2022-01-22 21:29 ` [ISSUE] [CLOSED] " borjator
2022-01-22 21:29 ` borjator

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-35168@inbox.vuxu.org \
    --to=borjator@users.noreply.github.com \
    --cc=ml@inbox.vuxu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).