From: Matt Lundin <mdl@imapmail.org>
To: Chris Patti <cpatti@gmail.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: Valid use cases for lists?
Date: Thu, 20 Aug 2015 09:06:05 -0500 [thread overview]
Message-ID: <87y4h6njg2.fsf@fastmail.fm> (raw)
In-Reply-To: <CAJ8P3RB4q9bUjihya-7f_447gX27LH_vZ+4t1TPbEKZxgsR_3A@mail.gmail.com> (Chris Patti's message of "Wed, 19 Aug 2015 15:32:22 -0400")
Chris Patti <cpatti@gmail.com> writes:
> Can anyone give me an example of when it's a good idea to use lists
> rather than headlines?
>
> They feel rather like a violation of the principle of least surprise
> to me, because when you use them, and then try to use pretty much any
> other Org feature on them (marking them as a TODO item, tagging, etc.)
> it doesn't work because lists aren't meant to be used that way.
> I'm guessing I'm missing something obvious here, and that's why I'm asking.
Lists are lists. Headlines are headlines. If you need something to show
up in an agenda view, use a headline.
From the perspective of document structure, headlines vs. lists
corresponds with section headings vs. lists in Markdown:
https://en.wikipedia.org/wiki/Markdown#Example
I find lists to be a good means quickly to organize and reorganize items
within an entry. I use them for brainstorming, for making grocery lists,
for itemizing ingredients in recipes, for documenting what I did on a
task, etc.
Though you can't tag them or add todos to them, you can use checkboxes
to track your progress on items in a list.
- http://orgmode.org/manual/Checkboxes.html#Checkboxes
Lists also play an important role in export. E.g., this list...
- apples
- Fuji
- Red Delicious
- bananas
- pears
Exports to html as...
<ul class="org-ul">
<li>apples
<ul class="org-ul">
<li>Fuji</li>
<li>Red Delicious</li>
</ul></li>
<li>bananas</li>
<li>pears</li>
</ul>
Matt
prev parent reply other threads:[~2015-08-20 14:06 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-19 19:32 Valid use cases for lists? Chris Patti
2015-08-19 19:55 ` Rasmus
2015-08-20 15:18 ` Mike McLean
2015-08-21 3:59 ` Peter Salazar
2015-08-21 18:39 ` Rasmus
2015-08-23 17:18 ` Peter Salazar
2015-08-19 20:00 ` Kyle Meyer
2015-08-19 21:02 ` Florian Beck
2015-08-20 14:06 ` Matt Lundin [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=87y4h6njg2.fsf@fastmail.fm \
--to=mdl@imapmail.org \
--cc=cpatti@gmail.com \
--cc=emacs-orgmode@gnu.org \
/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).