From: Lennart Borgman <lennart.borgman.073@student.lu.se>
Cc: help-gnu-emacs@gnu.org, Emacs Devel <emacs-devel@gnu.org>
Subject: Re: Read man page in Emacs - woman bug?
Date: Wed, 03 Aug 2005 00:30:03 +0200 [thread overview]
Message-ID: <42EFF3EB.1050109@student.lu.se> (raw)
In-Reply-To: <uvf2o2hsh.fsf@gnu.org>
Eli Zaretskii wrote:
>>Date: Tue, 02 Aug 2005 11:32:42 +0200
>>From: Lennart Borgman <lennart.borgman.073@student.lu.se>
>>Cc: help-gnu-emacs@gnu.org
>>
>>"M-x woman" can work on MS Windows too with GnuWin32 utilities. You then
>>have to add the GnuWin23 man path to `woman-manpath'.
>>
>>
>
>Did you try that? GnuWin23 distros have an unfortunate habit to
>distribute man pages as foo.1.txt files, and I'm not sure WoMan will
>grok such names. GnuWin23 also removes all traces of overstriking and
>underlining from the formatted man pages, so the result displayed by
>WoMan might lack fontification.
>
>One could use unformatted man pages instead, of course, if they are
>installed...
>
Well, I tried woman-find-file and read about woman-manpath but did not
actually try that. I did now however and it seems to work. (Though I am
running the CVS version of Emacs.) To me even those *.txt files looks
like they are fontified ok, but I am not sure. I am not used to man and
do not know much about it.
Links seems to work, but I did find a bug I believe. If you open
man5/texinfo.5 and click the link "tex (1)" emacs seems to loop.
next prev parent reply other threads:[~2005-08-02 22:30 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <877jf5myk5.fsf@narke.yellow.line>
[not found] ` <87fytsybzf.fsf@tiger.rapttech.com.au>
2005-08-02 9:32 ` Read man page in Emacs Lennart Borgman
2005-08-02 20:41 ` Eli Zaretskii
2005-08-02 22:30 ` Lennart Borgman [this message]
2005-08-03 9:00 ` Steven Woody
2005-08-04 8:18 ` Tim X
2005-08-04 10:28 ` Steven Woody
2005-08-04 11:18 ` David Kastrup
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=42EFF3EB.1050109@student.lu.se \
--to=lennart.borgman.073@student.lu.se \
--cc=emacs-devel@gnu.org \
--cc=help-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.