From mboxrd@z Thu Jan 1 00:00:00 1970 From: Kyle Meyer Subject: Re: Behavior of `org-show-entry' Date: Sun, 05 Feb 2017 19:31:11 -0500 Message-ID: <87a8a05fe8.fsf@kyleam.com> References: <87lgtk8kja.fsf@ericabrahamsen.net> <87d1ew5m8w.fsf@kyleam.com> <877f548bzu.fsf@ericabrahamsen.net> Mime-Version: 1.0 Content-Type: text/plain Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:54451) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1caXDE-0001wI-1k for emacs-orgmode@gnu.org; Sun, 05 Feb 2017 19:31:20 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1caXD9-0007Uu-Gl for emacs-orgmode@gnu.org; Sun, 05 Feb 2017 19:31:20 -0500 Received: from pb-smtp1.pobox.com ([64.147.108.70]:53788 helo=sasl.smtp.pobox.com) by eggs.gnu.org with esmtps (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.71) (envelope-from ) id 1caXD9-0007Ug-B1 for emacs-orgmode@gnu.org; Sun, 05 Feb 2017 19:31:15 -0500 Received: from sasl.smtp.pobox.com (unknown [127.0.0.1]) by pb-smtp1.pobox.com (Postfix) with ESMTP id E480C67537 for ; Sun, 5 Feb 2017 19:31:12 -0500 (EST) Received: from pb-smtp1.nyi.icgroup.com (unknown [127.0.0.1]) by pb-smtp1.pobox.com (Postfix) with ESMTP id D9F8467536 for ; Sun, 5 Feb 2017 19:31:12 -0500 (EST) Received: from localhost (unknown [24.60.167.92]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by pb-smtp1.pobox.com (Postfix) with ESMTPSA id 4DB4067534 for ; Sun, 5 Feb 2017 19:31:12 -0500 (EST) In-Reply-To: <877f548bzu.fsf@ericabrahamsen.net> List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org Sender: "Emacs-orgmode" To: emacs-orgmode@gnu.org Eric Abrahamsen writes: > Kyle Meyer 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 > . 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