[O] Re: Comma-protection of Org blocks
Achim Gratz wrote The question really is if org hasn't evolved to the point where it needs a more general quoting/escaping mechanism. +1 However there's caveat: Just run zgrep '' *.el.gz on your emacs' el.gz files and you will find that its not empty -- So general and convenient are somewhat at odds here :-) Which is why python has triple-quoted strings, raw strings and what not...
[O] Re: lisp/org-clock.el: Add param :properties to list properties in clocktable
Bernt Hansen be...@norang.ca writes: [...] Could you provide a sample clock report using this patch to get a better idea of why you find this useful? Yes, here you are, along with the contents of a sample file, so that you may get a gist of my need for inheritance. * Clocktables #+BEGIN: clocktable :maxlevel 2 :scope file :properties (Costcenter Billable) :inherit-props t Clock summary at [2011-03-27 Sun 12:04] | Costcenter| Billable | Headline | Time | | |---+--+-++--| | | | *Total time* | *3:08* | | |---+--+-++--| | A-102: General Administration | | TODO Travel cost declaration | 0:42 | | | A-102: General Administration | | TODO December 2007-2009 || 0:37 | | O-100: General overhead | | Making coffee for the lot of us | 0:06 | | | C-100: Customer relations general | | Helpdesk | 1:10 | | | C-100: Customer relations general | | Categorize our helpdesk e-mails || 0:20 | | C-101: Customer A | [X] | Help out customer a || 0:10 | | C-102: Customer B | [?] | Help out customer b on issue x || 0:20 | | C-100: Customer relations general | | Help out potential customer c || 0:20 | | W-100: Web Development| | Develop our main web app | 1:10 | | | W-100: Web Development| | that || 0:41 | | C-102: Customer B | [?] | something only customer b wants || 0:29 | #+END: Actually, my boss needs something more like the table below, which I can export to something that Outlook Times also spits out (some clocking plugin for MS Outlook that the rest of us uses, and I was supposed to use too, you may understand that that is just a silly idea for someone used to org-mode). Patches 1 and 3 allowed me to get this specific output using a custom formatter and a #+TBLFM: line, which I may post to Worg if people are interested. #+BEGIN: clocktable :formatter org-clocktable-write-outlook-times-style :maxlevel 2 :scope file :inherit-props t :properties (Costcenter Billable) :date t :block day Clock summary at [2011-03-27 Sun 12:04], for Sunday, March 27, 2011. | Date | Headline | Time | Costcenter| Billable | |+---++---+--| || *Total time* | *3.05* | | | |+---++---+--| | 27-03-2011 | TODO Travel cost declaration | 0.00 | A-102: General Administration | | | 27-03-2011 | TODO Travel cost declaration, TODO December 2007-2009 | 0.62 | A-102: General Administration | | |+---++---+--| | 27-03-2011 | Making coffee for the lot of us | 0.10 | O-100: General overhead | | |+---++---+--| | 27-03-2011 | Helpdesk | 0.00 | C-100: Customer relations general | | | 27-03-2011 | Helpdesk, Categorize our helpdesk e-mails | 0.33 | C-100: Customer relations general | | | 27-03-2011 | Helpdesk, Help out customer a | 0.17 | C-101: Customer A | [X] | | 27-03-2011 | Helpdesk, Help out customer b on issue x | 0.33 | C-102: Customer B | [?] | | 27-03-2011 | Helpdesk, Help out potential customer c | 0.33 | C-100: Customer relations general | | |+---++---+--| | 27-03-2011 | Develop our main web app | 0.00 | W-100: Web Development| | | 27-03-2011 | Develop our main web app, that| 0.68 | W-100: Web Development| | | 27-03-2011 | Develop our main web app, something only customer b wants | 0.48 | C-102:
[O] org-beamer-environment-extra format
Hi,
I was trying to configure the above variable for some overlay
environments in org-beamer. I saw a few of the default environments use
the %x format but I couldn't find any documentation about what it does.
From the exported latex file it seems a \label{somelabel} tag is
inserted. Attached is a patch including this information in the
docstring.
--
Suvayu
Open source is the future. It sets us free.
From d4ff435ff1ddd5fe85b9d4ed911a4f7f14fa500c Mon Sep 17 00:00:00 2001
From: Suvayu Ali fatkasuvayu+li...@gmail.com
Date: Sun, 27 Mar 2011 03:04:56 -0700
Subject: [PATCH] Update documentation org-beamer-environments-extra
---
lisp/org-beamer.el |1 +
1 files changed, 1 insertions(+), 0 deletions(-)
diff --git a/lisp/org-beamer.el b/lisp/org-beamer.el
index d27f91f..5dffd20 100644
--- a/lisp/org-beamer.el
+++ b/lisp/org-beamer.el
@@ -139,6 +139,7 @@ openThe opening template for the environment, with the following escapes
%h the headline text
%H if there is headline text, that text in {} braces
%U if there is headline text, that text in [] brackets
+%x inserts a \label{sec-no} tag
close The closing string of the environment.
:group 'org-beamer
--
1.7.3.4
[O] Escaping to insert comments in exported text
Hi Orgers, I wanted to insert comments in the exported tex file for latex export. Is there an standard way to do that? I found normal '%text' gets exported as '\%text'. However I can export comments by putting '%%text', it gets exported as '%\%text'. Is there any other solutions out there? -- Suvayu Open source is the future. It sets us free.
[O] Re: [PATCH] Fix html export of footnotes with lists, tables, quotes, etc.
Puneeth Attached is a patch that allows having lists, tables, blockquotes and other org blocks in footnotes. Source code blocks still don't work. Would you mind posting an example test case that covers all the above cases. I am trying to merge my branch with the most recent changes in the master. I would like to make sure that I break nothing when my changes gets merged to the master. Jambunathan K.
[O] Re: unnumbered subsections in latex export
This is slightly out of thread. I pulled the master branch with an intention to re-baseline my branch and I saw some 37 lines were changed since I branched out my odt branch. My heart just sinked. A request from my side. Would it be possible to delay adding of new capabilities and features to org-html.el till a decision on my proposed patch is made. This would considerably reduce merging effort on my side. ps: Hope I am not making a mountain out of a molehill. Jambunathan K.
[O] Re: unnumbered subsections in latex export
Hi Jambunathan, Jambunathan K kjambunat...@gmail.com writes: I pulled the master branch with an intention to re-baseline my branch and I saw some 37 lines were changed since I branched out my odt branch. My heart just sinked. A request from my side. Would it be possible to delay adding of new capabilities and features to org-html.el till a decision on my proposed patch is made. This would considerably reduce merging effort on my side. I hear you. I suggest me (and possibly others) stop adding changes to org-html.el until sunday 3th of april. Be reassured I will help fixing possible conflicts. I have been in a similar situation with Julien's big changes about org-agenda-format-item (just before 7.5): he had a complicate patch that required a lot of attention/testing from my side and any change I wanted to commit to org-agenda.el for other reasons would make his life harder. I can think of two solutions: 1. freezing changes till I can spend enough time merging the big patch; 2. breaking down the big change into small meaningful changes that I (or others) can review *easily*. I know you've been working very hard to find a solution as close as possible to solution (2) -- thanks a lot for that. Let's switch to the (1) solution right now. Best, PS: As I said in a previous email, I wasn't available as much as I wanted the last two weeks for personal reasons, and I'm working on arranging my schedule right now. -- Bastien
[O] Re: lisp/org-clock.el: Add param :properties to list properties in clocktable
Niels Giesen niels.gie...@gmail.com writes: Bernt Hansen be...@norang.ca writes: [...] Could you provide a sample clock report using this patch to get a better idea of why you find this useful? Yes, here you are, along with the contents of a sample file, so that you may get a gist of my need for inheritance. * Clocktables #+BEGIN: clocktable :maxlevel 2 :scope file :properties (Costcenter Billable) :inherit-props t Clock summary at [2011-03-27 Sun 12:04] | Costcenter| Billable | Headline | Time | | |---+--+-++--| | | | *Total time* | *3:08* | | |---+--+-++--| | A-102: General Administration | | TODO Travel cost declaration| 0:42 | | | A-102: General Administration | | TODO December 2007-2009 || 0:37 | | O-100: General overhead | | Making coffee for the lot of us | 0:06 | | | C-100: Customer relations general | | Helpdesk | 1:10 | | | C-100: Customer relations general | | Categorize our helpdesk e-mails || 0:20 | | C-101: Customer A | [X] | Help out customer a || 0:10 | | C-102: Customer B | [?] | Help out customer b on issue x || 0:20 | | C-100: Customer relations general | | Help out potential customer c || 0:20 | | W-100: Web Development| | Develop our main web app | 1:10 | | | W-100: Web Development| | that || 0:41 | | C-102: Customer B | [?] | something only customer b wants || 0:29 | #+END: Actually, my boss needs something more like the table below, which I can export to something that Outlook Times also spits out (some clocking plugin for MS Outlook that the rest of us uses, and I was supposed to use too, you may understand that that is just a silly idea for someone used to org-mode). Patches 1 and 3 allowed me to get this specific output using a custom formatter and a #+TBLFM: line, which I may post to Worg if people are interested. #+BEGIN: clocktable :formatter org-clocktable-write-outlook-times-style :maxlevel 2 :scope file :inherit-props t :properties (Costcenter Billable) :date t :block day Clock summary at [2011-03-27 Sun 12:04], for Sunday, March 27, 2011. | Date | Headline | Time | Costcenter| Billable | |+---++---+--| || *Total time* | *3.05* | | | |+---++---+--| | 27-03-2011 | TODO Travel cost declaration | 0.00 | A-102: General Administration | | | 27-03-2011 | TODO Travel cost declaration, TODO December 2007-2009 | 0.62 | A-102: General Administration | | |+---++---+--| | 27-03-2011 | Making coffee for the lot of us | 0.10 | O-100: General overhead | | |+---++---+--| | 27-03-2011 | Helpdesk | 0.00 | C-100: Customer relations general | | | 27-03-2011 | Helpdesk, Categorize our helpdesk e-mails | 0.33 | C-100: Customer relations general | | | 27-03-2011 | Helpdesk, Help out customer a | 0.17 | C-101: Customer A | [X] | | 27-03-2011 | Helpdesk, Help out customer b on issue x | 0.33 | C-102: Customer B | [?] | | 27-03-2011 | Helpdesk, Help out potential customer c | 0.33 | C-100: Customer relations general | | |+---++---+--| | 27-03-2011 | Develop our main web app | 0.00 | W-100: Web Development| | | 27-03-2011 | Develop our main web app, that| 0.68 | W-100: Web
[O] agenda view opening multiple buffers
Dear list, When asking for an agenda view (C-c a), org mode opens all files in the agenda list in individual buffers. I keep lots of files in my list (one per project), so having all those buffers open each time I visit my agenda is pretty annoying. Is there a way to make org mode not open each file in a buffer (or close the buffers after reading the file) when asking for an agenda view? Thanks, Julian -- Julian Mariano Burgos Hafrannsóknastofnunin/Marine Research Institute Skúlagata 4, 121 Reykjavík, Iceland Sími/Telephone : +354-5752037 Bréfsími/Telefax: +354-5752001 Netfang/Email: jul...@hafro.is, jmbur...@uw.edu
[O] Inline images export to HTML generates lt; and gt; rather than and
Dear all, Another fanatical Org-mode convert new to the list. Following the 'advice' of [1] I am attempting to generate my personal website using Org publishing, but I'm running up against a pretty weird bug when I try to export inline images. The code gets rendered so that the HTML appears in the browser literally; hitting view-source, instead of img src=img/avi.gif alt=img/avi.gif / Org seems to be outputting lt;img src=img/avi.gif alt=img/avi.gif /gt; which obviously doesn't appear as an image. The code in the org file is just [[file:img/avi.gif]]. Any idea why this might be? Publishing configuration follows.[2] Excited about what I can do with Org publishing; thanks in advance for any assistance. S [1] http://mph.puddingbowl.org/2010/02/org-mode-in-your-pocket-is-a-gnu-shaped-devil/ [2] From my Org init file. Sitemap is published seperately so that I can apply body-only so that it can be included with SSI. This works very well. === (require 'org-publish) (setq org-publish-project-alist '( (org-notes :base-directory ~/tmp/org-html-export/ :base-extension org :publishing-directory /srv/http/v7g :recursive t :publishing-function org-publish-org-to-html :headline-levels 4 ; Just the default for this project. ; :auto-preamble t :auto-sitemap t; Generate sitemap.org automagically... :sitemap-filename sitemap.org ; ... call it sitemap.org (it's the default)... :sitemap-title Sitemap ; ... with title 'Sitemap'. :sitemap-style 'tree :sitemap-sort-folders 'last :style base href=\/v7g/\ target=\_top\ / link rel=\stylesheet\ type=\text/css\ href=\/v7g/inc/v7.css\ media=\screen\ / link rel=\stylesheet\ type=\text/css\ href=\/v7g/inc/cols.css\ / script type=\text/javascript\ src=\/v7g/inc/css3-multi-column.js\/script :style-include-default nil :exclude sitemap.org :html-preamble !--#include virtual=\/v7g/inc/head.inc\ -- h1%t/h1 :html-postamble /div !--#include virtual=\/v7g/inc/foot1.inc\ -- !--#include virtual=\/v7g/inc/sitemap.shtml\ -- !--#include virtual=\/v7g/inc/foot2.inc\ -- %c !--#include virtual=\/v7g/inc/foot3.inc\ -- div :html-extension shtml ) (org-static :base-directory ~/tmp/org-html-export/ :base-extension css\\|js\\|png\\|jpg\\|gif\\|pdf\\|mp3\\|ogg\\|swf\\|inc\\| :publishing-directory /srv/http/v7g :recursive t :publishing-function org-publish-attachment ) (org :components (org-notes org-static org-sitemap)) (org-sitemap :base-directory ~/tmp/org-html-export/ :base-extension org :publishing-directory /srv/http/v7g/inc :publishing-function org-publish-org-to-html :body-only t :html-extension shtml ) )) === -- Sean Whitton / s...@silentflame.com OpenPGP KeyID: 0x3B6D411B http://seanwhitton.com/ pgppUly5jRDIF.pgp Description: PGP signature
[O] Re: agenda view opening multiple buffers
Julian Burgos jmbur...@uw.edu writes: Dear list, When asking for an agenda view (C-c a), org mode opens all files in the agenda list in individual buffers. I keep lots of files in my list (one per project), so having all those buffers open each time I visit my agenda is pretty annoying. Is there a way to make org mode not open each file in a buffer (or close the buffers after reading the file) when asking for an agenda view? Thanks, Julian Hi Julian, I think 'e' in the agenda is supposed to exit the agenda and close automatically opened agenda files. HTH, -- Bernt
[O] Re: Inline images export to HTML generates lt; and gt; rather than and
Sean Whitton s...@silentflame.com writes: Another fanatical Org-mode convert new to the list. Following the 'advice' of [1] I am attempting to generate my personal website using Org publishing, but I'm running up against a pretty weird bug when I try to export inline images. The code gets rendered so that the HTML appears in the browser literally; hitting view-source, instead of img src=img/avi.gif alt=img/avi.gif / Org seems to be outputting lt;img src=img/avi.gif alt=img/avi.gif /gt; which obviously doesn't appear as an image. The code in the org file is just [[file:img/avi.gif]]. Any idea why this might be? Publishing configuration follows.[2] Excited about what I can do with Org publishing; thanks in advance for any assistance. S [1] http://mph.puddingbowl.org/2010/02/org-mode-in-your-pocket-is-a-gnu-shaped-devil/ [2] From my Org init file. Sitemap is published seperately so that I can apply body-only so that it can be included with SSI. This works very well. Hi Sean, Welcome to the list! This works for me. I think there was a bug like this in a recent release. What version of org-mode are you using? Mine exports as follows --8---cut here---start-8--- * Test export [[file:img/avi.gif]] --8---cut here---end---8--- --8---cut here---start-8--- ... pimg src=img/avi.gif alt=img/avi.gif / /p ... --8---cut here---end---8--- Maybe try upgrading to the latest development snapshot of org? I'm using Org-mode version 7.5 (release_7.5.115.g00134) Regards, -- Bernt
Re: [O] Re: agenda view opening multiple buffers
On 27 Mar 2011, Bernt Hansen wrote: Julian Burgos jmbur...@uw.edu writes: Dear list, When asking for an agenda view (C-c a), org mode opens all files in the agenda list in individual buffers. I keep lots of files in my list (one per project), so having all those buffers open each time I visit my agenda is pretty annoying. Is there a way to make org mode not open each file in a buffer (or close the buffers after reading the file) when asking for an agenda view? Thanks, Julian Hi Julian, I think 'e' in the agenda is supposed to exit the agenda and close automatically opened agenda files. It's `x'. But I think Julian meant that the buffers should be closed automatically and not open at least as long as the agenda is shown. For the original issue I think the following would help: #+begin_src emacs-lisp (defun project-agenda (optional args keys restriction) (interactive) (let ((org-agenda-files '(~/project-file1 ~/project-file2))) (org-agenda args keys restriction))) #+end_src Or pressing `' in the prompt buffer, for more see (describe-function 'org-agenda) Michael pgpEgogOCsH62.pgp Description: PGP signature
Re: [O] Re: agenda view opening multiple buffers
Thanks. Using x is good enough for now. I´ll explore also Michael´s suggestions. It would be good to have the agenda open in a buffer without having all the agenda files opened too. On Sun, Mar 27, 2011 at 2:21 PM, Michael Markert markert.mich...@googlemail.com wrote: On 27 Mar 2011, Bernt Hansen wrote: Julian Burgos jmbur...@uw.edu writes: Dear list, When asking for an agenda view (C-c a), org mode opens all files in the agenda list in individual buffers. I keep lots of files in my list (one per project), so having all those buffers open each time I visit my agenda is pretty annoying. Is there a way to make org mode not open each file in a buffer (or close the buffers after reading the file) when asking for an agenda view? Thanks, Julian Hi Julian, I think 'e' in the agenda is supposed to exit the agenda and close automatically opened agenda files. It's `x'. But I think Julian meant that the buffers should be closed automatically and not open at least as long as the agenda is shown. For the original issue I think the following would help: #+begin_src emacs-lisp (defun project-agenda (optional args keys restriction) (interactive) (let ((org-agenda-files '(~/project-file1 ~/project-file2))) (org-agenda args keys restriction))) #+end_src Or pressing `' in the prompt buffer, for more see (describe-function 'org-agenda) Michael -- Julian Mariano Burgos Hafrannsóknastofnunin/Marine Research Institute Skúlagata 4, 121 Reykjavík, Iceland Sími/Telephone : +354-5752037 Bréfsími/Telefax: +354-5752001 Netfang/Email: jul...@hafro.is, jmbur...@uw.edu
[O] Continuation of main section text after subsections ?
Hi, When I'm using orgmode to write out largish documents, I often run into the outlining problem that it's apparently not possible to continue text of a higher level outline once subsections have been started. A simplified example of such an outline would be: --- * Main headline Some thoughts expressed here ** Subheading 1 More thoughts expressed here ** Subheading 2 More thoughts expressed here I would like to have this text part of 'Main headline', not of 'Subheading 2' I've looked for documentation or customization options on this, but haven't found any yet. What I have done so far is turn the subheadings into lists or surround them by *bold markers*, which helps a little. The current outlining interrupts my flow of writing too often; it's getting a nuisance. What are my options, if any, to get the outline behaviour as above? 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
[O] Re: Continuation of main section text after subsections ?
--- * Main headline Some thoughts expressed here ** Subheading 1 More thoughts expressed here ** Subheading 2 More thoughts expressed here I would like to have this text part of 'Main headline', not of 'Subheading 2' Why is copy pasting not an option ... My intention is not to tick you off but I am confused about what you are trying to say here. Jambunathan K.
Re: [O] Re: Continuation of main section text after subsections ?
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 What you can do is something like the following: * Main headline Something goes here #+BEGIN_NOTE sub thoughts #+END_NOTE Some more stuff under main headline The #stuff can be closed when you want it to get it out of the way, so I sometimes use this a means of attaching notes to a document. It works, but I'm sure it could be improved. That way you can also have different exporting options for the note if you really want them. On Sun, Mar 27, 2011 at 4:37 PM, Jambunathan K kjambunat...@gmail.com wrote: --- * Main headline Some thoughts expressed here ** Subheading 1 More thoughts expressed here ** Subheading 2 More thoughts expressed here I would like to have this text part of 'Main headline', not of 'Subheading 2' Why is copy pasting not an option ... My intention is not to tick you off but I am confused about what you are trying to say here. Jambunathan K.
Re: [O] Re: Continuation of main section text after subsections ?
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
Re: [O] Escaping to insert comments in exported text
Aloha Suvayu,
I'd be inclined to use #+LaTeX: %text
Alternatively (and perhaps more robustly with multiline comments) you
could make certain to \usepackage{verbatim} and then use
#+BEGIN_COMMENT
text
#+END_COMMENT
following the example of block level markup here:
http://orgmode.org/worg/org-tutorials/org-latex-export.html#sec-10_2
hth,
Tom
On Mar 27, 2011, at 12:48 AM, Suvayu Ali wrote:
Hi Orgers,
I wanted to insert comments in the exported tex file for latex export.
Is there an standard way to do that? I found normal '%text' gets
exported as '\%text'. However I can export comments by putting
'%%text', it gets exported as '%\%text'.
Is there any other solutions out there?
--
Suvayu
Open source is the future. It sets us free.
Re: [O] Re: Continuation of main section text after subsections ?
Marcel van der Boom mar...@hsdev.com wrote: 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? I'm sure that patches would be welcome, but I think you'd find it difficult to specify, let alone implement. In particular, how do you tell where the section 1.1.1 stuff ends and the section 1 stuff begins again? And would the extra stuff be part of section 1 or (sub)section 1.1? Why? And don't forget this is all just text, so any markup has to be minimal, intuitive and as unobtrusive as possible. The devil is in the details. Nick
Re: [O] Re: Continuation of main section text after subsections ?
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/
Re: [O] Re: Continuation of main section text after subsections ?
On Mar 27, 2011, at 6:45 AM, Nick Dokos wrote: Marcel van der Boom mar...@hsdev.com wrote: 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? I'm sure that patches would be welcome, but I think you'd find it difficult to specify, let alone implement. In particular, how do you tell where the section 1.1.1 stuff ends and the section 1 stuff begins again? And would the extra stuff be part of section 1 or (sub)section 1.1? Why? And don't forget this is all just text, so any markup has to be minimal, intuitive and as unobtrusive as possible. The devil is in the details. Nick I don't think the limitation is Org-mode's. Marcel's structure simply deviates from proper outline structure. His situation is typically handled in linear text with footnotes, and in non-linear text with links, both of which Org-mode implements without issue. Tom
[O] Re: Continuation of main section text after subsections ?
Marcel wrote: When I'm using orgmode to write out largish documents, I often run into the outlining problem that it's apparently not possible to continue text of a higher level outline once subsections have been started. Here's a not-so-pretty hack to get what (I guess) you want * Main headline ** Main headline contents Some thoughts expressed here *** Subheading 1 More thoughts expressed here *** Subheading 2 More thoughts expressed here ** main headline contents1 Not exactly part of Main headline but of Main headline contentsi for some i -- The idea basically is to split your heading into a heading proper and a (series of) contents headlines. The actual subheadings go 1 level deeper than your original (logical?) intention. You could of course in principle apply the same principle recursively to the (original) sub headlines though in practice I guess you would only need do that to the large sections.
[O] Re: Continuation of main section text after subsections ?
Marcel van der Boom mar...@hsdev.com writes: 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, I think this is not yet easily possible in org-mode due to the limitations of org's rather simple concept of markup. Because org tries to stay out of the way of the user's choice of indentation flow, for example, whitespace can't be used to indicate that your text has returned to the top level after entering a subheading. And unlike in, e.g., HTML or LaTeX, there's no way of closing the subheading environment explicitly. As Cian suggests, some alternatives you can use are to employ drawers or environments such as #+BEGIN_NOTE. I also use Org as a drafting tool, mostly for documents that will end up as papers or legal documents rendered with LaTeX. There are a few ambiguities in the markup that are hard to resolve without going the additional step of exporting to HTML or LaTeX and editing that output. You've just stumbled into one of them... I'd support some kind of fix, but it'd be moderately to very involved and far beyond my level of comfort with Elisp. I also agree that it'd be hard to specify. -- William Gardella J.D. Candidate Class of 2011, University of Pittsburgh School of Law
[O] Re: Continuation of main section text after subsections ?
Hello, Filippo A. Salustri salus...@ryerson.ca writes: 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. What about using C-c C-* on the list? Regards, -- Nicolas
Re: [O] Re: Continuation of main section text after subsections ?
It seems to me we're getting into some real design territory here, in that it comes down to a question of a proper outline. I agree that a proper outline is such that Marcel's format is improper. I agree that org follows the proper outline, was designed to suit it, and therefore it isn't surprising that it's not trivially easy to support Marcel's format too. I would humbly suggest that the real question is a design / use case question. Is it reasonable to expect authors to stick to proper outline format throughout their drafting process? If it is, then org is fine as is. If it isn't, then there's a problem. /How/ it's implemented, or worked around, as the case may be, is, imho, irrelevant in the long term (tho certainly useful in the short). Cheers. Fil On 27 March 2011 13:02, William Gardella gardell...@gmail.com wrote: Marcel van der Boom mar...@hsdev.com writes: 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, I think this is not yet easily possible in org-mode due to the limitations of org's rather simple concept of markup. Because org tries to stay out of the way of the user's choice of indentation flow, for example, whitespace can't be used to indicate that your text has returned to the top level after entering a subheading. And unlike in, e.g., HTML or LaTeX, there's no way of closing the subheading environment explicitly. As Cian suggests, some alternatives you can use are to employ drawers or environments such as #+BEGIN_NOTE. I also use Org as a drafting tool, mostly for documents that will end up as papers or legal documents rendered with LaTeX. There are a few ambiguities in the markup that are hard to resolve without going the additional step of exporting to HTML or LaTeX and editing that output. You've just stumbled into one of them... I'd support some kind of fix, but it'd be moderately to very involved and far beyond my level of comfort with Elisp. I also agree that it'd be hard to specify. -- William Gardella J.D. Candidate Class of 2011, University of Pittsburgh School of Law -- 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/
[O] Re: Continuation of main section text after subsections ?
Yes, of course. But it's still something *I* have to do as a separate task. This breaks my cognitive workflow; it's a distraction. One of the reasons I use org is that it's so distraction-free compared to every other tool I've tried. It seems like distraction-freeness is a big deal in org, so I would have thought that every bit of distraction is a distraction too many. Cheers. Fil On 27 March 2011 13:08, Nicolas n.goaz...@gmail.com wrote: Hello, Filippo A. Salustri salus...@ryerson.ca writes: 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. What about using C-c C-* on the list? Regards, -- Nicolas -- 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/
[O] Re: Continuation of main section text after subsections ?
Filippo A. Salustri salus...@ryerson.ca writes:
It seems to me we're getting into some real design territory here, in
that it comes down to a question of a proper outline.
I agree that a proper outline is such that Marcel's format is improper.
I agree that org follows the proper outline, was designed to suit it,
and therefore it isn't surprising that it's not trivially easy to
support Marcel's format too.
I would humbly suggest that the real question is a design / use case
question. Is it reasonable to expect authors to stick to proper
outline format throughout their drafting process? If it is, then org
is fine as is. If it isn't, then there's a problem.
/How/ it's implemented, or worked around, as the case may be, is,
imho, irrelevant in the long term (tho certainly useful in the short).
Cheers.
Fil
I think org-mode should aim to be flexible enough to accomodate all
writers, writing tasks, and writing styles. Maybe for this particular
issue it would be enough to give org-mode an explicit way to close a
heading--an Org-wide equivalent to \end{section} in LaTeX, say. Of
course it would have to be as pithy and unobtrusive as the rest of
org-mode syntax...I'm sure it's possible (because with Elisp practically
everything is possible), but out of my depth. :)
--
William Gardella
J.D. Candidate
Class of 2011, University of Pittsburgh School of Law
Re: [O] Re: Continuation of main section text after subsections ?
Out of my depth too. That's why I'd be happy to live with it as is. :)
Cheers.
Fil
On 27 March 2011 13:18, William Gardella gardell...@gmail.com wrote:
Filippo A. Salustri salus...@ryerson.ca writes:
It seems to me we're getting into some real design territory here, in
that it comes down to a question of a proper outline.
I agree that a proper outline is such that Marcel's format is improper.
I agree that org follows the proper outline, was designed to suit it,
and therefore it isn't surprising that it's not trivially easy to
support Marcel's format too.
I would humbly suggest that the real question is a design / use case
question. Is it reasonable to expect authors to stick to proper
outline format throughout their drafting process? If it is, then org
is fine as is. If it isn't, then there's a problem.
/How/ it's implemented, or worked around, as the case may be, is,
imho, irrelevant in the long term (tho certainly useful in the short).
Cheers.
Fil
I think org-mode should aim to be flexible enough to accomodate all
writers, writing tasks, and writing styles. Maybe for this particular
issue it would be enough to give org-mode an explicit way to close a
heading--an Org-wide equivalent to \end{section} in LaTeX, say. Of
course it would have to be as pithy and unobtrusive as the rest of
org-mode syntax...I'm sure it's possible (because with Elisp practically
everything is possible), but out of my depth. :)
--
William Gardella
J.D. Candidate
Class of 2011, University of Pittsburgh School of Law
--
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/
Re: [O] Re: Continuation of main section text after subsections ?
Hullo, On Sun, Mar 27, 2011 at 22:32, William Gardella gardell...@gmail.com wrote: Marcel van der Boom mar...@hsdev.com writes: 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, I think this is not yet easily possible in org-mode due to the limitations of org's rather simple concept of markup. Because org tries to stay out of the way of the user's choice of indentation flow, for example, whitespace can't be used to indicate that your text has returned to the top level after entering a subheading. And unlike in, e.g., HTML or LaTeX, there's no way of closing the subheading environment explicitly. As Cian suggests, some alternatives you can use are to employ drawers or environments such as #+BEGIN_NOTE. I also use Org as a drafting tool, mostly for documents that will end up as papers or legal documents rendered with LaTeX. There are a few ambiguities in the markup that are hard to resolve without going the additional step of exporting to HTML or LaTeX and editing that output. You've just stumbled into one of them... Out of curiosity, how would you return to an enclosing context in LaTeX or DocBook? In HTML, of course, you can nest ‘div’ elements (or proper ‘section’ elements in HTML5) and alternate subsections and text to your heart’s content. As far as I know, there is no equivalent in the other two formats: you need to use other containers within the section, such as lists or tables. Aankhen
Re: [O] Re: agenda view opening multiple buffers
On Sun, Mar 27, 2011 at 8:21 PM, Julian Burgos wrote: Thanks. Using x is good enough for now. I´ll explore also Michael´s suggestions. It would be good to have the agenda open in a buffer without having all the agenda files opened too. Following code should do what you want (I think). #+begin_src emacs-lisp ;; function code copied from definition of org-agenda-exit (add-hook 'org-finalize-agenda-hook (lambda () (interactive) (org-release-buffers org-agenda-new-buffers) (setq org-agenda-new-buffers nil))) #+end_src HTH -- Manish On Sun, Mar 27, 2011 at 2:21 PM, Michael Markert markert.mich...@googlemail.com wrote: On 27 Mar 2011, Bernt Hansen wrote: Julian Burgos jmbur...@uw.edu writes: Dear list, When asking for an agenda view (C-c a), org mode opens all files in the agenda list in individual buffers. I keep lots of files in my list (one per project), so having all those buffers open each time I visit my agenda is pretty annoying. Is there a way to make org mode not open each file in a buffer (or close the buffers after reading the file) when asking for an agenda view? Thanks, Julian Hi Julian, I think 'e' in the agenda is supposed to exit the agenda and close automatically opened agenda files. It's `x'. But I think Julian meant that the buffers should be closed automatically and not open at least as long as the agenda is shown. For the original issue I think the following would help: #+begin_src emacs-lisp (defun project-agenda (optional args keys restriction) (interactive) (let ((org-agenda-files '(~/project-file1 ~/project-file2))) (org-agenda args keys restriction))) #+end_src Or pressing `' in the prompt buffer, for more see (describe-function 'org-agenda) Michael -- Julian Mariano Burgos Hafrannsóknastofnunin/Marine Research Institute Skúlagata 4, 121 ReykjavÃk, Iceland SÃmi/Telephone : +354-5752037 BréfsÃmi/Telefax: +354-5752001 Netfang/Email: jul...@hafro.is, jmbur...@uw.edu
Re: [O] Re: Continuation of main section text after subsections ?
IIUC the goal is to allow continuing body text. Is this for org itself or for export? Or both? I wonder if inline tasks can be used to achieve some of this. Samuel -- The Kafka Pandemic: http://thekafkapandemic.blogspot.com/2010/12/welcome-to-kafka-pandemic-two-forces_9182.html I support the Whittemore-Peterson Institute (WPI) === I want to see the original (pre-hold) Lo et al. 2010 NIH/FDA/Harvard MRV paper.
[O] ASCII table export should use tabs?
I wonder if org should export ASCII tables using tabs. If I send to this list, I can be confident that everybody will know to display in a monospace font. That is not true for non-technical audiences. Yet I think there are times when I want to send ASCII instead of HTML. At least, I am not confident that /I/ know that HTML will display correctly. Tabs are not a perfect solution, as they will break with long entries. Still, you can read a broken table with tabs easier than a table displayed in a proportional font, which I believe most nontechnical people use. What do you think? Samuel -- The Kafka Pandemic: http://thekafkapandemic.blogspot.com/2010/12/welcome-to-kafka-pandemic-two-forces_9182.html I support the Whittemore-Peterson Institute (WPI) === I want to see the original (pre-hold) Lo et al. 2010 NIH/FDA/Harvard MRV paper.
[O] Re: [Orgmode] Re: Automatic noexport tag based on rules?
That is indeed an excellent solution if you want to add a tag for a todo kw. However, I wonder if there is a direct approach, where the exporter simply does not export if it is a certain todo kw. Is the solution to have the exporter delete anything with that todo kw? Or is there a way to have it skip? One advantage of this approach is that there might be a lot of contexts in which you don't need the noexport tag.
[O] Re: [Orgmode] Re: Context-sensitive word count in org mode (elisp)
If I could I would refactor org-clock-put-overlay into a function that puts overlays on the current headline but I am not able to do so.
Re: [O] Re: Continuation of main section text after subsections ?
Wouldn't blocks that allowed org headings offer this. If I understand this correctly, what you're really looking for is the ability to mark certain bits of text as one blob, so that you can move them around easily as you draft a paper, without worrying about pulling other bits of the paper. So this would work: * First level blah blah ** Second level #+BEGIN_block some text * Third level because all headings within the block are treated as subheadings of the containing level ** Fourth level This is some rubbish that I'm not sure about #+END_BLOCK This is different rubbish that will stay here if I cut the block above me Would something along those lines serve? On Sun, Mar 27, 2011 at 5:11 PM, 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
Re: [O] Escaping to insert comments in exported text
Hi Tom,
On Sun, 27 Mar 2011 06:36:18 -1000
Thomas S. Dye t...@tsdye.com wrote:
Aloha Suvayu,
I'd be inclined to use #+LaTeX: %text
Alternatively (and perhaps more robustly with multiline comments)
you could make certain to \usepackage{verbatim} and then use
#+BEGIN_COMMENT
text
#+END_COMMENT
following the example of block level markup here:
http://orgmode.org/worg/org-tutorials/org-latex-export.html#sec-10_2
Both of those are much cleaner solutions! Thanks a lot. :)
hth,
Tom
On Mar 27, 2011, at 12:48 AM, Suvayu Ali wrote:
Hi Orgers,
I wanted to insert comments in the exported tex file for latex
export. Is there an standard way to do that? I found normal '%text'
gets exported as '\%text'. However I can export comments by putting
'%%text', it gets exported as '%\%text'.
Is there any other solutions out there?
--
Suvayu
Open source is the future. It sets us free.
--
Suvayu
Open source is the future. It sets us free.
[O] Re: [Orgmode] Re: Automatic noexport tag based on rules?
On Sun, Mar 27, 2011 at 2:37 PM, Samuel Wales samolog...@gmail.com wrote: That is indeed an excellent solution if you want to add a tag for a todo kw. However, I wonder if there is a direct approach, where the exporter simply does not export if it is a certain todo kw. Is the solution to have the exporter delete anything with that todo kw? Or is there a way to have it skip? I think that was Carsten's suggestion a bit back, but I'm not sure. I think I asked if it was just deleting as it channeled through the export function but didn't get a response. Looking back, though, I'm sure that's what it was and my question was probably a bit silly :) And yes, I have turned this off as I find adding :noexport: to ever todo in addition to whatever tags I already use to ID the project/task is annoying and ugly. I've toyed with simply having a * Tracking headline at the beginning of each file where I dump todos via capture and track time and then having that have a top level noexport tag to take care of things. That's pretty much nice, but I still like todos created during meeting minutes or in the context of some other project notes to stay where they make sense rather than separating them from their location and putting them elsewhere. So I've got some solutions but am not quite happy yet. I should re-visit Carsten's solution to strip it on export. That would probably be the ticket. I happen to hate how inline tasks look. That's just me, though! One advantage of this approach is that there might be a lot of contexts in which you don't need the noexport tag. John
[O] Re: Continuation of main section text after subsections ?
William Gardella gardell...@gmail.com writes:
I think org-mode should aim to be flexible enough to accomodate all
writers, writing tasks, and writing styles.
With flexibility comes complexity, which runs counter to org should be
simple.
Maybe for this particular issue it would be enough to give org-mode
an explicit way to close a heading--an Org-wide equivalent to
\end{section} in LaTeX, say.
There already is: you simply start a new section for each thought,
preferrably wih no whitespace after the heading so it becomes a visual
unit that just folds away when outlined. I've been doing that with
Outline Mode and AuCTeX and it is actually much easier to do in orgmode.
Once you get your thoughts into the proper order by sorting the
headlines, you can then insert, remove, edit, de- and promote the
headings to finalize the document into something more readable. In my
experience, there rarely is a need to change the first level structure.
However, if you are organizing the structure of your document while the
content is still largely absent, then (as has already been suggested) it
is easier in orgmode to do that in a list. List items can be converted
into headings and vice versa quite easily.
Regards,
Achim.
--
+[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]+
Waldorf MIDI Implementation additional documentation:
http://Synth.Stromeko.net/Downloads.html#WaldorfDocs
Re: [O] Re: Comma-protection of Org blocks
Achim Gratz strom...@nexgo.de wrote: The question really is if org hasn't evolved to the point where it needs a more general quoting/escaping mechanism. This might be one of the things to ponder during the upcoming exporter cleanup, but goes a bit beyond just exporting. Absolutely right - org has grown organically (if you'll pardon the pun): it has developed different quoting mechanisms for different aspects of it, and they don't always work correctly, even in their restricted domain (braces in the LaTeX exporter cause trouble often e.g.). It would be great if a more general quoting mechanism could be incorporated into the formal description of org. That could then be used to reimplement these mechanisms. But I suspect it would be a big job and backward compatibility would also be a big problem. Nick
[O] Re: Continuation of main section text after subsections ?
Achim Gratz strom...@nexgo.de writes:
William Gardella gardell...@gmail.com writes:
I think org-mode should aim to be flexible enough to accomodate all
writers, writing tasks, and writing styles.
With flexibility comes complexity, which runs counter to org should be
simple.
Agreed, but I'd say org is already one of the most complex projects in
Emacs. Its *apparent* simplicity for new victims--er, users--is a
feature worth keeping, of course. :)
Maybe for this particular issue it would be enough to give org-mode
an explicit way to close a heading--an Org-wide equivalent to
\end{section} in LaTeX, say.
There already is: you simply start a new section for each thought,
preferrably wih no whitespace after the heading so it becomes a visual
unit that just folds away when outlined. I've been doing that with
Outline Mode and AuCTeX and it is actually much easier to do in orgmode.
Once you get your thoughts into the proper order by sorting the
headlines, you can then insert, remove, edit, de- and promote the
headings to finalize the document into something more readable. In my
experience, there rarely is a need to change the first level structure.
However, if you are organizing the structure of your document while the
content is still largely absent, then (as has already been suggested) it
is easier in orgmode to do that in a list. List items can be converted
into headings and vice versa quite easily.
Regards,
Achim.
I use a workflow similar to this, using subheadings to allow for easier
reordering of paragraphs/thoughts. I guess it's good to keep in mind
that using Org as a word processor (rather like using Gnus as a
mailclient) requires some rethinking and reevaluation of how one might
otherwise do things. And maybe a change in approach is a better idea
when a technical fix might make org's markup or parser unnecessarily
complex.
--
William Gardella
J.D. Candidate
Class of 2011, University of Pittsburgh School of Law
[O] Re: Continuation of main section text after subsections ?
Marcel van der Boom mar...@hsdev.com writes: 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, I think this is not yet easily possible in org-mode due to the limitations of org's rather simple concept of markup. Because org tries to stay out of the way of the user's choice of indentation flow, for example, whitespace can't be used to indicate that your text has returned to the top level after entering a subheading. And unlike in, e.g., HTML or LaTeX, there's no way of closing the subheading environment explicitly. As Cian suggests, some alternatives you can use are to employ drawers or environments such as #+BEGIN_NOTE. I also use Org as a drafting tool, mostly for documents that will end up as papers or legal documents rendered with LaTeX. There are a few ambiguities in the markup that are hard to resolve without going the additional step of exporting to HTML or LaTeX and editing that output. You've just stumbled into one of them... -- William Gardella J.D. Candidate Class of 2011, University of Pittsburgh School of Law
Re: [O] Re: Comma-protection of Org blocks
I agree that this is important. For new features, Extensible Syntax (capitalized because it is a specific proposal for a concrete universal syntax) allows you to use the same quoting, escaping, nesting, exporting, etc. solutions that were arrived at as a one-time fundamental mechanism. This reduces the risk of adding quoting, escaping, nesting, exporting, etc. issues when you add new features to (asymptotically at least -- it needs writing) zero. I only mention it again to point out that Extensible Syntax was motivated by reducing parsing risk, including the issues discussed in this thread. Samuel -- The Kafka Pandemic: http://thekafkapandemic.blogspot.com/2010/12/welcome-to-kafka-pandemic-two-forces_9182.html I support the Whittemore-Peterson Institute (WPI) === I want to see the original (pre-hold) Lo et al. 2010 NIH/FDA/Harvard MRV paper.
[O] FAQ? (was: Continuation of main section text after subsections ?)
Marcel van der Boom mar...@hsdev.com writes: [...] I've looked for documentation or customization options on this, but haven't found any yet. What I have done so far is turn the subheadings into lists or surround them by *bold markers*, which helps a little. Seems to me to be worth an entry in the FAQ, isn't it? Memnon
[O] Continuation of main section text after subsections
Perhaps we could have a tag like :noexport: except that it exports body. It does not export the header. Optionally, it would be replaced with a blank line. Then he can put headers anywhere he wants. Would this work for the OP's use case?
Re: [O] Continuation of main section text after subsections
I'm not certain, but I don't think it's possible to solve the OP's problem in LaTeX. Tom On Mar 27, 2011, at 3:07 PM, Samuel Wales wrote: Perhaps we could have a tag like :noexport: except that it exports body. It does not export the header. Optionally, it would be replaced with a blank line. Then he can put headers anywhere he wants. Would this work for the OP's use case?
