p.s. presumably the agenda would in some cases want to distinguish canonical [in the place whwere ther data will be saved] from non-canonical.
also presumably a few traversing commands would want to recognize such regions in order tonot follow non-canonical, or to look for infinite looping, etc. presumably org-id is the best solution for keeping track of which files have or need virtual regions. basically an underneath layer of org-id [but maybe not limited to entries] that the user does not interact with. On 5/2/20, Samuel Wales <samolog...@gmail.com> wrote: > stating the obvious: org typically stores a forest [files] of trees of > nodes. some things you want to put into it are best expressed more > generally than with trees. i call it [boring name] the tree problem. > > there are a bunch of existing sort-of solutions, but to me the best is > linking [as you mentioned], using org-id. although that only links to > entries, and it requires following links. one entry becomes > canonical. you have to set metadata for the linking node. > > there are solutions not implemented that could be better that have > been talked about on the mailng list, but they still have the issues > of following links or other issues. > > duplication is out the window because dry. > > what you seem to want seems to require a feature in emacs in which you > have virtual includable regions. this can be done to a large degree > at the buffer level, but not at the region level. > > that would open up some interesting possibilities, maybe including > inline multi-mode stuff. and it would fix your problem. you could > maybe color the one that is in the file itself differently, or keep > all looking equal status to the user. > > i think there has been discussion on the mailing list and probalby on > emacs-devel recently about an idea similar to this. it migth be teh > same as what you want. not sure. > > it goes by a different name. smoevbody will chime in i hope. > > On 5/2/20, David Rogers <davidandrewrog...@gmail.com> wrote: >> Is there a method I can use to include the same subtree in several >> different >> files, such that editing one instance of that subtree updates the others >> automatically? I'm hoping to be able to view the full version of the >> subtree >> in each of the files, without having to follow a link; if what I'm >> describing isn't really possible, then I'll just use links in the other >> files to point to the original subtree, which I know how to do. I'm just >> exploring the sometimes-unexpected possibilities. :) >> >> -- >> Thanks >> David >> >> > > > -- > The Kafka Pandemic > > What is misopathy? > https://thekafkapandemic.blogspot.com/2013/10/why-some-diseases-are-wronged.html > -- The Kafka Pandemic What is misopathy? https://thekafkapandemic.blogspot.com/2013/10/why-some-diseases-are-wronged.html
