From: Carsten Dominik <carsten.dominik@gmail.com>
To: Noorul Islam K M <noorul@noorul.com>
Cc: pjmtavares@hotmail.com, emacs-orgmode@gnu.org
Subject: Re: Re: Variable 'org-ctrl-k-protect-subtree' defaults to nil
Date: Wed, 3 Nov 2010 23:30:20 +0100 [thread overview]
Message-ID: <3A548F03-656C-4DC9-AF0A-01569627F98E@gmail.com> (raw)
In-Reply-To: <87y69audks.fsf@noorul.maa.corp.collab.net>
On Nov 3, 2010, at 7:27 AM, Noorul Islam K M wrote:
> <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.
I agree with Norul. C-k kills an entire visible line, and that
line has ... ellispes and therefore *contains* the folded text.
Just killing the headline would leave ... on a line by its own,
a bad state which is not good to have. This change would also
make the behavior inconsistent with other Emacs modes and behavior.
So we will keep the current default - but feel free to submit a
patch to documentation or a tutorial to points out this issue
to beginners.
Greetings.
- Carsten
prev parent reply other threads:[~2010-11-04 1:41 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
2010-11-03 9:22 ` Alan L Tyree
2010-11-03 22:30 ` Carsten Dominik [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=3A548F03-656C-4DC9-AF0A-01569627F98E@gmail.com \
--to=carsten.dominik@gmail.com \
--cc=emacs-orgmode@gnu.org \
--cc=noorul@noorul.com \
--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 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).