From mboxrd@z Thu Jan 1 00:00:00 1970 From: Alan L Tyree Subject: Re: [PROPOSAL] Use prefix arg to control scope of org-narrow-to-subtree. Date: Thu, 25 Apr 2019 07:56:54 +1000 Message-ID: <01d7eb13-00ae-cfcb-7356-e29aa0ce1a98@gmail.com> References: <87ftq7kyvt.fsf@red-bean.com> Reply-To: alantyree@gmail.com Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit Return-path: Received: from eggs.gnu.org ([209.51.188.92]:56782) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1hJPt0-0002ti-6J for emacs-orgmode@gnu.org; Wed, 24 Apr 2019 17:57:03 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1hJPsy-0003ri-Tl for emacs-orgmode@gnu.org; Wed, 24 Apr 2019 17:57:02 -0400 Received: from mail-pl1-x632.google.com ([2607:f8b0:4864:20::632]:34839) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1hJPsy-0003q7-Mq for emacs-orgmode@gnu.org; Wed, 24 Apr 2019 17:57:00 -0400 Received: by mail-pl1-x632.google.com with SMTP id w24so9975871plp.2 for ; Wed, 24 Apr 2019 14:57:00 -0700 (PDT) Received: from ?IPv6:2001:8003:2411:ce00:c05f:e594:61f6:e942? ([2001:8003:2411:ce00:c05f:e594:61f6:e942]) by smtp.googlemail.com with ESMTPSA id y8sm25981343pgk.20.2019.04.24.14.56.57 for (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 24 Apr 2019 14:56:57 -0700 (PDT) In-Reply-To: <87ftq7kyvt.fsf@red-bean.com> Content-Language: en-AU 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 On 25/4/19 5:05 am, Karl Fogel wrote: > Hi. This is a feature proposal -- if the consensus is that it would be welcomed, I'm happy to code it. I just didn't want to take the time to write it if there's no chance for it to be accepted upstream (since I don't want to be maintaining my own personal branch of Org Mode). > > It would be useful if `org-narrow-to-subtree' could optionally narrow to the next subtree(s) up, rather than only to the subtree point is currently in. For example, assume this text: > > * This is the first level > Some text here. > ** This is the second level > Some other text here. > *** This is the third level > By now we all know this song. > It is such a pretty song. > **** This is the fourth level > But do we have to sing it all day long? > This car trip is getting incong > ***** This is the fifth level > ruously unrhymed. > > Further assume that point is on the "c" of "car trip". > > In the current Org Mode, if you type `C-x n s', it will narrow to the fourth-level subtree (with the fifth level included in the narrowed buffer, of course). > > Since `org-narrow-to-subtree' takes no arguments at all right now, it's conveniently ripe for improvement :-). > > My proposal is for each raw prefix arg (each `C-u' prefix) to expand the narrowing level outward/upward by one. So in the above situation: > > - `C-u C-x n s' would narrow to the third-level subtree > > - `C-u C-u C-x n s' would narrow to the second-level subtree > > And so on. > > If you offer too many `C-u's, such that the narrowing would be wider than the current surrounding first-level subtree, then there are two possible ways we could handle it: > > 1) Extra `C-u's are ignored -- just narrow to surrounding 1st-level subtree. > > 2) Throw an error. > > I prefer (1), because it would be the more useful behavior, even though (2) would be easier to implement (since `org-back-to-heading' already throws the error). However, I'd welcome others' feedback on that question, or on any other aspect of this proposal. > > Best regards, > -Karl > Hi Karl, I would definitely use this feature. I'm not in a position to help with coding, but would be happy to help test. I presume that it would also apply to C-c C-x b: org-tree-to-indirect-buffer. Regards, Alan -- Alan L Tyree http://www2.austlii.edu.au/~alan