From: Nicolas Goaziou <mail@nicolasgoaziou.fr>
To: Karl Fogel <kfogel@red-bean.com>
Cc: Org Mode <emacs-orgmode@gnu.org>
Subject: Re: [PROPOSAL] Use prefix arg to control scope of org-narrow-to-subtree.
Date: Thu, 25 Apr 2019 10:42:11 +0200 [thread overview]
Message-ID: <878svyqxwc.fsf@nicolasgoaziou.fr> (raw)
In-Reply-To: <87ftq7kyvt.fsf@red-bean.com> (Karl Fogel's message of "Wed, 24 Apr 2019 14:05:10 -0500")
Hello,
Karl Fogel <kfogel@red-bean.com> writes:
> 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:
I suggest to use a numeric argument for that. M-1 for one level, M-2 for
two levels, maybe M-0 equivalent to current behaviour. C-u can be
a shortcut for M-1.
> 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.
1 sounds good.
I think it is a good idea.
Thank you.
Regards,
--
Nicolas Goaziou
next prev parent reply other threads:[~2019-04-25 8:42 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-24 19:05 [PROPOSAL] Use prefix arg to control scope of org-narrow-to-subtree Karl Fogel
2019-04-24 21:56 ` Alan L Tyree
2019-04-24 22:02 ` Alan L Tyree
2019-04-25 8:42 ` Nicolas Goaziou [this message]
2019-05-31 7:33 ` Karl Fogel
2019-12-01 8:45 ` [PATCH] " Karl Fogel
2019-12-01 13:13 ` Marco Wahl
2019-12-01 15:25 ` Karl Fogel
2019-12-01 15:44 ` Marco Wahl
2019-12-01 15:46 ` Karl Fogel
2019-12-02 8:51 ` Eric Abrahamsen
2019-12-02 15:15 ` Marco Wahl
2019-12-02 18:06 ` Karl Fogel
2019-12-02 18:56 ` Marco Wahl
2019-12-02 19:17 ` Karl Fogel
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=878svyqxwc.fsf@nicolasgoaziou.fr \
--to=mail@nicolasgoaziou.fr \
--cc=emacs-orgmode@gnu.org \
--cc=kfogel@red-bean.com \
/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).