emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Max Nikulin <manikulin@gmail.com>
To: emacs-orgmode@gnu.org
Subject: Re: Problems generating the org-mode documentation
Date: Sat, 23 Oct 2021 21:50:28 +0700	[thread overview]
Message-ID: <sl17fn$17g4$1@ciao.gmane.io> (raw)
In-Reply-To: <87fssss7us.fsf@kyleam.com>

On 23/10/2021 11:06, Kyle Meyer wrote:
> Hoffmann, Jobst writes:
>> But I think I found the culprit:
>> Line 17568 of org.texi reads:
>> @kindex C-c C-x @
>> and @ starts a command, which leads to the stack overflow.
>> Line 17568 of org.texi should read
>> @kindex C-c C-x @@
>> witha doubled @ at the end of the line and after applying this change
>> org.texi the documentation org.pdf can be generated without any error.
> Marco Wahl fixed this entry a few days ago on the bugfix branch:
> 37791bb4f (org-manual: Fix one kindex entry, 2021-10-18).

Shouldn't it be handled by ox-texinfo.el instead? However it is a rare 
case, so it is not really important. Are there cases when raw texinfo 
commands are requires in "#+kindex:" strings? Formally some other 
exporter might support kindex...

  parent reply	other threads:[~2021-10-23 14:51 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-10-22  6:16 Problems generating the org-mode documentation Vincent Breton
2021-10-22  6:34 ` Pedro Andres Aranda Gutierrez
2021-10-26 15:09   ` Jean-Christophe Helary
2021-10-22  9:47 ` Alan Ristow
2021-10-22 10:46 ` Hoffmann, Jobst
2021-10-23  4:06   ` Kyle Meyer
2021-10-23  9:55     ` Pedro Andres Aranda Gutierrez
2021-10-23 14:50     ` Max Nikulin [this message]
2021-10-22 15:54 ` Max Nikulin
     [not found] <CAO48Bk82nSQeWaxQ=A97BNdc80bbWvpwQwyh=1e-Ag-oS=QbjQ@mail.gmail.com>
2021-10-18 13:12 ` Jean-Christophe Helary

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:

  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='sl17fn$17g4$1@ciao.gmane.io' \
    --to=manikulin@gmail.com \
    --cc=emacs-orgmode@gnu.org \


* 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 public inbox


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).