From: Eli Zaretskii <eliz@gnu.org>
To: xahlee@gmail.com
Cc: erich@cozi.com, rms@gnu.org, emacs-devel@gnu.org,
monnier@iro.umontreal.ca, drew.adams@oracle.com,
eric.hanchrow@gmail.com
Subject: Re: [PATCH] (woman-always-choose-first-hit): New defcustom.
Date: Sun, 15 Mar 2009 00:19:16 +0200 [thread overview]
Message-ID: <uvdqbrbmj.fsf@gnu.org> (raw)
In-Reply-To: <001636458d880a725704651acee6@google.com>
> Date: Sat, 14 Mar 2009 21:21:47 +0000
> From: xahlee@gmail.com
>
> Eli Zaretskii wrote:
> > • The problems you mention are a far cry from making WoMan ``unusable''.
>
> “unusable” is probably a exaggeration. I'm trying to express how it is
> unusable to most users who are not emacs enthusiasts.
IMO, it is no less usable than `man', to newbies and veterans alike.
> consider emacs as a tool, and likewise man and woman are tools. People want
> to run man/woman mostly to get the job done, namely, reading unix man page
> in emacs. “man” works. However, woman is a improvement, but isn't default.
`woman' is not meant to be an improvement. From the commentary at the
beginning of woman.el:
;; WoMan implements a subset of the formatting performed by the Emacs
;; `man' (or `manual-entry') command to format a UN*X manual `page'
;; for display, but without calling any external programs.
IOW, it's a clone of `man' that does not require `man' the external
command. That's all there is to it. On some platforms, that's a heck
of an advantage; on others, it isn't.
> The extra option of minor improvement to user adds a slight complexity. But
> adding the fact that woman itself provides some rough edges. So for some
> emacs user who are beginning to be adventurous, when they read about woman
> and try it, its problem is frustrating, another tiny time drain in emacs.
`woman' works, period. So does `man', of course. Each one has its
quirks and bugs (I fixed one in each just the other day), but they are
minor bugs. I use both, on 3 radically different platforms, and I
don't find any of them ``frustrating'', nor do they need my Emacs
expertise to show me a manual page in a reasonably legible way.
> I think most, or all of these can be fixed, without sacrificing ANY of
> emacs's power.
Agreed.
next prev parent reply other threads:[~2009-03-14 22:19 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-10 0:12 [PATCH] (woman-always-choose-first-hit): New defcustom Eric Hanchrow
2009-03-10 18:20 ` Richard M Stallman
2009-03-11 1:32 ` Stefan Monnier
2009-03-11 16:57 ` Richard M Stallman
2009-03-11 17:03 ` Drew Adams
2009-03-11 23:08 ` xahlee
2009-03-12 4:13 ` Eli Zaretskii
2009-03-14 21:21 ` xahlee
2009-03-14 22:19 ` Eli Zaretskii [this message]
2009-03-15 14:08 ` tomas
2009-03-16 9:42 ` Richard M Stallman
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=uvdqbrbmj.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=drew.adams@oracle.com \
--cc=emacs-devel@gnu.org \
--cc=eric.hanchrow@gmail.com \
--cc=erich@cozi.com \
--cc=monnier@iro.umontreal.ca \
--cc=rms@gnu.org \
--cc=xahlee@gmail.com \
/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.