From: Eric Abrahamsen <eric@ericabrahamsen.net>
To: emacs-orgmode@gnu.org
Subject: Re: proposal to have ignoreheading tags/properties
Date: Fri, 13 Jun 2014 10:38:52 +0800 [thread overview]
Message-ID: <87egyt354z.fsf@ericabrahamsen.net> (raw)
In-Reply-To: CAMsBe8rWvKfqcOCZ0WFEToNy6KMMOL3syPHkuzffmqjQ5qJfdg@mail.gmail.com
Mark Edgington <edgimar@gmail.com> writes:
> In using org-mode, there is one problem that has always irked me (and
> is apparently also closely related to the FAQ "How do I ignore a
> headline?"). When I am writing something, I sometimes want to group
> things by concept or by work to be done, or any other number of
> groupings. BUT I do not want these groupings to be part of the
> exported document itself. In fact, I would like it to be as if the
> grouping did not exist at all (i.e. a headline that is ignored).
>
> The problem with using an ignored headline for grouping things is that
> it still does have an effect on exported document structure, in that
> all of the elements contained "inside / in the scope of" the ignored
> headline still keep their depth (one level deeper than the level of
> the ignored headline).
>
> What I want is for the nested items to have their levels all promoted
> by one, so that it's truly as if the ignored headline wasn't there at
> all, and that it invisibly wrapped around a group of items without
> requiring them to have a deeper level. Perhaps this could be done by
> use of an "ignoreheading" and an "ignoreheadingpromote" tag (one
> promotes the level of contained items, another doesn't), or some
> equivalent set of properties that could be set on a headline.
>
> Would there be any chance that something like this could be built in
> to org-mode? I think it would make it far more flexible in terms of
> organizing things, making this organization process orthogonal to the
> selection of sections/subsections of a document.
It looks like a groundswell for remove-andor-promote tags for headlines,
but for the sake of argument let me propose the use of blocks. It seems
to me that something like a "generic block" (a block that does nothing
but delete its begin/end delimiters on export) fits the use-case better:
#+BEGIN_BLOCK Here's a list of reasons why blocks make sense
1. They group together content that should go together, but don't
constitute a part of document structure. They're a little like
notecards in Scrivener
2. You can fold them like headlines, and re-order them with
org-meta(up|down)
3. You could put arbitrary text after the begin block declaration, as if
it were ignored headline text.
4. I can't think of any more reasons, except that this seems like the
right "weight" for this kind of feature.
#+END_BLOCK
Anyway, just being argumentative...
E
next prev parent reply other threads:[~2014-06-13 2:35 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
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 [this message]
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=87egyt354z.fsf@ericabrahamsen.net \
--to=eric@ericabrahamsen.net \
--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).