emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Mirko Vukovic <mirko.vukovic@gmail.com>
To: suvayu ali <fatkasuvayu+linux@gmail.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: suggestion for the manual: mention the "#+BEGIN_SRC org" trick when describing drawers and plainlists
Date: Sat, 10 Mar 2012 14:47:03 -0500	[thread overview]
Message-ID: <CAO73BAA93wydtGtZSY6QnsbLeyZhyE3RPDJXYQF8QBNbWxNy-g@mail.gmail.com> (raw)
In-Reply-To: <CAMXnza1ryo0dxshaqXh4FNCN4-w98kpVp1kAcsf6Vy170rVFeQ@mail.gmail.com>

On Sat, Mar 10, 2012 at 2:00 PM, suvayu ali <fatkasuvayu+linux@gmail.com> wrote:
> On Sat, Mar 10, 2012 at 16:01, Mirko Vukovic <mirko.vukovic@gmail.com> wrote:
>> But using BEGIN/END_SRC is really a hack.  I wonder if instead of using SRC
>> blocks, we could define (with some amount of coding) a more suitable kind of
>> blocks.  In my case I would like to have a BEGIN/END_TODO block.  This would
>> permit a layout such as
>
> We have inline tasks for that.
>
> About supporting non-tree-like structures in org files, this has been
> discussed before. You can look up sometime towards the end of last
> year in the archives to see the arguments in favour and against the
> feature.
>
> --
> Suvayu

Thank you.  I was not aware of the inline tasks capability

Mirko

      reply	other threads:[~2012-03-10 19:47 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-03-08  1:13 suggestion for the manual: mention the "#+BEGIN_SRC org" trick when describing drawers and plainlists Ilya Shlyakhter
2012-03-08  1:58 ` Ilya Shlyakhter
2012-03-08 13:14   ` Eric Schulte
2012-03-08  7:32 ` Sebastien Vauban
2012-03-08 12:53   ` Ilya Shlyakhter
2012-03-08 12:59     ` Ilya Shlyakhter
2012-03-10 15:01 ` Mirko Vukovic
2012-03-10 19:00   ` suvayu ali
2012-03-10 19:47     ` Mirko Vukovic [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://www.orgmode.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=CAO73BAA93wydtGtZSY6QnsbLeyZhyE3RPDJXYQF8QBNbWxNy-g@mail.gmail.com \
    --to=mirko.vukovic@gmail.com \
    --cc=emacs-orgmode@gnu.org \
    --cc=fatkasuvayu+linux@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).