emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed

From: Nick Dokos <nicholas.dokos@hp.com>
To: Carsten Dominik <dominik@uva.nl>
Cc: emacs-org list <emacs-orgmode@gnu.org>, nicholas.dokos@hp.com
Subject: Re: Command names are now in the manual
Date: Sat, 13 Nov 2010 17:43:13 -0500	[thread overview]
Message-ID: <19850.1289688193@gamaville.dokosmarshall.org> (raw)
In-Reply-To: Message from Carsten Dominik <dominik@uva.nl> of "Sat, 13 Nov 2010 15:50:58 CST." <02ED74E1-13B7-4535-A669-F217824157AA@uva.nl>

Carsten Dominik <dominik@uva.nl> wrote:


> I have just added the last command missing names to the manual.  So if =20=
> 
> you compile the manual in the latest git version, you will find =20
> command names listed for almost all keys listed in the manual, along =20
> with a much extended command and function index.
> 

I think there is a problem on line 4668: the @findex seems to dislike
braces around the name:

,----
| $ make html
| (cd doc; makeinfo --html --number-sections --no-split -o org.html org.texi)
| /home/nick/src/emacs/org/org-mode/doc
| org.texi:4668: Misplaced {.
| org.texi:4668: Misplaced }.
| org.texi:4668: Misplaced {.
| org.texi:4668: Misplaced }.
| makeinfo: Removing output file `org.html' due to errors; use --force to preserve.
| make: *** [doc/org.html] Error 1
`----

Other than that, it looks pretty good.

A suggestion for a possible(?) improvement: the "O" section of the
function index (and I imagine the variable index as well) is pretty
crowded :-). I wonder if texinfo has any facilities to break it up,
perhaps according to the first letter after the first dash.

Thanks!
Nick

next prev parent reply	other threads:[~2010-11-13 22:43 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-11-13 21:50 Command names are now in the manual Carsten Dominik
2010-11-13 22:43 ` Nick Dokos [this message]
2010-11-14 10:33   ` Carsten Dominik
2010-11-16  3:15 ` Samuel Wales
2010-11-16  6:58   ` Carsten Dominik
2010-11-16 23:18     ` Samuel Wales

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.orgmode.org/

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

  git send-email \
    --in-reply-to=19850.1289688193@gamaville.dokosmarshall.org \
    --to=nicholas.dokos@hp.com \
    --cc=dominik@uva.nl \
    --cc=emacs-orgmode@gnu.org \
    /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

Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs/org-mode.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).