From: goncholden <goncholden@protonmail.com>
To: Po Lu <luangruo@yahoo.com>
Cc: "emacs-devel@gnu.org" <emacs-devel@gnu.org>
Subject: Re: Documentation by function beyond elisp
Date: Thu, 09 Mar 2023 13:58:03 +0000 [thread overview]
Message-ID: <pcMLt2huZvai5h68GgKbflmkWqYPxsZLLC15PKxBcc0Rn8IdJzAXtGAShXQzTt0EHxpXZQZ40C3LchgS-PsIsjqX_Z_XdfbhAeDVfYIGdKA=@protonmail.com> (raw)
In-Reply-To: <87mt4mhwvx.fsf@yahoo.com>
------- Original Message -------
On Friday, March 10th, 2023 at 1:33 AM, Po Lu <luangruo@yahoo.com> wrote:
> goncholden goncholden@protonmail.com writes:
>
> > The capability is focused upon documenting user-defined functions in
> > bash and awk files.
>
>
> If you write a manual for your shell macros, functions, or awk
> functions, you can read it in Info as well. The same applies to other
> languages such as C. So please, what exactly is the feature you want?
>
> For an extensive example of the former, see the Autoconf manual.
>
> Thanks.
Your suggestion is then to write a manual to document functions and use info
for display. I have been scrutinising the possibility that the documentation
information is taken directly from the source files, rather than having to write
a separate thing, closely resembling what happens with elisp user-defined functions.
next prev parent reply other threads:[~2023-03-09 13:58 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-09 11:33 Documentation by function beyond elisp goncholden
2023-03-09 12:07 ` Po Lu
2023-03-09 12:17 ` goncholden
2023-03-09 13:33 ` Po Lu
2023-03-09 13:58 ` goncholden [this message]
2023-03-09 12:24 ` Eli Zaretskii
2023-03-09 13:01 ` goncholden
2023-03-09 15:29 ` Eli Zaretskii
2023-03-09 15:36 ` goncholden
2023-03-09 15:48 ` Eli Zaretskii
2023-03-09 17:04 ` goncholden
2023-03-09 17:33 ` Eli Zaretskii
2023-03-09 15:50 ` Yuri Khan
2023-03-10 9:14 ` Ihor Radchenko
2023-03-10 10:23 ` Yuri Khan
2023-03-10 14:43 ` João Távora
2023-03-10 14:50 ` Eshel Yaron
2023-03-10 15:33 ` João Távora
2023-03-11 10:46 ` Augusto Stoffel
2023-03-11 19:04 ` Eshel Yaron
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='pcMLt2huZvai5h68GgKbflmkWqYPxsZLLC15PKxBcc0Rn8IdJzAXtGAShXQzTt0EHxpXZQZ40C3LchgS-PsIsjqX_Z_XdfbhAeDVfYIGdKA=@protonmail.com' \
--to=goncholden@protonmail.com \
--cc=emacs-devel@gnu.org \
--cc=luangruo@yahoo.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).