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 19:33:04 +0200 [thread overview]
Message-ID: <83h6ut25kf.fsf@gnu.org> (raw)
In-Reply-To: <vy0DJFXuAa2e1f565NcCh8bxizRDdc6ClEmjsjQkTSd7HxEm1I4DI7SZR1Rbqa-1CXNgNryisex7Z3ouZw2ONIVS-UnQ9SmaCmUZrC7gd8k=@protonmail.com> (message from goncholden on Thu, 09 Mar 2023 17:04:55 +0000)
> Date: Thu, 09 Mar 2023 17:04:55 +0000
> From: goncholden <goncholden@protonmail.com>
> Cc: emacs-devel@gnu.org
>
> > 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.
>
> etags are all new for me.
All the languages except Emacs Lisp are supported via etags. And you
can optionally have Emacs Lisp functions supported by etags as well,
in which case you will be able to find functions that are not yet
loaded into Emacs.
next prev parent reply other threads:[~2023-03-09 17:33 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
2023-03-09 17:04 ` goncholden
2023-03-09 17:33 ` Eli Zaretskii [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=83h6ut25kf.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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.