From: Rasmus <rasmus@gmx.us>
To: emacs-orgmode@gnu.org
Subject: Re: Feature request: #+INCLUDE: with anchors
Date: Thu, 11 Jan 2018 11:39:29 +0100 [thread overview]
Message-ID: <878td4r866.fsf@gmx.us> (raw)
In-Reply-To: b999f17e7f8614ebc2349af311b80d14@openmail.cc
edgar@openmail.cc writes:
> Hello,
>
> I have seen this syntax in markdown (one of the many versions):
>
> !listing
> path/to/file.ext
> start=ini_keyword end=end_keyword
>
> Here, ~file.ext~ is a source file, and both ~ini_keyword~ and
> ~end_keyword~ are text strings in the text delimiting what should be
> included (responsibility of the writer to make sure they are
> unique). I think that having something like this in Org would be
> nice. I am aware of the ~:lines~ option, but having something like
> this would not require an update of the numeric reference every time
> the referenced file changes.
What would happen if one of the keywords aren’t unique?
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’.
Rasmus
--
Tack, ni svenska vakttorn. Med plutonium tvingar vi dansken på knä!
next prev parent reply other threads:[~2018-01-11 10:39 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-10 18:30 Feature request: #+INCLUDE: with anchors edgar
2018-01-11 10:39 ` Rasmus [this message]
[not found] <mailman.77.1515690017.29034.emacs-orgmode@gnu.org>
2018-01-12 7:14 ` edgar
2018-01-23 8:16 ` 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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=878td4r866.fsf@gmx.us \
--to=rasmus@gmx.us \
--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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.