From: Max Nikulin <manikulin@gmail.com>
To: emacs-orgmode@gnu.org
Cc: emacs-devel@gnu.org
Subject: Re: Completion of links to man pages
Date: Thu, 5 Oct 2023 22:59:09 +0700 [thread overview]
Message-ID: <ufmmgh$m6u$1@ciao.gmane.io> (raw)
In-Reply-To: <87jzs1i6aa.fsf@localhost>
On 05/10/2023 19:48, Ihor Radchenko wrote:
> Max Nikulin writes:
>
>> Frankly speaking, I am unsure if woman should be supported in Org at
>> all. My early experience with woman.el was not nice. I tried M-x woman
>> RET ssh RET (openssh).
>
> woman is not trying to be complete. See [[info:woman#Introduction]].
>
> For Org support, we already support it, and it would be a feature
> regression if we remove it.
World has changed since woman.el was developed. Are there systems with
man pages available, but no man command nowadays? Android with man pages
copied by its user?
I see a little value in a tool that can not handle a wide spread case
when a better one is available. Features, that were unique for woman,
have been implemented for man.
In WoMan I have not found a way to open <man:man(7)> directly without an
additional prompt for the page section.
man.el has a lot of options how to select window for a man page. It is
not the case for woman. For Org internal link types same/other window is
controlled by prefix argument (however `org-open-at-point' doc string
describes another meaning of prefix argument: if link should be opened
in Emacs or an external application). I am unsure what is proper
behavior of man links opened from Org, should Org try to make behavior
consistent or it should let packages to act as they wish.
next prev parent reply other threads:[~2023-10-05 16:00 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-04 11:40 Completion of links to man pages Max Nikulin
2023-10-05 11:40 ` Ihor Radchenko
2023-10-05 12:20 ` Max Nikulin
2023-10-05 12:48 ` Ihor Radchenko
2023-10-05 15:59 ` Max Nikulin [this message]
2023-10-05 16:15 ` Ihor Radchenko
2023-10-05 16:37 ` Eli Zaretskii
2023-10-05 16:55 ` Ihor Radchenko
2023-10-05 17:13 ` Eli Zaretskii
2023-10-05 17:30 ` Ihor Radchenko
[not found] ` <ufnvit$12ho$1@ciao.gmane.io>
2023-10-06 21:37 ` Richard Stallman
2023-10-07 11:14 ` Michael Albinus
2023-10-06 3:58 ` Max Nikulin
2023-10-05 15:52 ` Eli Zaretskii
2023-10-05 16:05 ` Ihor Radchenko
2023-10-05 16:33 ` Eli Zaretskii
2023-10-05 16:53 ` Ihor Radchenko
2023-10-05 17:11 ` Eli Zaretskii
2023-10-05 17:36 ` Ihor Radchenko
2023-10-06 3:16 ` Max Nikulin
2023-12-09 11:32 ` Ihor Radchenko
2023-12-13 15:20 ` [PATCH] ol-man.el: Enable completion Max Nikulin
2023-12-14 15:09 ` Ihor Radchenko
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.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='ufmmgh$m6u$1@ciao.gmane.io' \
--to=manikulin@gmail.com \
--cc=emacs-devel@gnu.org \
--cc=emacs-orgmode@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 public inbox
https://git.savannah.gnu.org/cgit/emacs/org-mode.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).