From: Ihor Radchenko <yantar92@posteo.net>
To: Max Nikulin <manikulin@gmail.com>
Cc: emacs-orgmode@gnu.org, emacs-devel@gnu.org
Subject: Re: Completion of links to man pages
Date: Thu, 05 Oct 2023 11:40:44 +0000 [thread overview]
Message-ID: <87sf6pi9fn.fsf@localhost> (raw)
In-Reply-To: <ufjj01$p58$1@ciao.gmane.io>
[ CCing emacs-devel ]
Max Nikulin <manikulin@gmail.com> writes:
> I am unsure if the code below is appropriate for :complete property of
> "man" link. It does not rely on any double-dash functions or variables,
> but it still uses some implementation details since there is no suitable
> high level functions in man.el and woman.el from Emacs.
Without docstrings, we cannot rely even on single-dash functions.
To emacs-devel: Would it be of interest to expose man/woman completion
API?
> (defun org-man-complete (&optional _arg)
> "Helper for completion of links to man pages."
> (concat
> "man:"
> (let ((completion-ignore-case t)) ; See `man' comments.
`completion-ignore-case' is not set in woman.
> (funcall
> (if (eq org-man-command 'woman)
> #'org-man--complete-woman
> #'org-man--complete-man)
> "Manual entry: "))))
>
> (defun org-man--complete-man (prompt)
> (require 'man)
> (let (Man-completion-cache)
> (completing-read
> prompt
> 'Man-completion-table)))
> (defun org-man--init-woman-cache (&optional re-cache)
> (unless (and (not re-cache)
> (or
> (and woman-expanded-directory-path
> woman-topic-all-completions)
> (woman-read-directory-cache)))
> (setq woman-expanded-directory-path
> (woman-expand-directory-path woman-manpath woman-path))
> (setq woman-totic-all-completions
> (woman-topic-all-completions woman-expand-directory-path))
> (woman-write-directory-cache)))
>
> (defun org-man--complete-woman (prompt)
> (require 'woman)
> (org-man--init-woman-cache)
> (completing-read prompt woman-topic-all-completions))
--
Ihor Radchenko // yantar92,
Org mode contributor,
Learn more about Org mode at <https://orgmode.org/>.
Support Org development at <https://liberapay.com/org-mode>,
or support my work at <https://liberapay.com/yantar92>
next parent reply other threads:[~2023-10-05 11:40 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <ufjj01$p58$1@ciao.gmane.io>
2023-10-05 11:40 ` Ihor Radchenko [this message]
2023-10-05 12:20 ` Completion of links to man pages Max Nikulin
2023-10-05 12:48 ` Ihor Radchenko
2023-10-05 15:59 ` Max Nikulin
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
2023-10-06 3:40 ` Max Nikulin
2023-10-06 21:37 ` Richard Stallman
2023-10-07 3:30 ` Max Nikulin
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
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=87sf6pi9fn.fsf@localhost \
--to=yantar92@posteo.net \
--cc=emacs-devel@gnu.org \
--cc=emacs-orgmode@gnu.org \
--cc=manikulin@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 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).