emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Suvayu Ali <fatkasuvayu+linux@gmail.com>
To: Emacs Org mode <emacs-orgmode@gnu.org>
Subject: Fix info manual compilation
Date: Sat, 13 Apr 2013 21:35:27 +0200	[thread overview]
Message-ID: <20130413193527.GA11353@kuru.dyndns-at-home.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 163 bytes --]

hi,

The info manual does not compile because of a wrong next node entry in
org.texi.  A fix is attached.

-- 
Suvayu

Open source is the future. It sets us free.

[-- Attachment #2: 0001-Fix-org-info-manual-compilation.patch --]
[-- Type: text/plain, Size: 875 bytes --]

From bed20723adc4700df5289804ab4254d705fe148f Mon Sep 17 00:00:00 2001
From: Suvayu Ali <fatkasuvayu+linux@gmail.com>
Date: Sat, 13 Apr 2013 21:33:17 +0200
Subject: [PATCH] Fix org info manual compilation

---
 doc/org.texi | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/doc/org.texi b/doc/org.texi
index 645c8c5..c65bdc1 100644
--- a/doc/org.texi
+++ b/doc/org.texi
@@ -11273,7 +11273,7 @@ You can choose default values for these options by customizing the variable
 @code{org-html-infojs-options}.  If you always want to apply the script to your
 pages, configure the variable @code{org-html-use-infojs}.
 
-@node @LaTeX{} and PDF export, OpenDocument Text export, HTML export, Exporting
+@node @LaTeX{} and PDF export, Markdown export, HTML export, Exporting
 @section @LaTeX{} and PDF export
 @cindex @LaTeX{} export
 @cindex PDF export
-- 
1.8.1.4


             reply	other threads:[~2013-04-13 19:35 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-04-13 19:35 Suvayu Ali [this message]
2013-04-13 20:42 ` Fix info manual compilation Nicolas Goaziou
2013-04-14  1:45   ` Suvayu Ali
2013-04-14  7:41     ` Nicolas Goaziou
2013-04-14  9:44       ` Suvayu Ali
2013-04-14  8:34     ` Bastien
2013-04-14 10:05       ` Suvayu Ali
2013-04-14 10:09         ` Bastien

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=20130413193527.GA11353@kuru.dyndns-at-home.com \
    --to=fatkasuvayu+linux@gmail.com \
    --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
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

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