From: Noorul Islam K M <noorul@noorul.com>
To: pjmtavares@hotmail.com
Cc: emacs-orgmode@gnu.org
Subject: Re: Variable 'org-ctrl-k-protect-subtree' defaults to nil
Date: Wed, 03 Nov 2010 11:57:15 +0530 [thread overview]
Message-ID: <87y69audks.fsf@noorul.maa.corp.collab.net> (raw)
In-Reply-To: <SNT107-W442F76C02668C54D33B5B2DE490@phx.gbl> (pjmtavares@hotmail.com's message of "Tue, 2 Nov 2010 15:14:27 +0000")
<pjmtavares@hotmail.com> writes:
> Hi everyone,
>
> It's the first time I'm giving any feedback on org-mode, so first of all I would like to congratulate the original creator and all contributors on a very interesting and useful work.
>
> I've discovered org-mode only a couple of weeks ago and was intrigued enough to restart using emacs, after several years away from it! I've been studying Org's documentation and tutorials, and started using it to help me manage my relocation from Brazil to Italy.
>
> What I am reporting, technically, is a feature: the fact that variable 'org-ctrl-k-protect-subtree' defaults to nil. But considering how easy this makes to lose a whole subtree of data, especially for a newcomer to org-mode, I think it should be considered a serious bug. As a matter of fact, I am very surprised that C-k would be considered an admissible alternative to C-c C-x C-w/M-w, as a way to kill a subtree!
>
> I propose that 'org-ctr-k-protect-subtree' is made to default to 't' ASAP (already costumized it in that way on my setup), and that the behavior of C-k on headings is made consistent: kill to the end of line, regardless of the visibility of the subtree.
>
I slightly disagree here. Most of the time I definitely want the entire
subtree to go away. I think this is the beauty of outline mode.
Thanks and Regards
Noorul
next prev parent reply other threads:[~2010-11-03 6:29 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-02 15:14 Variable 'org-ctrl-k-protect-subtree' defaults to nil pjmtavares
2010-11-03 6:27 ` Noorul Islam K M [this message]
2010-11-03 9:22 ` Alan L Tyree
2010-11-03 22:30 ` Carsten Dominik
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87y69audks.fsf@noorul.maa.corp.collab.net \
--to=noorul@noorul.com \
--cc=emacs-orgmode@gnu.org \
--cc=pjmtavares@hotmail.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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.