From: Lars Ingebrigtsen <larsi@gnus.org>
To: Han Boetes <han@boetes.org>
Cc: 46911@debbugs.gnu.org
Subject: bug#46911: 28.0.50; woman default page to open
Date: Thu, 04 Mar 2021 21:06:06 +0100 [thread overview]
Message-ID: <87a6rivg41.fsf@gnus.org> (raw)
In-Reply-To: <7hpn0fdd32.fsf@dahud.boetes.org> (Han Boetes's message of "Thu, 04 Mar 2021 00:36:33 +0100")
Han Boetes <han@boetes.org> writes:
> whilst using m-x woman man I get this completion menu first:
>
> In this buffer, type RET to select the completion near point.
>
> Possible completions are:
> /usr/share/man/man1/man.1.gz /usr/share/man/man1/man.man-db.1.gz
> /usr/share/man/man1p/man.1p.gz /usr/share/man/man7/man.7.gz
> /usr/share/man/man7/man.man-pages.7.gz
>
> After that it took me pressing 5 additional keys to get to the man(1)
> manpage. man(1) is very good at simply choosing the first manpage in the
> path whilst using "man man" and enabling openening other manpages with
> the command "man 7 man". However great woman is, getting to the right
> manpage is clunky.
I think this is how `M-x woman' has always worked -- instead of typing
in a section and a word (as you do with `M-x man'), you use a file
browser to choose the manual.
There are advantages and disadvantages to both methods (for instance, in
`M-x man' you aren't notified that there's a page for the topic in
several sections), but the `M-x woman' method (sometimes) more choosing.
So I think everything here works as designed? Anybody got an opinion
here?
--
(domestic pets only, the antidote for overdose, milk.)
bloggy blog: http://lars.ingebrigtsen.no
next prev parent reply other threads:[~2021-03-04 20:06 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-03 23:36 bug#46911: 28.0.50; woman default page to open Han Boetes
2021-03-04 20:06 ` Lars Ingebrigtsen [this message]
2021-03-04 21:25 ` Eli Zaretskii
2021-03-04 22:05 ` Han Boetes
2021-03-05 4:48 ` Glenn Morris
2021-03-05 7:32 ` Eli Zaretskii
2021-03-05 13:33 ` Lars Ingebrigtsen
2021-03-05 14:48 ` Eli Zaretskii
2021-03-05 15:51 ` Michael Albinus
2021-03-06 9:39 ` Eli Zaretskii
2021-03-06 12:41 ` Lars Ingebrigtsen
2021-03-06 13:12 ` Eli Zaretskii
2021-03-08 19:22 ` Lars Ingebrigtsen
2021-03-11 23:42 ` Lars Ingebrigtsen
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=87a6rivg41.fsf@gnus.org \
--to=larsi@gnus.org \
--cc=46911@debbugs.gnu.org \
--cc=han@boetes.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 public inbox
https://git.savannah.gnu.org/cgit/emacs.git
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).