From: Eli Zaretskii <eliz@gnu.org>
To: goncholden <goncholden@protonmail.com>
Cc: emacs-devel@gnu.org
Subject: Re: Documentation by function beyond elisp
Date: Thu, 09 Mar 2023 17:48:45 +0200 [thread overview]
Message-ID: <83lek60vtu.fsf@gnu.org> (raw)
In-Reply-To: <GPDtriFJCzLPM-jk7aE1YxY-0TYmX_njhFP5beWqL1ca2Ywm_knE88difexPjs5diijMu6ymmzpmThHZZY0LsuRoRBDsD4eUJaSKCNt2s8Y=@protonmail.com> (message from goncholden on Thu, 09 Mar 2023 13:01:31 +0000)
> Date: Thu, 09 Mar 2023 13:01:31 +0000
> From: goncholden <goncholden@protonmail.com>
> Cc: emacs-devel@gnu.org
>
>
> ------- Original Message -------
> On Friday, March 10th, 2023 at 12:24 AM, Eli Zaretskii <eliz@gnu.org> wrote:
>
>
> > > Date: Thu, 09 Mar 2023 11:33:02 +0000
> > > From: goncholden goncholden@protonmail.com
> > >
> > > For elisp files, emacs has the capability of showing documentation by function. A valuable tool
> > > would be to extend such functionality to others like bash and awk. Perhaps one can come up
> > > with something that could work beautifully. Have there been an ideas for such capability extension
> > > before?
> >
> >
> > Did you try "C-h S"?
>
> That does not work for user-defined awk functions, complaining that a function name
> is not a symbol.
You could teach etags about Awk programs and shell scripts. Or maybe
some variant of the tags program out there already supports those, in
which case Emacs should be able to give you what you want for free,
after you run that tags program on your Awk/Bash source files.
next prev parent reply other threads:[~2023-03-09 15:48 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
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 [this message]
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=83lek60vtu.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=goncholden@protonmail.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).