emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Nicolas Goaziou <mail@nicolasgoaziou.fr>
To: "Kévin Le Gouguec" <kevin.legouguec@gmail.com>
Cc: Org Mode List <emacs-orgmode@gnu.org>
Subject: Re: [RFC] Rewrite org-(forward|backward)-paragraph
Date: Mon, 08 Jun 2020 19:24:05 +0200	[thread overview]
Message-ID: <87y2ox5v4a.fsf@nicolasgoaziou.fr> (raw)
In-Reply-To: <875zc1d3f3.fsf@gmail.com> (=?utf-8?Q?=22K=C3=A9vin?= Le Gouguec"'s message of "Mon, 08 Jun 2020 16:42:56 +0200")

Hello,

Kévin Le Gouguec <kevin.legouguec@gmail.com> writes:

> I don't know how useful my feedback will be, since I'm not a heavy user
> of paragraph-based movement[1], but here goes!

Thank you!

> I've danced around ORG-NEWS to assess the changes; what I observed does
> feel closer to text-mode (point moves to the blank lines between
> paragraphs instead of to the paragraph starts), the other changes I
> could spot do not strike me as deal-breaking:
>
> - point now jumps over tight lists[2] instead of stopping at each
> item,

The idea is to avoid some trivial moves where C-n would be sufficient,
e.g., in tables, properties drawers. Also Text mode skip those, since it
doesn't understand such structures.

> - point stops a few more times within code blocks, acting like
>   #+begin_src and #+end_src are paragraphs of their own, instead of
>   jumping over the whole block; also, forward and backward movements are
>   now symmetric 🙌
>
> Are there other situations where you think your changes could be
> controversial?

I don't think it's much controversial, but stop points are necessarily
opinionated. I hope they make sense.

Also, testing could unveil some bugs.

>> WDYT?e Also, what should be done with M-{ and M-}?
>
> FWIW, I think that reducing the distance between Org mode and The Rest
> of Emacs™ is a commendable goal, so I would vote for binding paragraph
> functions to M-{ and M-}, and moving element functions to C-<UP> and
> C-<DOWN>.  I realize that this might be too big a change for the sake of
> conformity though.

Honestly, I don't know if Sexp-based navigation is useful at all. Does
anyone use such navigation ?

> (And again: I don't use these functions very often, so my vote probably
> shouldn't carry too much weight.)

I don't either. I didn't notice there was a difference until recently.

Regards,

-- 
Nicolas Goaziou


  reply	other threads:[~2020-06-08 17:25 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-06-03 22:21 Nicolas Goaziou
2020-06-08 14:42 ` Kévin Le Gouguec
2020-06-08 17:24   ` Nicolas Goaziou [this message]
2020-06-13 15:25     ` 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=87y2ox5v4a.fsf@nicolasgoaziou.fr \
    --to=mail@nicolasgoaziou.fr \
    --cc=emacs-orgmode@gnu.org \
    --cc=kevin.legouguec@gmail.com \
    --subject='Re: [RFC] Rewrite org-(forward|backward)-paragraph' \
    /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

Code repositories for project(s) associated with this 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).