emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Nick Dokos <nicholas.dokos@hp.com>
To: Rainer M Krug <r.m.krug@gmail.com>
Cc: nicholas.dokos@hp.com, emacs-orgmode <emacs-orgmode@gnu.org>
Subject: [PATCH] doc bug [was: info documentation not in sync with pdf]
Date: Fri, 10 Jun 2011 11:26:58 -0400	[thread overview]
Message-ID: <4744.1307719618@alphaville.americas.hpqcorp.net> (raw)
In-Reply-To: Message from Rainer M Krug <r.m.krug@gmail.com> of "Fri, 10 Jun 2011 10:09:45 +0200." <BANLkTinvsch5jMXAaUhgW+8EtRiEJWo8PAu2nz9rzXy4x0ZQLw@mail.gmail.com>

Rainer M Krug <r.m.krug@gmail.com> wrote:

> On Thu, Jun 9, 2011 at 5:37 PM, Eric Schulte <schulte.eric@gmail.com> wrote:
> 
> > Hi Rainer,
> >
> > There is a section on the :padline header argument in the "Specific
> > Header Arguments" section of the Org-mode documentation, however you
> > most likely need a more recent version of the documentation loaded.
> >
> > This header and documentation were added in March.
> >
> 
> I am using  Org-mode version 7.5 (release_7.5.360.g374b7) and I found it in
> the info documentation, but it is not in the pdf.
> 

Doc bug:

diff --git a/doc/org.texi b/doc/org.texi
index eb97759..7caf680 100644
--- a/doc/org.texi
+++ b/doc/org.texi
@@ -12410,6 +12410,7 @@ references in the code block body in link comments.
 @end itemize
 
 @node padline, no-expand, comments, Specific header arguments
+@subsubsection @code{:padline}
 Control in insertion of padding lines around code block bodies in tangled
 code files.  The default value is @code{yes} which results in insertion of
 newlines before and after each tangled code block.  The following arguments
 

Nick

      reply	other threads:[~2011-06-10 15:44 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-06-10  8:09 info documentation not in sync with pdf Rainer M Krug
2011-06-10 15:26 ` Nick Dokos [this message]

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=4744.1307719618@alphaville.americas.hpqcorp.net \
    --to=nicholas.dokos@hp.com \
    --cc=emacs-orgmode@gnu.org \
    --cc=r.m.krug@gmail.com \
    /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).