emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Jonathan Leech-Pepin <jonathan.leechpepin@gmail.com>
To: Trevor Vartanoff <tv@codepuzzles.org>
Cc: emacs-orgmode@gnu.org, n.goaziou@gmail.com
Subject: Re: org-metaup / org-metadown nerfed in 7.9.1
Date: Wed, 26 Sep 2012 21:49:35 -0400	[thread overview]
Message-ID: <CAEWDx5ewLwQD7L5O-O6v4ChWix31RdvnO0BaTXuF-9z0QDL2VA@mail.gmail.com> (raw)
In-Reply-To: <50638D34.1090603@codepuzzles.org>

Hello Trevor,

On 26 September 2012 19:18, Trevor Vartanoff <tv@codepuzzles.org> wrote:
> Nicolas,
> "Org has its own definition for a paragraph, which, apparently, doesn't
> match yours.
> A paragraph ends either at a blank line, at the end of the buffer, or at
> the start of another non-paragraph element. In particular, indentation is
> unrelated to paragraph boundaries."
> If your definition of a paragraph excludes every single publication of
> fiction and nonfiction in the history of written language, you may want to
> rethink your definition. I think Charles Dickens knew what a paragraph
> boundary was.

LaTeX uses the same paragraph definition, it splits on blank lines.
So does the old exporter.  By default if there is not a blank line
they treat it as a continuation of the previous.  If you treat it
otherwise how do you tell the difference between a manual break and
wrapped text that went to the next line?

> Actually, it's worse than that: even if you agree that everyone using a
> computer should now separate all paragraphs with a blank line, it still
> means that for any form of writing with closely packed separate lines, such
> as song lyrics, poetry, Shakespeare plays, or even basic lists of todo
> items, org-mode no longer lets you shift the lines around.

Basic lists of todo items will still work fine, Org treats list items
as their own elements and can be moved using org-metaup/down.  It will
also move paragraphs/verses for poetry and theater.  =transpose-lines=
( C-x C-t ) can be used to move the individual lines around

> I propose we implement an org-property value to decide which definition of
> "element" org-metaup should use. I'm glad to see an exception was made for
> node property, but that's only one of many, many problem cases.
> Regards,
> Trevor Vartanoff


  reply	other threads:[~2012-09-27  1:49 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-09-26 23:18 org-metaup / org-metadown nerfed in 7.9.1 Trevor Vartanoff
2012-09-27  1:49 ` Jonathan Leech-Pepin [this message]
2012-09-27  8:18 ` Bastien
  -- strict thread matches above, loose matches on Subject: below --
2012-09-27  2:09 Trevor Vartanoff
2012-09-20 14:29 Trevor Vartanoff
2012-09-19 14:44 Trevor Vartanoff
2012-09-19 14:50 ` Anthony Lander
2012-09-22  9:24   ` Bastien
2012-09-23  8:25     ` Nicolas Goaziou
2012-09-23  9:39       ` Bastien
2012-09-23 10:03       ` Carsten Dominik
2012-09-23 17:39         ` Nicolas Goaziou
2012-09-23 18:05           ` Bastien
2012-09-23 19:51     ` Anthony Lander
2012-09-23  8:20 ` Nicolas Goaziou
2012-09-18 15:50 Trevor Vartanoff
2012-09-19  6:43 ` Bastien

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=CAEWDx5ewLwQD7L5O-O6v4ChWix31RdvnO0BaTXuF-9z0QDL2VA@mail.gmail.com \
    --to=jonathan.leechpepin@gmail.com \
    --cc=emacs-orgmode@gnu.org \
    --cc=n.goaziou@gmail.com \
    --cc=tv@codepuzzles.org \


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