all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Morgan Smith <Morgan.J.Smith@outlook.com>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: Utkarsh Singh <utkarsh190601@gmail.com>, 45380@debbugs.gnu.org
Subject: bug#45380: 28.0.50; Error in coloured output in Emacs 28.05(AUR package: emacs-git)
Date: Sun, 24 Oct 2021 20:55:14 -0400	[thread overview]
Message-ID: <BYAPR05MB402397C1BC7E18388552774EC5839@BYAPR05MB4023.namprd05.prod.outlook.com> (raw)
In-Reply-To: <87lf2i0w0l.fsf@gnus.org>

Ya I sent a bug report (46332) about this exact same thing happening. 
And then you fixed it so that it happened much less often. I didn't 
notice until like a day after we closed that issue. My guess is that 
there are two unrelated bugs that exhibit the exact same behavior and 
you already fixed one.

I'm using emacs master (commit 2415743) btw.

On 10/24/21 8:48 PM, Lars Ingebrigtsen wrote:
> Morgan Smith <morgan.j.smith@outlook.com> writes:
> 
>> How to reproduce: Just keep trying some long running colored commands
>> in eshell like "git log --color". Eventually the logic will get messed
>> up and it'll look like the previously posted screenshot.
> 
> What Emacs version are you using?  I thought this was fixed some months
> ago.
> 





  reply	other threads:[~2021-10-25  0:55 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-12-23  4:09 bug#45380: 28.0.50; Error in coloured output in Emacs 28.05(AUR package: emacs-git) Utkarsh Singh
2020-12-23 15:39 ` Eli Zaretskii
2021-01-23 23:09 ` Lars Ingebrigtsen
     [not found]   ` <877do2n3ux.fsf@gmail.com>
2021-01-25 23:45     ` Lars Ingebrigtsen
2021-10-25  0:44       ` Morgan Smith
2021-10-25  0:48         ` Lars Ingebrigtsen
2021-10-25  0:55           ` Morgan Smith [this message]
2021-10-25 12:27             ` miha--- via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-10-25 13:25               ` 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=BYAPR05MB402397C1BC7E18388552774EC5839@BYAPR05MB4023.namprd05.prod.outlook.com \
    --to=morgan.j.smith@outlook.com \
    --cc=45380@debbugs.gnu.org \
    --cc=larsi@gnus.org \
    --cc=utkarsh190601@gmail.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.