all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Kai Grossjohann <kai@emptydomain.de>
Subject: Re: emacs documentation for (La)TeX
Date: Mon, 22 Dec 2003 16:36:21 +0100	[thread overview]
Message-ID: <87ad5kzwy2.fsf@emptyhost.emptydomain.de> (raw)
In-Reply-To: mailman.451.1072070152.868.help-gnu-emacs@gnu.org

Joe Corneli <jcorneli@math.utexas.edu> writes:

> Has ever tried to use Emacs' self-documenting features to document
> another computer language?

The sawfish mode does it by defining commands
sawfish-describe-function, sawfish-describe-variable and so on.

I guess you might also try to leverage info-look.el (or infolook.el?)
to your purposes.  It can already give you the documentation for libc
functions, I think, so it would be natural to extend it to LaTeX.

What do people think?

Kai

  parent reply	other threads:[~2003-12-22 15:36 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 [this message]
2003-12-22 16:50     ` Jesper Harder
     [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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87ad5kzwy2.fsf@emptyhost.emptydomain.de \
    --to=kai@emptydomain.de \
    /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.