From: "Stefan Monnier" <monnier+gnu/emacs@rum.cs.yale.edu>
Cc: rms@gnu.org, Ted.Harding@nessie.mcc.ac.uk, emacs-devel@gnu.org
Subject: Re: [lurwas@moya.dnsalias.net: groff version 1.18.1 and emacs]
Date: Wed, 04 Dec 2002 15:20:32 -0500 [thread overview]
Message-ID: <200212042020.gB4KKWu25400@rum.cs.yale.edu> (raw)
In-Reply-To: 20021204.135516.82043726.wl@gnu.org
>
> > groff version 1.18.1 gives wrongly formatted man-pages, thus not
> > letting emacs display escape sequences correctly. With earlier groff
> > versions, it works. Setting '(Man-fontify-manpage-flag nil) in my
> > .emacs file is a way around this problem, but it's kind of ugly.
>
> IIRC, this has already been answered on the emacs-devel list.
>
> The easiest way currently is to use `setenv' and set the environment
> variable GROFF_NO_SGR to 1 (within Emacs) in case the man program
> hasn't been configured already to not use SGR. The proper way is to
> make Emacs understand SGR escape sequences.
Why does nroff use SGR when outputting to Emacs ?
Does Emacs pass a TERM var that indicates that SGR codes are supported ?
If so, Emacs should be fixed, otherwise groff should be fixed.
Stefan
next prev parent reply other threads:[~2002-12-04 20:20 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <E18JXMq-0003vX-00@fencepost.gnu.org>
2002-12-04 12:55 ` [lurwas@moya.dnsalias.net: groff version 1.18.1 and emacs] Werner LEMBERG
2002-12-04 20:20 ` Stefan Monnier [this message]
2002-12-05 9:47 ` Werner LEMBERG
2002-12-06 13:32 ` Richard Stallman
2002-12-06 22:19 ` Werner LEMBERG
2002-12-06 22:55 ` Stefan Monnier
2002-12-07 15:58 ` Werner LEMBERG
2002-12-07 16:35 ` Alex Schroeder
2002-12-09 16:12 ` Stefan Monnier
[not found] ` <E18LCzH-0004Jz-00@fencepost.gnu.org>
2002-12-09 7:17 ` Werner LEMBERG
2002-12-09 19:16 ` Eli Zaretskii
2002-12-10 20:57 ` Werner LEMBERG
2002-12-06 13:31 ` Richard Stallman
2002-12-06 22:26 ` Werner LEMBERG
2002-12-07 0:13 ` Alan Shutko
2002-12-07 18:59 ` Eli Zaretskii
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=200212042020.gB4KKWu25400@rum.cs.yale.edu \
--to=monnier+gnu/emacs@rum.cs.yale.edu \
--cc=Ted.Harding@nessie.mcc.ac.uk \
--cc=emacs-devel@gnu.org \
--cc=rms@gnu.org \
/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.