From mboxrd@z Thu Jan 1 00:00:00 1970 From: Nathan Neff Subject: Org meta up/down and left/right behavior Date: Tue, 5 Nov 2019 08:58:54 -0600 Message-ID: Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="0000000000005df0cb05969aac42" Return-path: Received: from eggs.gnu.org ([2001:470:142:3::10]:59257) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1iS0IV-0003KR-R6 for emacs-orgmode@gnu.org; Tue, 05 Nov 2019 09:59:08 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1iS0IU-0001aW-KX for emacs-orgmode@gnu.org; Tue, 05 Nov 2019 09:59:07 -0500 Received: from mail-il1-x135.google.com ([2607:f8b0:4864:20::135]:33980) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1iS0IU-0001a6-FM for emacs-orgmode@gnu.org; Tue, 05 Nov 2019 09:59:06 -0500 Received: by mail-il1-x135.google.com with SMTP id p6so5776855ilp.1 for ; Tue, 05 Nov 2019 06:59:05 -0800 (PST) List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org Sender: "Emacs-orgmode" To: emacs-orgmode --0000000000005df0cb05969aac42 Content-Type: text/plain; charset="UTF-8" Hello all, I noticed for the first time the difference in the shift key behavior in the following function groups: org-meta up/down versus org-shiftmeta up/down and org-meta left/right versus org-shift meta left/right With the up/down behavior the shift key being pressed indicates that I wish to only bring the main heading up/down. With the left/right behavior the shift key indicates that I wish to bring the entire subtree left / right. This behavior seems to be inconsistent -- am I correct? I noticed this only today - I use the left/right behavior the most often and map the shift key to mean "Take the entire subtree". Today I was moving some headlines up/down and noticed this difference. Has anyone made this behavior consistent by mapping keys or some other method? It seems that changing these specific mappings could impact other aspects (e.g. table rows) which may cause other inconsistencies -- thus the difference in behavior of the shift key :-) Thanks, --Nate --0000000000005df0cb05969aac42 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Hello all,

I noticed for the first = time the difference in the shift key
behavior in the following fu= nction groups:

org-meta up/down versus org-shiftme= ta up/down
and
org-meta left/right versus org-shift met= a left/right

With the up/down behavior the shift k= ey being pressed indicates
that I wish to only bring the main hea= ding up/down.

With the left/right behavior the shi= ft key indicates that I wish
to bring the entire subtree left / r= ight.

This behavior seems to be inconsistent -- am= I correct?=C2=A0 I noticed this only=C2=A0
today - I use the lef= t/right behavior the most often and map the shift key to mean
&qu= ot;Take the entire subtree".=C2=A0 Today I was moving some headlines u= p/down and noticed
this difference. =C2=A0

Has anyone made this behavior consistent by mapping keys or some other m= ethod?=C2=A0 It seems
that changing these specific mappings could= impact other aspects (e.g. table rows) which may
cause other inc= onsistencies -- thus the difference in behavior of the shift key :-)
<= div>
Thanks,
--Nate
--0000000000005df0cb05969aac42--