From: edgar@openmail.cc
To: emacs-orgmode@gnu.org
Subject: Re: Feature request: #+INCLUDE: with anchors
Date: Fri, 12 Jan 2018 07:14:45 +0000 [thread overview]
Message-ID: <890072acf0ef26b87e349615f7b83751@openmail.cc> (raw)
In-Reply-To: <mailman.77.1515690017.29034.emacs-orgmode@gnu.org>
> Message: 6
> Date: Thu, 11 Jan 2018 11:39:29 +0100
> From: Rasmus <rasmus@gmx.us>
> To: emacs-orgmode@gnu.org
> Subject: Re: [O] Feature request: #+INCLUDE: with anchors
> Message-ID: <878td4r866.fsf@gmx.us>
> Content-Type: text/plain; charset=utf-8
>
> What would happen if one of the keywords aren?t unique?
Get the first instance? what happens when a referenced heading, block or
table is not unique (or doesn't exist)?
>
> Something similar can already be done in Org. See this part of the
> manual:
>
> Inclusions may specify a file-link to extract an object matched by
> org-link-search (see Search options).
>
> To extract only the contents of the matched object, set
> :only-contents property to non-nil. This will omit any planning lines
> or property drawers. The ranges for :lines keyword are relative to the
> requested element. Some examples:
>
> #+INCLUDE: "./paper.org::#theory" :only-contents t
> Include the body of the heading with the custom id ?theory?
> #+INCLUDE: "./paper.org::mytable" Include named element.
> #+INCLUDE: "./paper.org::*conclusion" :lines 1-20
> Include the first 20 lines of the headline named ?conclusion?.
>
Although I was aware of this, I think that what you write is very
useful, thank you.
-------------------------------------------------
ONLY AT VFEmail! - Use our Metadata Mitigator to keep your email out of the NSA's hands!
$24.95 ONETIME Lifetime accounts with Privacy Features!
15GB disk! No bandwidth quotas!
Commercial and Bulk Mail Options!
next parent reply other threads:[~2018-01-12 16:51 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.77.1515690017.29034.emacs-orgmode@gnu.org>
2018-01-12 7:14 ` edgar [this message]
2018-01-23 8:16 ` Feature request: #+INCLUDE: with anchors Rasmus
2018-01-10 18:30 edgar
2018-01-11 10:39 ` Rasmus
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=890072acf0ef26b87e349615f7b83751@openmail.cc \
--to=edgar@openmail.cc \
--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).