emacs-orgmode
[Top][All Lists]

## [Orgmode] Re: org-indent, org-inlinetask: patches on github

 From: Jeff Horn Subject: [Orgmode] Re: org-indent, org-inlinetask: patches on github Date: Sun, 7 Nov 2010 13:25:55 -0500

Yes, thanks a ton Nicholas! I will test these patches this afternoon.

Jeff

On Sun, Nov 7, 2010 at 10:21 AM, Nicolas Goaziou <address@hidden> wrote:
> Hello,
> Hello,
>
> I added them into my repository.
>
> They should fix quite a few bugs:
>
> - indentation with inline tasks (with or without org-indent mode
>  turned on) should be fine ;
> - cycling levels of headings in indent-mode should be fixed ;
> - C-c @ now marks inline task if point is inside the task, or the
>  subtree if point is outside ;
> - exporting inline tasks to latex is repaired.
>
>
> Furthermore, the last patch introduces a template concept in inline
> doc-string:
>
> | This variable is an alist of shape (BACKEND STRING OBJECTS).
> |
> | BACKEND is the name of the backend for the template (ascii, html...).
> |
> | STRING is a format control string.
> |
> | OBJECTS is a list of elements to be substituted into the format
> | string.  They can be of any type, from a string to a form
> | returning a value (thus allowing conditional insertion).  A nil
> | object will be substituted as the empty string.  Obviously, there
> | must be at least as many objects as %-sequences in the format
> | string.
> |
> | Moreover, the following special keywords are defined: todo',
> | priority', heading', content', tags'.  If some of them are not
> | defined in an inline task, their value is the empty string.
> |
> | As an example, valid associations are:
> |
> | (html "<ul><li>%s <p>%s</p></li></ul>" (heading content))
> |
> | or, in a conditional way,
> |
> | (latex "\\begin{flushright}%s%s%s\\end{flushright}"
> |        ((unless (eq todo "") (format "\\textsc{%s%s: }" todo priority))
> |         (unless (eq content "") (format "\n%s" content))))
>
> This should be enough to cover most needs with regards to inline
> tasks. Please note that drawers and scheduled items are not exported,
> and while it would be possible, they weren't exported before, anyway.
>
> Default values are conservative, only ascii export is more exotic (but
> will be changed if someone comes up with a better idea), as I wanted
> to have some fun with that variable.
>
> I didn't make it customizable for two reasons:
> 1. Using this is for real men. Real men don't use customize ! (in fact
>   the second reason is the more problematic ;))
> 2. I don't know how to tell customize to understand such a beast.
>
> Here is the repo:
>
>
> To maintainers:
> - to sum it up, if you don't like the idea of templates, or how it is
>  implemented, all commits but the last one are only fixes.
> - could you delete submissions from 11-04 and 11-06 (but _not_ from
>  10-26) on the patchwork server, as they are now included in the
>  repo?
>
>
> I'm now waiting for comments from the 3-3.5 persons in the world using
>
> Regards,
>
> --
> Nicolas Goaziou
>
> Regards,
>
> -- Nicolas
>

--
Jeffrey Horn
Graduate Lecturer and PhD Student in Economics
George Mason University

(704) 271-4797