all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: chohag@jtan.com
Cc: 69598-done@debbugs.gnu.org
Subject: bug#69598: 29.2; colour support based on $TERM value not terminfo database
Date: Thu, 21 Mar 2024 10:33:17 +0200	[thread overview]
Message-ID: <86h6h02dde.fsf@gnu.org> (raw)
In-Reply-To: <868r2rzxd0.fsf@gnu.org> (message from Eli Zaretskii on Sat, 09 Mar 2024 09:18:51 +0200)

> Cc: 69598@debbugs.gnu.org
> Date: Sat, 09 Mar 2024 09:18:51 +0200
> From: Eli Zaretskii <eliz@gnu.org>
> 
> > From: chohag@jtan.com
> > cc: chohag@jtan.com, 69598@debbugs.gnu.org
> > Comments: In-reply-to Eli Zaretskii <eliz@gnu.org>
> >    message dated "Fri, 08 Mar 2024 21:50:01 +0200."
> > Date: Fri, 08 Mar 2024 21:13:27 +0000
> > 
> > I should be clear that I'm not trying to get something fixed --- I
> > don't have a problem here. I can get along just fine but in my
> > travels I discovered that emacs did not work as I expected and, on
> > investigation, as it described itself and so I thought that GNU
> > would like know that their flagship product and/or its documentation
> > was deficient.
> > 
> > I have provided more information at your request which I hope you
> > find useful but I have no need or desire to pursue this matter.
> 
> Thank you for your inputs.  You may wish reading the file
> lisp/term/README, which attempts to explain this and other related
> stuff.  Sorry I didn't remember we had this file and didn't point you
> to it in the first place.

No further comments within 2 weeks, so I'm now closing this bug.





      reply	other threads:[~2024-03-21  8:33 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-03-06 23:01 bug#69598: 29.2; colour support based on $TERM value not terminfo database chohag--- via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-03-07  6:47 ` Eli Zaretskii
2024-03-07 17:32   ` chohag--- via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-03-07 17:47     ` Eli Zaretskii
2024-03-07 18:31       ` chohag--- via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-03-07 19:26         ` Eli Zaretskii
2024-03-07 19:59           ` chohag--- via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-03-07 20:10             ` Eli Zaretskii
2024-03-07 21:45               ` chohag--- via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-03-07 21:50                 ` chohag--- via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-03-08  7:11                 ` Eli Zaretskii
2024-03-08 11:36                   ` chohag--- via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-03-08 12:22                     ` Eli Zaretskii
2024-03-08 14:23                       ` chohag--- via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-03-08 15:09                         ` Eli Zaretskii
2024-03-08 18:52                           ` chohag--- via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-03-08 19:50                             ` Eli Zaretskii
2024-03-08 21:13                               ` chohag--- via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-03-09  7:18                                 ` Eli Zaretskii
2024-03-21  8:33                                   ` Eli Zaretskii [this message]

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=86h6h02dde.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=69598-done@debbugs.gnu.org \
    --cc=chohag@jtan.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.