Samuel Wales <samolog...@gmail.com> writes: > Great write-up, Thorsten.
thanks > There is a whole other set of options also. I don't know if they are > close enough for you to include, but it's worth pointing them out. > > These are in the general category of Org annotations. Instead of > editing Org in a temporary buffer, you use a real, permanent Org file > (can include an agenda file). > > There are two types of options: those that allow you to use Org to > annotate external files without changing those files, and those that > allow you to annotate external files by putting persistent markers in > them. > > In both types, you can in principle do C-c ' to get to your Org agenda > files location from your external files, and the same thing in > reverse. > > The existing mechanisms include org-pua.el, org-registry.el, and > org-annotate.el. > > In principle, you should be able to annotate web pages in w3m.el and > dired entries and info notes also. > > To me, there is a lot of possibility here. > It should also be possible to put an ID marker in an external file, > which corresponds exactly to the Org IDs in a canonical entry in your > agenda files. Then C-c ' can bounce between the external file and > your agenda file. please see my recent post about 'navi-mode' for Org-mode buffers. 'navi-mode' actually is a kind of permanent associated buffer tightly coupled to the original Org-mode or source code buffer. It uses markers to allow bouncing between the associated 'twin-buffers', but non of the libraries you mention. However, I worked out my own system to ensure that the *Navi* buffer is always up-to-date after modifying the original-buffer, and to locate point at a logical position in the navi-buffer even when the view (on the original-buffer has changed drastically). The temporary editing of source-code in Org-mode buffers is inspired by org-src.el (or Org Babel), its very fast and convenient, just like editing source-code blocks in Org-mode. Just try it out, maybe it is similar to what you imagine (only with different implementation). -- cheers, Thorsten
