emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed

From: Kyle Meyer <kyle@kyleam.com>
To: Nicolas Goaziou <mail@nicolasgoaziou.fr>
Cc: emacs-orgmode@gnu.org
Subject: Re: Behavior of `org-show-entry'
Date: Mon, 06 Feb 2017 12:18:20 -0500	[thread overview]
Message-ID: <877f535jc3.fsf@kyleam.com> (raw)
In-Reply-To: <877f53wjkf.fsf@nicolasgoaziou.fr>

Nicolas Goaziou <mail@nicolasgoaziou.fr> writes:

> Kyle Meyer <kyle@kyleam.com> writes:
>
>> Hmm, for the reason I gave above, I don't think org-show-entry should
>> change, but perhaps there should be a separate function that does
>>
>>     (org-show-entry)
>>     (org-with-limited-levels (org-show-children))
>>
>> which is what org-cycle does for the second state listed in its
>> docstring.  Or maybe there is a better way to accomplish this that I
>> don't know about.
>
> See `org-show-context' and `org-reveal'.

Sadly, I had already seen these, and I still answered what I did :)

It seems like, with the default value of org-show-context-detail,
(org-show-context 'agenda) will show the desired view of

    * a
    
    
    a body
    
    ** aa...
    * b

So, do you recommend that, assuming helm wants this view after jumping
to a heading, it calls (org-show-set-visibility 'local)?  Or should it
use its own key, something like (org-show-context 'helm), so that users
can customize the key in org-show-context-detail?  Or something else?

Thanks.

-- 
Kyle

next prev parent reply	other threads:[~2017-02-06 17:18 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-02-05 20:11 Behavior of `org-show-entry' Eric Abrahamsen
2017-02-05 22:03 ` Kyle Meyer
2017-02-05 23:16   ` Eric Abrahamsen
2017-02-06  0:31     ` Kyle Meyer
2017-02-06 13:11       ` Nicolas Goaziou
2017-02-06 17:18         ` Kyle Meyer [this message]
2017-02-06 17:29         ` 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=877f535jc3.fsf@kyleam.com \
    --to=kyle@kyleam.com \
    --cc=emacs-orgmode@gnu.org \
    --cc=mail@nicolasgoaziou.fr \
    /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

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).