From: Dan Espen <despen@verizon.net>
To: help-gnu-emacs@gnu.org
Subject: Re: WoMan generates different result from man?
Date: Mon, 03 Jun 2013 12:56:48 -0400 [thread overview]
Message-ID: <icsj0zjfov.fsf@home.home> (raw)
In-Reply-To: mailman.931.1370272993.22516.help-gnu-emacs@gnu.org
Hongxu Chen <leftcopy.chx@gmail.com> writes:
> Jonathan Groll <lists@groll.co.za> writes:
>
>> On Mon, 03 Jun 2013 19:39:07 +0800, Hongxu Chen <leftcopy.chx@gmail.com> wrote:
>>
>>>
>>> Hi all,
>>>
>>> I am using `WoMan' other than man to read manpages. But I find there
>>> are some slight differences when reading the content. Take the
>>> manpage of `man' as an example:
>>>
>>> WoMan parses the result of the section number introduction like this:
>>>
>>> 1@Executable programs or shell commands 2@System calls
>>> (functions provided by the kernel) 3@Library calls (functions within
>>> program libraries) 4@Special files (usually found in /dev) 5@File
>>> formats and conventions eg /etc/passwd 6@Games 7@Miscellaneous
>>> (including macro packages and conventions), e.g. man(7),
>>> groff(7) 8@System administration commands (usually only for
>>> root) 9@Kernel routines [Non standard]
>>>
>>> While the result generates by `man' does have `@' but spaces ` ',
>>> just as follows:
>>> 1 Executable programs or shell commands
>>> 2 System calls (functions provided by the kernel)
>>> 3 Library calls (functions within program libraries)
>>> 4 Special files (usually found in /dev)
>>> 5 File formats and conventions eg /etc/passwd
>>> 6 Games
>>> 7 Miscellaneous (including macro packages and conventions), e.g. man(7),
>>> groff(7)
>>> 8 System administration commands (usually only for root)
>>> 9 Kernel routines [Non standard]
>>>
>>> The margin in WoMan also seems a little odd.
>>>
>>> So is this a known issue?
>>
>> Yes. Women are from venus.
> Well, WoMan is really different from man...
> Are there some workarounds to remedy?
>
> BTW, is WoMan popular in Emacs, or Emacsers typically look up info
> through info?
I have no way of telling, but stopped using woman and use M-x man instead.
If the man page doesn't help and it mentions info, I'll try info.
--
Dan Espen
next prev parent reply other threads:[~2013-06-03 16:56 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-03 11:39 WoMan generates different result from man? Hongxu Chen
2013-06-03 12:57 ` Jonathan Groll
2013-06-03 15:20 ` Hongxu Chen
2013-06-03 17:28 ` Stefan Monnier
[not found] ` <mailman.931.1370272993.22516.help-gnu-emacs@gnu.org>
2013-06-03 16:56 ` Dan Espen [this message]
2013-06-03 18:15 ` Emanuel Berg
2013-06-04 0:53 ` Hongxu Chen
[not found] ` <mailman.964.1370307204.22516.help-gnu-emacs@gnu.org>
2013-06-04 1:57 ` Emanuel Berg
2013-06-04 3:31 ` Hongxu Chen
[not found] ` <mailman.969.1370316681.22516.help-gnu-emacs@gnu.org>
2013-06-04 17:08 ` Emanuel Berg
2013-06-06 8:31 ` Hongxu Chen
[not found] ` <mailman.1074.1370507531.22516.help-gnu-emacs@gnu.org>
2013-06-06 9:43 ` Emanuel Berg
2013-06-07 1:11 ` Hongxu Chen
2013-06-03 17:18 ` Glenn Morris
2013-06-03 17:50 ` Eli Zaretskii
2013-06-03 19:34 ` Glenn Morris
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=icsj0zjfov.fsf@home.home \
--to=despen@verizon.net \
--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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).