From: Eric S Fraga <ucecesf@ucl.ac.uk>
To: Dan Davison <davison@stats.ox.ac.uk>
Cc: "Sébastien Vauban" <wxhgmqzgwmuf@spammotel.com>,
emacs-orgmode@gnu.org,
"Giles Chamberlin" <giles.chamberlin@tandberg.com>
Subject: Re: Re: Limited #+INCLUDE ?
Date: Tue, 27 Apr 2010 09:27:45 +0100 [thread overview]
Message-ID: <878w89l2pq.wl%ucecesf@ucl.ac.uk> (raw)
In-Reply-To: <87eii26lzg.fsf@stats.ox.ac.uk>
On Mon, 26 Apr 2010 15:40:35 -0400, Dan Davison <davison@stats.ox.ac.uk> wrote:
> I'm considering investigating the following and would appreciate
> comments on this idea. The aim is to make it easier to use Org-mode to
> work pure code files which are *external to Org-mode* (i.e. this
> proposal lies outside of the current org-babel tangling framework).
>
> - Extend Org file links to allow links to a range of lines in a
> file. The syntax could be
> [[file:/path/to/file::from::to][linkname]]
+1
I like this idea, especially for exporting complex documents. If
org-store-link were enhanced to generate links with this line
information, I would probably use this a lot.
> - These links will bring up a buffer visiting the target file, narrowed
> to the target region.
Or could be brought up with a wide view but with the region selected?
> - 'from' and 'to' could be line numbers, or regexps for text search.
The latter could be quite appealing, although possibly a little
fragile.
next prev parent reply other threads:[~2010-04-27 9:29 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-23 11:25 Limited #+INCLUDE ? Giles Chamberlin
2010-04-26 8:32 ` Sébastien Vauban
2010-04-26 19:40 ` Dan Davison
2010-04-27 0:34 ` Mark Elston
2010-04-27 2:19 ` Dan Davison
2010-04-28 0:52 ` Mark Elston
2010-04-27 8:27 ` Eric S Fraga [this message]
2010-04-27 10:25 ` Darlan Cavalcante Moreira
2010-04-27 15:12 ` Eric Schulte
2010-04-27 17:26 ` Dan Davison
2010-04-27 17:58 ` Eric Schulte
2010-04-27 18:27 ` Giles Chamberlin
2010-04-27 17:52 ` Samuel Wales
2010-04-27 19:19 ` Dan Davison
2010-04-27 21:56 ` Carsten Dominik
2010-04-29 23:14 ` Samuel Wales
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=878w89l2pq.wl%ucecesf@ucl.ac.uk \
--to=ucecesf@ucl.ac.uk \
--cc=davison@stats.ox.ac.uk \
--cc=e.fraga@ucl.ac.uk \
--cc=emacs-orgmode@gnu.org \
--cc=giles.chamberlin@tandberg.com \
--cc=wxhgmqzgwmuf@spammotel.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).