From: Jesper Harder <harder@myrealbox.com>
Subject: Re: emacs documentation for (La)TeX
Date: Mon, 22 Dec 2003 17:50:25 +0100 [thread overview]
Message-ID: <m3wu8o7q5q.fsf@defun.localdomain> (raw)
In-Reply-To: mailman.451.1072070152.868.help-gnu-emacs@gnu.org
Joe Corneli <jcorneli@math.utexas.edu> writes:
> I am thinking about trying to use Emacs' self-documenting features
> to create some "native" documentation for LaTeX. I'm thinking about
> building this based on the TeX documentation being made available at
> www.miwie.org
Just install 'latex2e.texi' from the tarball. Then you can look up
LaTeX commands with `C-h C-i' [1] -- no extra work required :-)
> Has ever tried to use Emacs' self-documenting features to document
> another computer language?
I think the best approach is to write Texinfo documentation like
latex2e.texi.
[1] Unfortunately changed to `C-h S' in CVS.
next prev parent reply other threads:[~2003-12-22 16:50 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <E1AX8MA-0007qZ-00@linux183.ma.utexas.edu>
[not found] ` <20031220172409.GA2259@miwie.in-berlin.de>
2003-12-22 4:13 ` emacs documentation for (La)TeX Joe Corneli
[not found] ` <mailman.451.1072070152.868.help-gnu-emacs@gnu.org>
2003-12-22 15:36 ` Kai Grossjohann
2003-12-22 16:50 ` Jesper Harder [this message]
[not found] <E1AYWTr-0002OH-0w@monty-python.gnu.org>
2003-12-22 21:14 ` Joe Corneli
[not found] ` <mailman.487.1072131422.868.help-gnu-emacs@gnu.org>
2003-12-22 22:36 ` Jesper Harder
2003-12-25 16:33 ` Kai Grossjohann
[not found] <E1AYhTJ-0004l8-M8@monty-python.gnu.org>
2003-12-23 18:19 ` Joe Corneli
[not found] ` <mailman.527.1072207300.868.help-gnu-emacs@gnu.org>
2003-12-23 20:28 ` Kevin Rodgers
[not found] <E1AYzMh-0004iH-6u@monty-python.gnu.org>
2003-12-24 3:44 ` Joe Corneli
[not found] <E1AZe1u-00038Z-U8@monty-python.gnu.org>
2003-12-25 22:23 ` Joe Corneli
[not found] ` <mailman.628.1072394739.868.help-gnu-emacs@gnu.org>
2003-12-25 22:34 ` Kai Grossjohann
2003-12-26 3:10 ` Brad Collins
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=m3wu8o7q5q.fsf@defun.localdomain \
--to=harder@myrealbox.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.
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).