I agree with Marcel on this. If org is supposed to help get /to/ the final version of a document, then it should support the (possibly inconsistent) structures that can appear in all the in-between steps after conceiving of the document and before the final version.
The workaround I use is to use lists instead of headlines. The problem then becomes the extra work of turning lists into headines+text later. Cheers. Fil On 27 March 2011 12:11, Marcel van der Boom <mar...@hsdev.com> wrote: > > On zo 27-mrt-2011 16:52 > Cian <cian.ocon...@gmail.com> wrote: > >> You can't do that, as it would be akin to trying to have in a book >> >> Section 1 >> Stuff >> Section 1.1.1 >> More stuff >> >> Now this goes under Section 1 >> >> Not really an idiom that makes sense (I find its best to think of >> org-mode's headings as chapter headers > > Agreed, for paper books that would not make much sense (depending on > how you do it) and that fact kept me from asking the question for a > while. > For electronic texts however, especially in the drafting stage where > (sub-)sections get shuffled around, promoted, demoted, split etc. it > does make sense, to me at least. > > When writing I tend to think about org headings as 'handles' to a > logical block of information, including its child blocks. Apparently my > analogy clashes with what org-mode wants. I had my hopes on a > customization option. > > Is there a strong reason this could not work as an option in org-mode? > > marcel > > -- > Marcel van der Boom -- http://hsdev.com/mvdb.vcf > HS-Development BV -- http://www.hsdev.com > So! web applications -- http://make-it-so.info > Cobra build -- http://cobra.mrblog.nl > > -- Filippo A. Salustri, Ph.D., P.Eng. Mechanical and Industrial Engineering Ryerson University 350 Victoria St, Toronto, ON M5B 2K3, Canada Tel: 416/979-5000 ext 7749 Fax: 416/979-5265 Email: salus...@ryerson.ca http://deseng.ryerson.ca/~fil/
