all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Patrick Poitras <patrick.f.poitras@gmail.com>
To: Jim Porter <jporterbugs@gmail.com>
Cc: 68724-done@debbugs.gnu.org
Subject: bug#68724: eshell/make doesn't properly handle color term characters
Date: Thu, 25 Jan 2024 17:31:07 -0800	[thread overview]
Message-ID: <CACpx+d4pZ1YTgHi7wRN9odfazSMRK-XZ1Lgj85GtP6WgAEwP-A@mail.gmail.com> (raw)
In-Reply-To: <a80319fa-e354-1861-5157-eb6a82f5af83@gmail.com>

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

This is what happens when I file bug reports while sick. Forgot a bunch of
details. My apologies.

Yeah, bug reported from emacs 30.0.50 @ 4e260bfc47e on master. Can confirm
that it's now fix on latest master.

Thanks!

On Thu, Jan 25, 2024 at 5:18 PM Jim Porter <jporterbugs@gmail.com> wrote:

> On 1/25/2024 4:54 PM, Patrick Poitras wrote:
> > In eshell, if I am in a directory and call `make`, the call that is
> > executed is (eshell/make) from em-unix.el.
> >
> > The *compilation* window then pops up, which reads: ...
>
> Thanks for the bug report. I'm guessing you're using Emacs 30.0.50. This
> is a bug, in that eshell/make should print its output to the Eshell
> buffer by default (not a new compilation buffer). That's now fixed in
> 4834be0949e on master, so closing this issue.
>
> However, for fixing the colors in the compilation buffer, you can also
> add 'ansi-color-compilation-filter' to 'compilation-filter-hook'.
>

[-- Attachment #2: Type: text/html, Size: 1378 bytes --]

  reply	other threads:[~2024-01-26  1:31 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-26  0:54 bug#68724: eshell/make doesn't properly handle color term characters Patrick Poitras
2024-01-26  1:18 ` Jim Porter
2024-01-26  1:31   ` Patrick Poitras [this message]
2024-01-26  1:59     ` Jim Porter

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=CACpx+d4pZ1YTgHi7wRN9odfazSMRK-XZ1Lgj85GtP6WgAEwP-A@mail.gmail.com \
    --to=patrick.f.poitras@gmail.com \
    --cc=68724-done@debbugs.gnu.org \
    --cc=jporterbugs@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.