all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Lars Ingebrigtsen <larsi@gnus.org>
To: Morgan Smith <Morgan.J.Smith@outlook.com>
Cc: 46332@debbugs.gnu.org
Subject: bug#46332: Eshell color control characters not displayed correctly
Date: Sat, 06 Feb 2021 11:54:40 +0100	[thread overview]
Message-ID: <877dnleaa7.fsf@gnus.org> (raw)
In-Reply-To: <SN4PR0801MB36791D8552654AD43B28CD1AC5B29@SN4PR0801MB3679.namprd08.prod.outlook.com> (Morgan Smith's message of "Fri, 5 Feb 2021 12:34:36 -0500")

Morgan Smith <Morgan.J.Smith@outlook.com> writes:

> So I have my pager set to cat and in eshell I type `git log` and after a
> while (1000 - 2000 lines) it starts to show the control characters
> verbatim instead of coloring the characters. So it works initially but
> then breaks down after a bit. This applies to all commands but git log
> is a good one to use for testing.
>
> I did a quick git bisect to figure out when the problem occurred and it
> seems commit 2e2a8e5491bc6259a9ebe8c703c1c501307953e2 is the
> offender.

Thanks for bisecting this -- we've had similar reports about ANSI
colouring randomly not working, but I've been unable to reproduce the
problem here.

And I'm still not able to, and it would be nice to be able to reproduce
it before starting to poke at it.

Do you have a recipe, starting from "emacs -Q", for how to reproduce
this bug?

-- 
(domestic pets only, the antidote for overdose, milk.)
   bloggy blog: http://lars.ingebrigtsen.no





  reply	other threads:[~2021-02-06 10:54 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-02-05 17:34 bug#46332: Eshell color control characters not displayed correctly Morgan Smith
2021-02-06 10:54 ` Lars Ingebrigtsen [this message]
2021-02-09 19:31   ` Morgan Smith
2021-02-09 20:23     ` Lars Ingebrigtsen
2021-02-22 15:51       ` Lars Ingebrigtsen
2021-02-22 19:01         ` Morgan Smith
2021-02-22 19:55           ` Lars Ingebrigtsen

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=877dnleaa7.fsf@gnus.org \
    --to=larsi@gnus.org \
    --cc=46332@debbugs.gnu.org \
    --cc=Morgan.J.Smith@outlook.com \
    /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.
Code repositories for project(s) associated with this external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.