Samuel Wales <samolog...@gmail.com> writes: > On 4/5/13, Thorsten Jolitz <tjol...@gmail.com> wrote: >> that sounds like a different idea. I have heard about programming >> environments that keep comments and source-code in two different (but >> sync'd) files to minimize distraction from the source code - maybe a >> possible use case for your idea? > > Yes. The purpose for keeping them separate is to have one of them be > a complete Org file.
If you structure your Emacs Lisp files the 'outshine way', you can convert them into complete Org files fast and easily using 'outorg.el'. Use ,---------- | C-u C-c ' `---------- from inside the elisp buffer, or ,------ | C-u e `------ in the associated *Navi:my-elisp-file* buffer. Both bindings call '(outorg-edit-as-org &optional ARG)' with ARG and thus act on the complete buffer, not only the subtree at point. Therefore, whenever you want to edit text, your Emacs Lisp source code buffer becomes a (complete or partial) Org-mode buffer in a second, while you are in emacs-lisp-mode most of the time when its about editing code - only enhanced with Org-mode's look&feel by the activation of 'outline-minor-mode' with 'outshine.el' extensions. When its not about whole Org-mode buffers or whole subtrees (with headlines and code-blocks), but just about atomic comment-strings to be edited in Org-mode buffers, then 'poporg.el' is the tool of choice. -- cheers, Thorsten
