From: Kyle Meyer <kyle@kyleam.com>
To: Org Mode List <emacs-orgmode@gnu.org>
Subject: Re: [RFC] Simplify `org-show-context' configuration
Date: Mon, 16 Feb 2015 18:15:44 -0500 [thread overview]
Message-ID: <87d25930tb.fsf@kyleam.com> (raw)
In-Reply-To: <87lhjxh8q4.fsf@nicolasgoaziou.fr> (Nicolas Goaziou's message of "Mon, 16 Feb 2015 22:01:07 +0100")
Nicolas Goaziou <mail@nicolasgoaziou.fr> 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
[...]
>
> I think this is enough, but I can add more views if needed.
>
> WDYT?
I prefer this to the old setup. From a configuration standpoint, it's
much nicer to have all the relevant information in one variable.
[...]
> +As a special case, a nil (respectively t) value means
> +`minimal' (respectively `full') detail level for all contexts.
Minor: It took me some extra effort to parse this sentence because I'm
not used to seeing 'respectively' used in this way. I think something
like below is more common.
As special cases, a nil or t value means show all contexts in
`minimal' or `full' view, respectively.
[...]
> (defun org-reveal (&optional siblings)
> "Show current entry, hierarchy above it, and the following headline.
> -This can be used to show a consistent set of context around locations
> -exposed with `org-show-hierarchy-above' or `org-show-following-heading'
> -not t for the search context.
> +
> +This can be used to show a consistent set of context around
> +locations exposed with `org-show-context'.
>
> With optional argument SIBLINGS, on each level of the hierarchy all
> siblings are shown. This repairs the tree structure to what it would
Does a single C-u serve a purpose anymore?
--
Kyle
next prev parent reply other threads:[~2015-02-16 23:15 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 [this message]
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
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=87d25930tb.fsf@kyleam.com \
--to=kyle@kyleam.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).