emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Peter Mao <peter.mao@gmail.com>
To: Max Nikulin <manikulin@gmail.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: missing from the manual - move commands
Date: Mon, 26 Dec 2022 17:35:12 -0800	[thread overview]
Message-ID: <CAEK3s1NWdo5cTyniZmTZ6fXG85fzVR9xbzuXUVzdBrc_rzGozA@mail.gmail.com> (raw)
In-Reply-To: <e7082c5f-3be8-1bdd-5d0c-5668ce29db94@gmail.com>

[-- Attachment #1: Type: text/plain, Size: 843 bytes --]

On Mon, Dec 26, 2022 at 7:03 AM Max Nikulin <manikulin@gmail.com> wrote:

> On 24/12/2022 09:43, Peter Mao wrote:
> > The following commands are missing from the manual!
> >
> > org-forward-element
> > org-backward-element
> I think, the manual was written with assumption that Emacs users are
> familiar with C-up, M-{, C-down, M-} keystrokes.
Not everyone uses all of the motion commands.  I've been using emacs since
v18, and forward-paragraph and backward-paragraph have never been part of
my repertoire.

In addition, M-right and M-left, which I have used a lot outside of org,
for decades, behave differently in org, so the existence of motion commands
that are common in emacs (outside of org) do not guarantee an equivalent
inside of org.  BTW, I think M-f and M-b are better anyways, but decades of
muscle memory die hard.


[-- Attachment #2: Type: text/html, Size: 1179 bytes --]

  reply	other threads:[~2022-12-27  1:36 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-12-24  2:43 missing from the manual Peter Mao
2022-12-25  8:07 ` Marcin Borkowski
2022-12-25  8:19   ` Ihor Radchenko
2022-12-25 21:09     ` Peter Mao
2022-12-26 15:03 ` missing from the manual - move commands Max Nikulin
2022-12-27  1:35   ` Peter Mao [this message]
2023-01-25 13:42 ` [TODO] Document org-forward-element and org-backward-element in the manual (was: missing from the manual) Ihor Radchenko

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:

  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=CAEK3s1NWdo5cTyniZmTZ6fXG85fzVR9xbzuXUVzdBrc_rzGozA@mail.gmail.com \
    --to=peter.mao@gmail.com \
    --cc=emacs-orgmode@gnu.org \
    --cc=manikulin@gmail.com \


* 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


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).