emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Carsten Dominik <carsten.dominik@gmail.com>
To: Karl Maihofer <ignoramus@gmx.de>
Cc: emacs-orgmode@gnu.org
Subject: Re: How to use headlines and lists in Org to structure your thoughts?
Date: Sat, 18 Dec 2010 21:00:31 +0100	[thread overview]
Message-ID: <092A9589-5D17-4598-ABBE-B66814C205FD@gmail.com> (raw)
In-Reply-To: <20101214181325.141033ikbnfst1og@webmail.df.eu>


On Dec 14, 2010, at 6:13 PM, Karl Maihofer wrote:

> The ongoing discussion about inline tasks and drawers withhin lists
> much depends on the way you use Org, I think. Perhaps it is a good
> idea to brainstorm some fundamental aspects in regard to headlines and
> lists.
>
> Why and in which situations do we use lists? I use lists a lot to
> write down my thoughts. I think there are mainly two reasons for this:
> - Headlines are exported as headlines, not as list items. ;-)

This is, in fact, not correct.  Headlines beyond a certain
level (3 by default) are exported as lists.  You can change
the level where this change happens in a number of different
ways, see for example:

#+OPTIONS: H:2

- Carsten

> - In Headlines you do not have word wrap. So you always have to phrase
>  a headline and then write your text below this headline. For me it
>  is much easier to use lists and write, write, write... with word
>  wrap.
>
> I think these are the reasons for me to use lists a lot. But if I do
> so, I cannot define tasks in my texts - the core concept of Org. To
> solve this dilemma, I can think of two different approaches:
>
> 1. Make it possible to use inline tasks withhin lists. This is what
>   Nicolas implemented (thanks a lot!!!) and what works very well. But
>   it is not a "nice" concept. We discussed this already and I
>   understand the reasons why Carsten and Nicolas himself have
>   reservations. It it only a workaround.
> 2. Make headlines behave like list items. This means enabling word
>   wrap for headlines and export the headlines as lists. If a headline
>   should be exported as a headline you could use a tag :HEADLINE:. If
>   this would be possible, I cannot see a reason why I should make
>   such extensive use of lists.
>
> What do you think? How do you use lists? Do you think the second
> approach would make sense? Or do I miss something essential?
>
> Regards,
> Karl
>
>
>
> _______________________________________________
> 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

      parent reply	other threads:[~2010-12-18 20:00 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-12-14 17:13 How to use headlines and lists in Org to structure your thoughts? Karl Maihofer
2010-12-14 18:11 ` Jeff Horn
2010-12-14 19:56 ` Alan L Tyree
2010-12-18 17:33   ` Karl Maihofer
2010-12-15 19:42 ` Eric S Fraga
2010-12-18 20:00 ` Carsten Dominik [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=092A9589-5D17-4598-ABBE-B66814C205FD@gmail.com \
    --to=carsten.dominik@gmail.com \
    --cc=emacs-orgmode@gnu.org \
    --cc=ignoramus@gmx.de \
    /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).