From: Mark Edgington <edgimar@gmail.com>
To: emacs-orgmode@gnu.org
Subject: Re: proposal to have ignoreheading tags/properties
Date: Thu, 12 Jun 2014 18:09:39 +0000 (UTC) [thread overview]
Message-ID: <loom.20140612T194320-659@post.gmane.org> (raw)
In-Reply-To: 87k38m5903.fsf@gmail.com
Thorsten Jolitz <tjolitz <at> gmail.com> writes:
>
> In a tree structure, when ignoring the parent node, it seems only
> logical that the siblings are ignored too.
>
> You seem to use the wrong tool for the task (headlines), this looks like
> a perfect use case for TAGS, i.e. define your (concept) groups as
> tags. If these tags are not part of `org-export-exclude-tags' they won't
> affect exporting, but you can still use them to build your agenda or a
> sparse tree or so.
>
Why do you suppose this is the "wrong tool"? It is a quite natural and
sensible tool, because it allows grouping, folding, and nesting collections
of items together. I cannot do that with tags. If you don't like the idea
of having a headline serve this purpose, then perhaps we can invent a new
kind of "pseudo-headline" which behaves in this way. How would you propose
to use tags alone to do something like the following which allows folding
and unfolding the contents, without a lot of extra work? -- for example:
* Chapters about Topic A :pseudo:
** Chapter 1 Title
** Chapter 2 Title
* Chapters about Topic B :pseudo:
** Chapter 3 Title
List of interesting things:
*** items relevant to X :pseudo:
- item 1
- item 2
- item 3
*** items relevant to Y :pseudo:
- item 4
- item 5
Another example would be, say, if you wanted to divide up some kind of
text-file (e.g. source code, or prose), dividing it into groupings that make
sense to you, but not wanting to actually bring these changes into the
document's exported structure. Here's an example of a letter:
* Addresses / date :pseudo:
123 Cherry Lane
City, ST 12345
October 5, 2014
Ms. Jane Doe
Accounts Payable
....
* Greeting :pseudo:
Dear Ms. Johnson:
* Body :pseudo:
It has come to my attention that ......
* Closing :pseudo:
Sincerely,
John Doe
* Postscript :pseudo:
P.S. .....
Perhaps one could make it so that when a headline bullet (sequence) has a
'#' character tacked on after the sequence, it is no longer a headline, but
a "summary node" having the property that it promotes the levels of all its
children. It doesn't much matter to me *how* one makes such a node, but I
think the availability of nodes/headlines like this is important.
In any case, it's not clear that this is "the wrong tool". I would use it,
and for me (and presumably others) it would be the right (kind of) tool.
Furthermore tags are limited by their brevity -- with a pseudo headline I
can describe a concept or category with much more detail / clarity.
next prev parent reply other threads:[~2014-06-12 18:10 UTC|newest]
Thread overview: 49+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-12 16:49 proposal to have ignoreheading tags/properties Mark Edgington
2014-06-12 17:32 ` Thorsten Jolitz
2014-06-12 17:41 ` Ken Mankoff
2014-06-12 18:11 ` Thorsten Jolitz
2014-06-12 18:16 ` Ken Mankoff
2014-06-13 14:32 ` Rasmus
2014-06-13 15:02 ` Thorsten Jolitz
2014-06-12 18:09 ` Mark Edgington [this message]
2014-06-12 18:12 ` Eric Schulte
2014-06-12 18:54 ` Aaron Ecay
2014-06-12 19:21 ` Nicolas Girard
2014-06-12 19:26 ` Ken Mankoff
2014-06-12 19:52 ` Nicolas Girard
2014-06-13 1:20 ` Samuel Wales
2014-06-12 19:34 ` Nicolas Girard
2014-06-12 20:13 ` Eric Schulte
2014-06-12 22:42 ` Nicolas Girard
2014-06-12 23:36 ` Eric Schulte
2014-06-13 0:35 ` Ken Mankoff
2014-06-13 0:46 ` Eric Schulte
2014-06-13 2:35 ` Ken Mankoff
2014-06-13 11:11 ` Eric Schulte
2014-06-13 3:28 ` Mark Edgington
2014-06-13 14:23 ` Rasmus
2014-06-14 12:43 ` Nicolas Goaziou
2014-06-14 16:48 ` Mark Edgington
2014-06-14 18:12 ` Aaron Ecay
2014-06-14 18:12 ` Nicolas Goaziou
2014-06-14 18:07 ` Aaron Ecay
2014-06-14 18:22 ` Nicolas Goaziou
2014-06-14 22:39 ` Aaron Ecay
2014-06-16 1:14 ` Eric Schulte
2014-06-16 8:08 ` Nicolas Goaziou
2014-06-16 12:19 ` Mark Edgington
2014-06-16 13:29 ` Eric Schulte
2014-06-22 2:03 ` Aaron Ecay
2014-06-22 23:52 ` Eric Schulte
2014-07-27 17:21 ` Bastien
2014-07-28 18:15 ` Mark Edgington
2014-07-28 18:27 ` Rasmus
2014-07-28 19:21 ` Mark Edgington
2014-07-28 19:43 ` Nicolas Goaziou
2014-07-28 22:01 ` Rasmus
2014-07-29 14:31 ` Bastien
2014-08-02 5:16 ` Mark Edgington
2014-08-06 4:09 ` Aaron Ecay
2014-06-13 2:38 ` Eric Abrahamsen
2014-06-13 4:07 ` Mark Edgington
2014-06-13 4:44 ` Eric Abrahamsen
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=loom.20140612T194320-659@post.gmane.org \
--to=edgimar@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).