emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Sebastien Vauban <sva-news-D0wtAvR13HarG/iDocfnWg@public.gmane.org>
To: emacs-orgmode-mXXj517/zsQ@public.gmane.org
Subject: Re: [RFC] Simplify `org-show-context' configuration
Date: Tue, 17 Feb 2015 09:25:03 +0100	[thread overview]
Message-ID: <86y4nx3py8.fsf@example.com> (raw)
In-Reply-To: 87lhjxh8q4.fsf@nicolasgoaziou.fr

Hello Nicolas,

Nicolas Goaziou wrote:
> As explained in its commit message, the following patch is an attempt at
> simplifying `org-show-context' configuration by offering a set of
> 5 predefined views to choose from instead of setting 4 different
> variables (`org-show-following-heading', `org-show-siblings',
> `org-show-entry-below' and `org-show-hierarchy-above'). These views are
>
>   minimal        show current headline, and entry below if needed
>   local          show current headline, entry below and next headline
>   lineage        show direct ancestors and all siblings of current headline;
>                  show entry only if required
>   canonical      show direct ancestors and all of their siblings; show entry
>                  only if required
>   full           show direct ancestors, all their siblings and entry
>
> To sum it up, if original buffer is
>
>   * H1
>   * H2
>   ** Sub 1
>   ** Sub 2
>   *** Sub sub 1
>   *** Sub sub 2
>       Text
>   *** Sub sub 3
>   *** Sub sub 4
>   ** Sub 3
>
> and match is on "Text", minimal is
>
>   * H1
>   * H2
>     * Sub sub 2
>       Text
>
> `local' is
>
>   * H1
>   * H2
>   *** Sub sub 2
>       Text
>   *** Sub sub 3
>
> `lineage' is
>
>   * H1
>   * H2
>   ** Sub 2
>   *** Sub sub 1
>   *** Sub sub 2
>       Text
>   *** Sub sub 3
>   *** Sub sub 4
>
> `canonical' and `full' are
>
>   * H1
>   * H2
>   ** Sub 1
>   ** Sub 2
>   *** Sub sub 1
>   *** Sub sub 2
>       Text
>   *** Sub sub 3
>   *** Sub sub 4
>   ** Sub 3
>
> Note that neither `canonical' nor `full' are possible to obtain with the
> 4 original variables.

Question: are the level-1 headlines always visible, all of them I mean?
I know that's the case as of now, but wondered if it'd be good to hide
the ones which are not significant.  Not a very sharp advice on this,
though.

> "if required"/"if needed" means the entry will only be shown if point is
> within the entry (i.e., not on the headline). Thus, for example,
> `canonical' and `full' only differ when match is on a headline, since
> only latter will show the entry.
>
> I think this is enough, but I can add more views if needed.
>
> WDYT?

My /personal/ preference is to see the ancestors, so that I can know
which path lead to the entry, and avoid confusion in case some "sub sub
sections" are repeated in many different "sub sections".

With your proposal, I then only have the choice between `lineage',
`full' and `canonical', while I'd like something which would give me:

--8<---------------cut here---------------start------------->8---
  * H1
  * H2
  ** Sub 2
  *** Sub sub 2
      Text
--8<---------------cut here---------------end--------------->8---

WDYT?

Best regards,
  Seb

-- 
Sebastien Vauban

  parent reply	other threads:[~2015-02-17  8:25 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 [this message]
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
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=86y4nx3py8.fsf@example.com \
    --to=sva-news-d0wtavr13harg/idocfnwg@public.gmane.org \
    --cc=emacs-orgmode-mXXj517/zsQ@public.gmane.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).