From: Kyle Meyer <kyle@kyleam.com>
To: emacs-orgmode@gnu.org
Subject: Re: Behavior of `org-show-entry'
Date: Sun, 05 Feb 2017 19:31:11 -0500 [thread overview]
Message-ID: <87a8a05fe8.fsf@kyleam.com> (raw)
In-Reply-To: <877f548bzu.fsf@ericabrahamsen.net>
Eric Abrahamsen <eric@ericabrahamsen.net> writes:
> Kyle Meyer <kyle@kyleam.com> writes:
[...]
>> Based on how org-show-entry calls it, outline-flag-region shows the text
>> from the current heading to the next. So it seems to behave as
>> documented: "[s]how the body directly following this heading".
>
> Okay, but I still don't see how this would ever be the desired result.
> You can't get to *any* next visibility state without first wasting a
> <tab>.
Yeah, fair enough. I can't think of a situation where I would desire
that result either. But I think org-show-entry probably should behave
this way to be consistent with outline-show-entry.
>>> Which part of this should be tweaked to achieve the desired effect?
>>
>> Perhaps helm could call org-show-children after it calls org-show-entry.
>
> Okay, cool. I guess my main question was: should this be fixed in helm,
> or in org? I'll try clobbering the helm functions for a while and see
> how that goes, then raise this on the helm list.
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.
--
Kyle
next prev parent reply other threads:[~2017-02-06 0:31 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 [this message]
2017-02-06 13:11 ` Nicolas Goaziou
2017-02-06 17:18 ` Kyle Meyer
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=87a8a05fe8.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).