From: Kyle Meyer <kyle@kyleam.com>
To: Chris Patti <cpatti@gmail.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: Valid use cases for lists?
Date: Wed, 19 Aug 2015 16:00:56 -0400 [thread overview]
Message-ID: <87vbcbgi9z.fsf@kyleam.com> (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?
I think there are quite a few, but here's one example. I keep a heading
with a list of links to potentially interesting articles that I don't
have time to process at the moment when I encounter them. I capture new
links (with no description) as items under this heading. I don't want
to use a separate heading for each link because I don't want to think
about a name to give the heading. I just want a list of links where I
can check off items when I get around to visiting them.
> 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.
That is pretty much how I decide. If I think I need heading-specific
features, I use headings.
--
Kyle
next prev parent reply other threads:[~2015-08-19 20:01 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 [this message]
2015-08-19 21:02 ` Florian Beck
2015-08-20 14:06 ` Matt Lundin
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=87vbcbgi9z.fsf@kyleam.com \
--to=kyle@kyleam.com \
--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).