all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Werner LEMBERG <wl@gnu.org>
Cc: eliz@elta.co.il, kai.grossjohann@gmx.net, bug-gnu-emacs@gnu.org
Subject: Re: Menu: Help -> Manuals -> Read Man Page... problem
Date: Thu, 25 Mar 2004 08:06:29 +0100 (CET)	[thread overview]
Message-ID: <20040325.080629.152066039.wl@gnu.org> (raw)
In-Reply-To: <Pine.LNX.4.58.0403241131400.8168@pcl321.mppmu.mpg.de>

> As far as I can see there are the following solutions to these
> problems:
>
> (1) You, the emacs developers, convince the groff people to abandon
> the whole color escape stuff (hardly realistic).

He has tried :-)

> (2) You introduce an emacs display option to properly handle color
> escapes and use that option when viewing manpages (may be
> difficult).

This is available already!  In ansi-color.el there is a function
ansi-color-apply-on-region -- Kai has told me that he will have a look
how to integrate this function into the man stuff.  It should be
straightforward, but, as usual, we lack the manpower to do that
quickly.  Since a work-around is available, it hasn't too much a
priority I fear.


    Werner

      reply	other threads:[~2004-03-25  7:06 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-03-17  9:56 Menu: Help -> Manuals -> Read Man Page... problem Peter Breitenlohner
2004-03-17 19:01 ` Eli Zaretskii
2004-03-18  8:52   ` Peter Breitenlohner
2004-03-18 15:37     ` Reiner Steib
2004-03-18 16:04       ` Peter Breitenlohner
2004-03-18 16:26     ` Eli Zaretskii
2004-03-19 18:47       ` GROFF_NO_SGR when calling groff (was: Menu: Help -> Manuals -> Read Man Page... problem) Reiner Steib
2004-03-19 20:02         ` GROFF_NO_SGR when calling groff Werner LEMBERG
2004-03-24 11:15     ` Menu: Help -> Manuals -> Read Man Page... problem Peter Breitenlohner
2004-03-25  7:06       ` Werner LEMBERG [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=20040325.080629.152066039.wl@gnu.org \
    --to=wl@gnu.org \
    --cc=bug-gnu-emacs@gnu.org \
    --cc=eliz@elta.co.il \
    --cc=kai.grossjohann@gmx.net \
    /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.