Hi, Org people. It is often suggested that literate Org programming means interspersing program fragments within an Org file. For practical reasons, I rather prefer adding Org documentation into my programs. So this helping tool which pops out a temporary Org mode buffer with the contents of the current block comment or (doc-)string, and which replaces the original once the editing is done. Some remaining issues, I know, and surely lots I do not know! The tool is usable enough to be shared, for those who would happen to have a use for it. I put it there: https://github.com/pinard/PopOrg Keep happy, all! François
Hi François, François Pinard <pinard@iro.umontreal.ca> writes: > https://github.com/pinard/PopOrg I added a link to https://github.com/pinard/PopOrg/blob/master/poporg.el In worg/org-hacks.org: http://orgmode.org/cgit.cgi/worg.git/commit/?id=c0a908 Please edit this further to refine it! Thanks, -- Bastien
I like the idea a lot. Thanks for posting it. It will help with lists in elisp files. Also wondering about the opposite. What if we could have bidirectional links, and actually use an agenda file for some of the entries instead of keeping the entries in the non-Org file? Samuel -- The Kafka Pandemic: http://thekafkapandemic.blogspot.com The disease DOES progress. MANY people have died from it. ANYBODY can get it. There is no hope without action.
Samuel Wales <samologist@gmail.com> writes:
> What if we could have bidirectional links, and actually use an agenda
> file for some of the entries instead of keeping the entries in the
> non-Org file?
I'm not sure I understand the use case you have in head. Maybe
executable links could be helpful to you? I use them to generate Org
views I often need (they look like [[elisp:CODE][BUTTON NAME]]).
François
Hi Francois, On 1/24/13, François Pinard <pinard@iro.umontreal.ca> wrote: > I'm not sure I understand the use case Your Org in elisp solution allows limited Org functionality in Elisp and other files. You cannot put those files in the agenda, or do many other things that you can do with agenda files. The entries are not in an Org context. They are in an external file. What I am suggesting as a possible alternative in some cases, is to have all of your notes about the elisp file in your ordinary Org agenda files. However, this is not Babel. Instead, it is a bidirectional Org<->non-Org link. A command in the external file will find the nearest bidirectional link, then take you to its dual entry in your Org files. And a command in Org will take you to the place in elisp that points to that entry. So in elisp you will have: ;;; $[bidir da39a3ee5e6b4b0d3255bfef95601890afd80709] And in your Org file you will have: * my notes on that part of elisp :PROPERTIES: :ID: da39a3ee5e6b4b0d3255bfef95601890afd80709 :END: Here are my notes. === This will allow you to use the full power of Org without tangling. Samuel -- The Kafka Pandemic: http://thekafkapandemic.blogspot.com The disease DOES progress. MANY people have died from it. ANYBODY can get it. There is no hope without action.