From: Samuel Wales <samologist@gmail.com>
To: Samuel Wales <samologist@gmail.com>,
Org Mode List <emacs-orgmode@gnu.org>
Subject: Re: [RFC] Simplify `org-show-context' configuration
Date: Tue, 17 Feb 2015 15:07:23 -0700 [thread overview]
Message-ID: <CAJcAo8tJCzwrJpkFc_PQ0FUQhpQwNN5z-amyS=OWgz=sHav5QQ@mail.gmail.com> (raw)
In-Reply-To: <87pp98uv7o.fsf@nicolasgoaziou.fr>
hi nicolas,
On 2/17/15, Nicolas Goaziou <mail@nicolasgoaziou.fr> wrote:
> I don't understand. Body text is not shown in ancestors. Considering the
> following buffer:
>
> * Grandmother
> ** Uncle
> *** Heir
> ** Father
> Ancestor text
> *** Sister
> Sibling text
> *** Self
> Match
> **** First born
> Child text
> **** The other child
> *** Brother
> ** Aunt
>
> `canonical' view is
>
> * Grandmother
> ** Uncle
> ** Father
> *** Sister
> *** Self
> Match
> **** First born
> **** The other child
> *** Brother
> ** Aunt
thanks for showing a complete example.
that is not canonical. i thought we were working from my previous
posts over the years where i used the term "canonical".
you cannot create the visibility state you show from a fully-folded
buffer using only arrow keys and tab.
there are exactly two types of visibility. each type has many
variants in principle, but we only need a few for each.
1] can be created using arrows and tab from a fully-folded buffer
2] cannot
this is a critical distinction.
org so far is not capable of doing any of the [1] states when going to
a location. that's the problem that needs solving imo.
i actually don't care about any of the [2] states until [1] is possible.
within [1], there is a minimal state. let's call it
minimal-canonical. /that/ is the state that is most needed. it's
roughly like what you show except with the body text for all
ancestors.
what you show is [2]. it is a great view, and needed, but it is not
minimal-canonical.
i don't want the term canonical to be used for any of the [2] states,
because then we will be back to missing the need for the
minimal-canonical view and the need for preserving an org buffer's [1]
status.
hope that clarifies.
samuel
--
The Kafka Pandemic: http://thekafkapandemic.blogspot.com
The disease DOES progress. MANY people have died from it. And
ANYBODY can get it.
Denmark: free Karina Hansen NOW.
next prev parent reply other threads:[~2015-02-17 22:07 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-16 21:01 [RFC] Simplify `org-show-context' configuration Nicolas Goaziou
2015-02-16 23:15 ` Kyle Meyer
2015-02-17 0:00 ` Nicolas Goaziou
2015-02-17 8:25 ` Sebastien Vauban
2015-02-17 8:43 ` Nicolas Goaziou
2015-02-17 9:19 ` Sebastien Vauban
2015-02-17 9:53 ` Eric Abrahamsen
2015-02-17 10:10 ` Sebastien Vauban
2015-02-17 10:59 ` Nicolas Goaziou
2015-02-17 19:05 ` Samuel Wales
2015-02-17 20:41 ` Nicolas Goaziou
2015-02-17 22:07 ` Samuel Wales [this message]
2015-02-18 0:24 ` Nicolas Goaziou
2015-02-18 0:52 ` Samuel Wales
2015-02-22 14:01 ` Nicolas Goaziou
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='CAJcAo8tJCzwrJpkFc_PQ0FUQhpQwNN5z-amyS=OWgz=sHav5QQ@mail.gmail.com' \
--to=samologist@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).