From: Peter Breitenlohner <peb@mppmu.mpg.de>
Cc: bug-gnu-emacs@gnu.org
Subject: Re: Menu: Help -> Manuals -> Read Man Page... problem
Date: Thu, 18 Mar 2004 09:52:31 +0100 (CET) [thread overview]
Message-ID: <Pine.LNX.4.58.0403180936040.3919@pcl321.mppmu.mpg.de> (raw)
In-Reply-To: <7704-Wed17Mar2004210116+0200-eliz@elta.co.il>
On Wed, 17 Mar 2004, Eli Zaretskii wrote:
> Thanks for the report.
Hi Eli,
thanks for your quick response.
> IIRC, Emacs 21.3 was released before Groff 1.18, so you cannot expect
> it to support this feature.
That's not entirely true. Groff-1.18.tar.gz from the ftp server is dated
"08 Oct 2002" and we use that version since 27 Nov 2002. On the other hand
emacs-21.3.tar.gz from the ftp server is dated "19 Mar 2003". But I agree
that there probably wasn't much time to detect the problem.
> Current Emacs development sources already set GROFF_NO_SGR=1 when they
> run `man'.
Good to know (in particular since man is somewhat disfavoured by FSF).
Is this built into the emacs binary or just in the one place I found:
line 61 of emacs-21.3/lisp/gnus/gnus-uu.el?
And would it suffice to modify that file
'"groff -mandoc -Tascii %s' => '"GROFF_NO_SGR=1 groff -mandoc -Tascii %s'
(and of course recompile gnus-uu.elc)?
I certainly want to fix this little problem before we get emacs-21.4
regards
Peter Breitenlohner <peb@mppmu.mpg.de>
next prev parent reply other threads:[~2004-03-18 8:52 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 [this message]
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
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=Pine.LNX.4.58.0403180936040.3919@pcl321.mppmu.mpg.de \
--to=peb@mppmu.mpg.de \
--cc=bug-gnu-emacs@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.