From: Allen Li <vianchielfaura@gmail.com>
To: Nathan Aclander <nathan.aclander@gmail.com>
Cc: emacs-orgmode@gnu.org, Nicolas Goaziou <mail@nicolasgoaziou.fr>
Subject: Re: Bug: shiftmeta[left|right] on multi line items [9.1.2 (release_9.1.2-40-g6ca906 @ /usr/local/share/emacs/27.0.50/lisp/org/)]
Date: Sat, 9 Dec 2017 17:04:20 -0800 [thread overview]
Message-ID: <CAJr1M6fj5UscKD7S_7cyR8rm5w3mb==X2Xe0WVDLc2WKDCh=YQ@mail.gmail.com> (raw)
In-Reply-To: <87k1xvwh1m.fsf@gmail.com>
On Sat, Dec 9, 2017 at 4:41 PM, Nathan Aclander
<nathan.aclander@gmail.com> wrote:
>
> Nicolas Goaziou <mail@nicolasgoaziou.fr> writes:
>
>> I don't qualify this as a bug. These commands explicitly work when point
>> is at the beginning of an item. Indeed, the sub-item may be arbitrarily
>> large, contain tables... it would be confusing to move the whole
>> sub-list when its structure is out of sight.
>
> Why do you think it would be confusing to move the whole sub-list? Why
> would it be move confusing when the point is on the sub-item vs. when
> the point is on the parent item?
>
> I think the inconsistency is unintuitive here, and causes confusion. And
> I think since large sub-items already get moved when the point is
> at the beginning, it would make sense to also move them when the point
> is on the sub item.
>
> Nathan
I think what Nicolas is saying is this (^ is point):
* ^Heading
M-S-left/right works here.
* Heading
^content text
M-S-left/right does not work here. Let’s assume that it does work
here to be consistent with the feature/bug you are requesting.
* Heading
- foo
- bar
^second bar line
M-S-left/right does not work here. Let’s assume that it does work
here per the feature/bug you are requesting. Does it move bar, foo,
or Heading? What if the text is very long and you cannot see where
you are?
...
some very long text
^some very long text
some very long text
...
What M-S-left/right does would be very confusing.
next prev parent reply other threads:[~2017-12-10 1:04 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-22 5:00 Bug: shiftmeta[left|right] on multi line items [9.1.2 (release_9.1.2-40-g6ca906 @ /usr/local/share/emacs/27.0.50/lisp/org/)] Nathan Aclander
2017-12-01 17:28 ` Nicolas Goaziou
2017-12-10 0:41 ` Nathan Aclander
2017-12-10 1:04 ` Allen Li [this message]
2017-12-10 5:25 ` Nathan Aclander
2017-12-10 16:01 ` Nicolas Goaziou
2017-12-10 19:33 ` Nathan Aclander
2017-12-22 18:37 ` Nicolas Goaziou
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='CAJr1M6fj5UscKD7S_7cyR8rm5w3mb==X2Xe0WVDLc2WKDCh=YQ@mail.gmail.com' \
--to=vianchielfaura@gmail.com \
--cc=emacs-orgmode@gnu.org \
--cc=mail@nicolasgoaziou.fr \
--cc=nathan.aclander@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).