emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Nicolas Goaziou <mail@nicolasgoaziou.fr>
To: Kaushal Modi <kaushal.modi@gmail.com>
Cc: emacs-org list <emacs-orgmode@gnu.org>
Subject: Re: Section on #+include keyword is missing quite some info in the org-manual.org
Date: Wed, 26 Sep 2018 12:47:41 +0200	[thread overview]
Message-ID: <87ftxwr0vm.fsf@nicolasgoaziou.fr> (raw)
In-Reply-To: <CAFyQvY3oeSo__MwtXgqtxrwBU7PhoJb0kpCvaxR5yw2TEfXAfQ@mail.gmail.com> (Kaushal Modi's message of "Tue, 25 Sep 2018 22:23:39 -0400")

Hello,

Kaushal Modi <kaushal.modi@gmail.com> writes:

> I was visiting the Org manual to verify if I got the :only-contents
> parameter of #+include keyword correct, and noticed that that info is
> completely missing from that section in the new org-manual.org.
>
> Reverting back to older texi, it is missing pieces like below and much more too:
>
> #+INCLUDE: "./paper.org::#theory" :only-contents t
>    @r{Include the body of the heading with the custom id @samp{theory}}
>
> #+INCLUDE: "./paper.org::mytable"  @r{Include named element.}
> #+INCLUDE: "./paper.org::*conclusion" :lines 1-20
>
>    @r{Include the first 20 lines of the headline named @samp{conclusion}.}
>
>
> If this is not intentional (looks like it's not because that feature
> works great and I would miss it if it did not), I can commit update to
> org-manual.org with that whole section restored from the past.

This is not intentional. Could you re-introduce the latest revision of
that section?

> But I am wondering if things are more serious.. how do we ensure that
> the org-manual.org is not missing out the useful info from the old
> org.texi?

Eyeballing. I did it a couple of times already, but more eyes are
needed, obviously.

Thank you.

Regards,

-- 
Nicolas Goaziou

  reply	other threads:[~2018-09-26 10:47 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-09-26  2:23 Section on #+include keyword is missing quite some info in the org-manual.org Kaushal Modi
2018-09-26 10:47 ` Nicolas Goaziou [this message]
2018-10-01 19:25   ` Kaushal Modi
2018-10-04 15:00     ` Kaushal Modi

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=87ftxwr0vm.fsf@nicolasgoaziou.fr \
    --to=mail@nicolasgoaziou.fr \
    --cc=emacs-orgmode@gnu.org \
    --cc=kaushal.modi@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).