all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Joe Corneli <jcorneli@math.utexas.edu>
Subject: Re: emacs documentation for (La)TeX
Date: Mon, 22 Dec 2003 15:14:59 -0600	[thread overview]
Message-ID: <E1AYXOF-0007cs-00@linux183.ma.utexas.edu> (raw)
In-Reply-To: <E1AYWTr-0002OH-0w@monty-python.gnu.org> (help-gnu-emacs-request@gnu.org)

> I think the best approach is to write Texinfo documentation like
> latex2e.texi.

Indeed Michael Wiedmann is currently looking into exporting his
DocBook XML documentation of LaTeX to texinfo format.  But there is
something very nice in my opinion about being able to get the
documentation for Lisp functions with C-h f RET when you are writing
code. Between info-look.el and a more robust latex texinfo manual, it
looks like most of my questions about latex could be answered just as
easily as my ELisp questions[0].  Except perhaps for links to the
source, which may be the most useful feature of describe-function.
Perhaps this feature could be added directly to the texinfo package
(?), but that seems a bit non-standard.

[0] In general I tend to prefer looking at the documentation of
functions whose names I know -- for complicated questions (E.g. "how
do I get the diary to work properly?") that have relatively simple
answers, this often isn't as effective as looking in the manual.  But
it is a habit, and for simple questions it seems to be a very
effective strategy.  It might be that Emacs could do a better job of
providing in-line documentation for high-level questions in the
source files -- or maybe I just need to train myself to reflexively
look in the manual instead of the code for these kinds of
questions. At any rate, the reason I'm so keen on in-line help for
latex functions is mostly my interest in better understanding
low-level questions, where a link to the source together with a terse
doc string is typically the most useful thing one can look at.

       reply	other threads:[~2003-12-22 21:14 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <E1AYWTr-0002OH-0w@monty-python.gnu.org>
2003-12-22 21:14 ` Joe Corneli [this message]
     [not found] ` <mailman.487.1072131422.868.help-gnu-emacs@gnu.org>
2003-12-22 22:36   ` emacs documentation for (La)TeX Jesper Harder
2003-12-25 16:33   ` Kai Grossjohann
     [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
     [not found] <E1AYzMh-0004iH-6u@monty-python.gnu.org>
2003-12-24  3:44 ` Joe Corneli
     [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] <E1AX8MA-0007qZ-00@linux183.ma.utexas.edu>
     [not found] ` <20031220172409.GA2259@miwie.in-berlin.de>
2003-12-22  4:13   ` 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

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=E1AYXOF-0007cs-00@linux183.ma.utexas.edu \
    --to=jcorneli@math.utexas.edu \
    /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.