On Sat, 09 Oct 2010 19:00:29 +0200, Nicolas Goaziou <n.goaz...@gmail.com> wrote:
> 
> Hello,
> 
> >>>>> Carsten Dominik writes:
> 
> > On Oct 9, 2010, at 12:46 PM, Eric S Fraga wrote:
> 
> >> Footnotes: [1] If I have one niggle to report it is that indenting
> >> text after an in-line todo doesn't seem to work properly: it
> >> indents any subsequent paragraphs much too far, lining up with the
> >> headline text for the in-line todo. This seems conceptually wrong
> >> to me. Not a big deal, mind you.
> 
> > This is clearly a bug. Nicolas, could you be persuaded to have a
> > look at that? You have worked on the indentation code reently in
> > connection with the plain lists.
> 
> I can have a look at it, but I would need an example to work on as I
> never use "inline todo". I don't want to sound too lazy, but could
> Eric provide a minimal example to get me started ?
> 
> Regards,
> 
> -- Nicolas

Gladly.  Attached is a very small example, self-documented!
# -*- mode: org; mode: auto-fill; -*-
#+TITLE:     test.org
#+AUTHOR:    Eric S Fraga
#+EMAIL:     e.fr...@ucl.ac.uk
#+DATE:      2010.10.10 19:00:34
#+LANGUAGE:  en
#+OPTIONS:   H:3 num:t toc:t \n:nil @:t ::t |:t ^:t -:t f:t *:t TeX:t LaTeX:t 
skip:nil d:nil tags:not-in-toc
#+INFOJS_OPT: view:nil toc:nil ltoc:t mouse:underline buttons:0 
path:http://orgmode.org/org-info.js
#+EXPORT_SELECT_TAGS: export
#+EXPORT_EXCUDE_TAGS: noexport
#+LINK_UP:
#+LINK_HOME:
#+DRAWERS: HIDDEN hidden extra details
#+STARTUP: lognotedone lognoteclock-out

#+ STARTUP: indent

* Introduction
The introduction, most obviously introduces
material in an introductory manner.
***************************** TODO Remember to expand this section
***************************** END

                              The following text is indented to line
                              up with the in-line todo heading which
                              it should not be.  The whole point of an
                              in-line todo is that it is not meant to
                              disrupt the flow of the rest of the
                              document.
-- 
Eric S Fraga
GnuPG: 8F5C 279D 3907 E14A 5C29  570D C891 93D8 FFFC F67D
_______________________________________________
Emacs-orgmode mailing list
Please use `Reply All' to send replies to the list.
Emacs-orgmode@gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-orgmode

Reply via email to