From: Rasmus <rasmus@gmx.us>
To: bzg@gnu.org
Cc: emacs-orgmode@gnu.org
Subject: Re: Should org-narrow-to-subtree be disabled by default?
Date: Fri, 03 Jan 2014 16:50:40 +0100 [thread overview]
Message-ID: <87mwjdxdwv.fsf@gmx.us> (raw)
In-Reply-To: <8761q1cbxc.fsf@bzg.ath.cx> (Bastien's message of "Fri, 03 Jan 2014 16:39:11 +0100")
Bastien <bzg@gnu.org> writes:
> Rasmus <rasmus@gmx.us> writes:
>
>> Bastien <bzg@gnu.org> writes:
>>
>>> one good way to decide could be to ask people here if they ever
>>> accidentally narrowed the view to a subtree -- I never did.
>>
>> No. But I know the concept of narrowing, which may be unfamiliar to
>> some. I find narrowing super useful, especially when writing longer
>> documents.
>
> I checked narrow-to-defun, and it is not disabled by default, only
> narrow-to-region and narrow-to-page, which are both accessible in any
> mode.
>
> As org-narrow-to-* functions are only accessible from org-mode buffers
> and not that easily called by accident (I haven't seen any report like
> this in years), I suggest we stick to the current setup.
Fine with me.
>>> Also, I tend to think Emacs is on the paranoid side here, I don't
>>> think newbies can hit C-x n n accidentally...
>>
>> Perhaps an easier way to narrow by accident is through
>> org-speed-commands-default, i.e. speedkey "s".
>
> Yes, but newbies don't use speed commands without knowing what they
> do, do they?
Probably not since org-use-speed-commands is nil by default.
--
A page of history is worth a volume of logic
prev parent reply other threads:[~2014-01-03 15:47 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-23 13:55 Should org-narrow-to-subtree be disabled by default? Jisang Yoo
2013-11-23 15:25 ` Bastien
2013-11-23 15:53 ` Rasmus
2014-01-03 15:39 ` Bastien
2014-01-03 15:50 ` Rasmus [this message]
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=87mwjdxdwv.fsf@gmx.us \
--to=rasmus@gmx.us \
--cc=bzg@gnu.org \
--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).