From: Eric S Fraga <e.fraga@ucl.ac.uk>
To: John Kitchin <jkitchin@andrew.cmu.edu>
Cc: Org Mode Mailing List <emacs-orgmode@gnu.org>
Subject: Re: transcluding some org-elements in multiple places
Date: Fri, 09 Dec 2016 16:28:16 +0000 [thread overview]
Message-ID: <87shpx5aov.fsf@ucl.ac.uk> (raw)
In-Reply-To: <3d4bfe3d30ae4c5a8be905fa6b15f350@HE1PR01MB1898.eurprd01.prod.exchangelabs.com> (John Kitchin's message of "Fri, 9 Dec 2016 15:29:15 +0000")
[-- Attachment #1: Type: text/plain, Size: 1364 bytes --]
On Friday, 9 Dec 2016 at 15:29, John Kitchin wrote:
> Hi all,
>
> I have an idea for how I could transclude "copies" or links to
[...]
> Any thoughts? Do you see any potential issues?
Potentially very interesting and useful idea. Some thoughts/issues:
- not sure about the name but that's just æsthetics...
- can I link to a transcluded headline? i.e. [[#localheadline]]
- what about more than level of indirection: link to a trancluded
headline which transcludes to another etc. What is shown? Is there a
performance hit?
- definitely not sure about the name... ;-)
- what happens if the destination moves or gets deleted? the link to
it, which looked like something "complete" is now meaningless. This
could be quite confusing. This is probably the most serious issue.
- the table aspect is almost a "view" on a database which is really
appealing but would benefit from a fully defined syntax a la sql?
Would table formulas work as expected from the view of the contents?
- maybe view: as the link type?
- could we have "read-only" views? I may not want the original touched.
- how does an export work? On the view or the actual contents?
That's it for the moment based on stream of consciousness thinking!
--
: Eric S Fraga (0xFFFCF67D), Emacs 26.0.50.1, Org release_9.0.1-49-ga43eac
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 162 bytes --]
next parent reply other threads:[~2016-12-09 22:02 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <3d4bfe3d30ae4c5a8be905fa6b15f350@HE1PR01MB1898.eurprd01.prod.exchangelabs.com>
2016-12-09 16:28 ` Eric S Fraga [this message]
2016-12-14 15:55 ` transcluding some org-elements in multiple places David Talmage
2016-12-14 16:55 ` John Kitchin
2017-01-05 13:26 ` Matt Price
2017-01-05 16:37 ` John Kitchin
[not found] ` <CAN_Dec8C386-+mNODfrXZkMpoRt30xEUkjSMCZDOhpi-ydRDeg@mail.gmail.com>
[not found] ` <m2zij5qbci.fsf@Johns-MacBook-Air.local>
2017-01-06 2:17 ` Matt Price
2017-01-06 2:19 ` John Kitchin
2017-01-06 14:30 ` Matt Price
2016-12-09 15:29 John Kitchin
2016-12-16 0:26 ` Matt Price
2016-12-16 16:51 ` Matt Price
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=87shpx5aov.fsf@ucl.ac.uk \
--to=e.fraga@ucl.ac.uk \
--cc=emacs-orgmode@gnu.org \
--cc=jkitchin@andrew.cmu.edu \
/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).