From mboxrd@z Thu Jan 1 00:00:00 1970 From: edgar@openmail.cc Subject: Feature request: #+INCLUDE: with anchors Date: Wed, 10 Jan 2018 18:30:15 +0000 Message-ID: Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII; format=flowed Content-Transfer-Encoding: 7bit Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:56007) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1eZLgm-0006tX-Im for emacs-orgmode@gnu.org; Wed, 10 Jan 2018 14:05:29 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1eZLgh-000682-JH for emacs-orgmode@gnu.org; Wed, 10 Jan 2018 14:05:28 -0500 Received: from onethreetwo.vfemail.net ([199.16.11.132]:21819 helo=vfemail.net) by eggs.gnu.org with esmtps (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.71) (envelope-from ) id 1eZLgh-00067Q-Bj for emacs-orgmode@gnu.org; Wed, 10 Jan 2018 14:05:23 -0500 List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org Sender: "Emacs-orgmode" To: emacs-orgmode@gnu.org 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. Thanks for the great work! ------------------------------------------------- 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!