From: Nathan Aclander <nathan.aclander@gmail.com>
To: Allen Li <vianchielfaura@gmail.com>
Cc: Nathan Aclander <nathan.aclander@gmail.com>,
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, 09 Dec 2017 21:25:56 -0800 [thread overview]
Message-ID: <87indfw3vf.fsf@gmail.com> (raw)
In-Reply-To: <CAJr1M6fj5UscKD7S_7cyR8rm5w3mb==X2Xe0WVDLc2WKDCh=YQ@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1666 bytes --]
Allen Li <vianchielfaura@gmail.com> writes:
> 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.
Using ^ as point like you did, what I am expecting to happen is:
Case 1:
* Heading
- foo
- ^bar
second bar line
M-S-left/right moves
- bar
second bar line
left and right.
Case 2:
- foo
- bar
^second bar line
M-S-left/right moves
- bar
second bar line
left and right.
Case 3:
...
some very long text
^some very long text
some very long text
...
Whatever sub list that "some very long text" is part of should be moved
left and right.
None of these scenarios seem very confusing, and ( at least to me ) seem
more consistent than the current behavior. Could you explain why you
find adding this behavior would make this confusing?
As a current workaround, what I have to do is:
1. save point
2. Go to the parent sub-list
3. Shift left or right
4. move point back to its previous location.
Nathan
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 832 bytes --]
next prev parent reply other threads:[~2017-12-10 5:26 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
2017-12-10 5:25 ` Nathan Aclander [this message]
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=87indfw3vf.fsf@gmail.com \
--to=nathan.aclander@gmail.com \
--cc=emacs-orgmode@gnu.org \
--cc=mail@nicolasgoaziou.fr \
--cc=vianchielfaura@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).