From: Carsten Dominik <dominik@uva.nl>
To: Carsten Dominik <carsten.dominik@gmail.com>
Cc: Dan Davison <davison@stats.ox.ac.uk>,
Matti De Craene <mattidecraene@gmail.com>,
emacs-orgmode@gnu.org, Bastien <bastien.guerry@wikimedia.fr>
Subject: Re: [Patch] M-Right and M-Left behave differently on headings and list items
Date: Fri, 23 Apr 2010 10:26:08 +0200 [thread overview]
Message-ID: <EE9A115E-E508-4546-ACF1-E77178EEC509@uva.nl> (raw)
In-Reply-To: <61F604DA-1716-464B-A8BD-EB8FBCE3FE2B@gmail.com>
On Apr 22, 2010, at 6:02 PM, Carsten Dominik wrote:
>
> On Apr 21, 2010, at 4:44 PM, Dan Davison wrote:
>
>> Carsten Dominik <carsten.dominik@gmail.com> writes:
>>
>>> On Apr 21, 2010, at 3:32 PM, Bastien wrote:
>>>
>>>> Carsten Dominik <carsten.dominik@gmail.com> writes:
>>>>
>>>>> do others agree with Matti's view?
>>>>
>>>> FWIW, I do.
>>>
>>> There is still another difference.
>>>
>>> Currently, when I execute the indentation command
>>> several times in a row, the range to which this applies
>>> is locked.
>>>
>>> So for example"
>>>
>>> - level 1a
>>> - level 2a
>>> - level 2b
>>> - level 2c
>>> - level 1b
>>>
>>> If I now go on level 1a and use M-S-left, level 1b becomes a sibling
>>> of 2c. If I immediately after this do M-S-right, 1b should be
>>> indented
>>> along with 2c, but this does not happen because the item range is
>>> locked. If, however, you do something in between, like moving the
>>> cursor by one character, 1b will be included.
>>>
>>> I believe I did this a long time ago, because I felt that not
>>> locking
>>> the range for commands in direct succession would too quickly modify
>>> the structure, including at places outside of the current view (
>>> beyond the window end)
>>>
>>> If you are calling for more consistency, maybe this "feature" should
>>> go as well?
>>
>> I hope that this is sufficiently closely related to belong in this
>> thread: I find it surprising that org-do-demote deactivates the
>> region. Let's say I start out with
>>
>> * 1
>> ** 11
>> * 111
>> * 112
>> * 2
>>
>> and I wish to move to make 111 and 112 be children of 11
>>
>> The way that seems natural to me is to select headings 111 and 112,
>> and
>> apply org-demote-subtree twice in succession. So with point at the
>> beginning of the 111 line,
>>
>> C-space down down M-right M-right
>
> Hi Dan,
>
> I do agree with your observation. However, keeping the mark active
> would mean that further cursor motions will still have the
> highlighted region hanging around, and I found this the bigger
> headache.
>
> What I do in these cases is
>
> M-right C-x C-x M-right
>
> which is not pretty but workable.
If you have a better solution, please let me know.
- Carsten
>
> - Carsten
>
>>
>> However, this leads me to
>>
>> * 1
>> ** 11
>> ** 111
>> ** 112
>> ** 2
>>
>> because after one application of org-demote-subtree, the region
>> becomes
>> deactivated and the second demotion applies to heading 2, which is
>> unlikely to have been intended.
>>
>> Dan
>>
>>
>>>
>>> - Carsten
>>>
>>>
>>>
>>> _______________________________________________
>>> Emacs-orgmode mailing list
>>> Please use `Reply All' to send replies to the list.
>>> Emacs-orgmode@gnu.org
>>> http://lists.gnu.org/mailman/listinfo/emacs-orgmode
>
> - Carsten
>
>
>
- Carsten
next prev parent reply other threads:[~2010-04-23 8:26 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-19 22:29 [Patch] M-Right and M-Left behave differently on headings and list items Matti De Craene
2010-04-21 12:53 ` Carsten Dominik
2010-04-21 13:19 ` Sébastien Vauban
2010-04-21 13:27 ` Anthony Lander
2010-04-21 13:32 ` Bastien
2010-04-21 13:54 ` Carsten Dominik
2010-04-21 14:04 ` Bernt Hansen
2010-04-21 14:44 ` Dan Davison
2010-04-22 16:02 ` Carsten Dominik
2010-04-23 8:26 ` Carsten Dominik [this message]
2010-04-21 20:27 ` Matti De Craene
2010-04-21 21:07 ` Carsten Dominik
2010-04-22 10:15 ` Bastien
2010-04-22 20:37 ` Matti De Craene
2010-04-23 8:26 ` Carsten Dominik
2010-04-26 22:07 ` Matti De Craene
2010-04-27 5:57 ` 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
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=EE9A115E-E508-4546-ACF1-E77178EEC509@uva.nl \
--to=dominik@uva.nl \
--cc=bastien.guerry@wikimedia.fr \
--cc=carsten.dominik@gmail.com \
--cc=davison@stats.ox.ac.uk \
--cc=emacs-orgmode@gnu.org \
--cc=mattidecraene@gmail.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).