From: James Harkins <jamshark70@gmail.com>
To: Emacs-orgmode@gnu.org
Subject: Visibility cycling of plain lists?
Date: Mon, 31 Dec 2012 11:53:38 +0800 [thread overview]
Message-ID: <CAFniQ7Xmm6fWHo2t3wQC4EaC13D5C2tFA7dwtbA+U1Tn+Q1ExQ@mail.gmail.com> (raw)
Is there a way to show the content of a node containing a plain list,
so that the plain list items are collapsed? Or, is there a function
that will automatically collapse all the items in the plain list?
For instance, if I have a tree like this:
* Top level I
** Subheading A
*** Further subheading 1
** Subheading B
* Top-level II
When I first visit the file, I see:
* Top level I...
* Top-level II
... and if I expand the first heading, I see:
* Top level I
** Subheading A...
** Subheading B
* Top-level II
But, if the tree has this structure instead:
* TODO Top level I [0/2]
- [ ] List item A
Comments on list item A
- [ ] List item B
Comments on list item B
* Top-level II
... expanding the first node expands the entire contents, including
the comments -- I see *everything*. It's more useful to me to see the
list items collapsed (comments hidden), and then I can use tab
visibility cycling to see the comments that I want to see.
I'm aware that I could use regular subheadings for these list items.
The problem is that they would all have to be TODOs (because I want
the parent node's progress cookie to update), but I don't need to
track them individually in my agenda views. The top-level here is a
homework assignment, and each list item is work received from one
student. In the agenda, I need to know only that I haven't graded
everything for that assignment yet, but I don't need to see a separate
TODO entry for every student. Lists with checkboxes are perfect for
this.
Also, if I used "real" TODOs, org-mobile-push would assign an org-id
to every one of them, grossly bloating my ~/.emacs.d/.org-id-locations
(and bloating the org file with hundreds of :PROPERTIES: drawers that
I don't really need). So it's really much more efficient for me to use
list items, except that I haven't found a way to use visibility
cycling on them that is as intelligent as it is for outline headings.
Thanks,
hjh
--
James Harkins /// dewdrop world
jamshark70@dewdrop-world.net
http://www.dewdrop-world.net
"Come said the Muse,
Sing me a song no poet has yet chanted,
Sing me the universal." -- Whitman
blog: http://www.dewdrop-world.net/words
audio clips: http://www.dewdrop-world.net/audio
more audio: http://soundcloud.com/dewdrop_world/tracks
next reply other threads:[~2012-12-31 3:53 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-31 3:53 James Harkins [this message]
2012-12-31 4:01 ` Visibility cycling of plain lists? James Harkins
2012-12-31 9:36 ` Bastien
2012-12-31 14:05 ` James Harkins
2012-12-31 14:19 ` Bastien
2013-01-01 2:13 ` James Harkins
2013-01-01 16:10 ` Bastien
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=CAFniQ7Xmm6fWHo2t3wQC4EaC13D5C2tFA7dwtbA+U1Tn+Q1ExQ@mail.gmail.com \
--to=jamshark70@gmail.com \
--cc=Emacs-orgmode@gnu.org \
--cc=jamshark70@dewdrop-world.net \
/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).