From: Trevor Vartanoff <tv@codepuzzles.org>
To: emacs-orgmode@gnu.org
Subject: Re: org-metaup / org-metadown nerfed in 7.9.1
Date: Wed, 19 Sep 2012 10:44:03 -0400 [thread overview]
Message-ID: <5059DA33.3030109@codepuzzles.org> (raw)
Your explanation is useful. After some more experimenting, it looks like
7.8.11 accepts a return as the dividing line between "elements", but
7.9.1 only recognizes them as separate if there's an empty line between
them.
Example: if I copy the first two lines of your email, I can shift "It is
hard to understand..." to be after "When did you get the message...",
but not if I delete the empty line between them.
And so, example 2, I was receiving "cannot drag element
forward/backward" when I was in a heading with no line breaks. That is,
a heading where paragraphs are separated with return + indent rather
than a full line break of return + return.
(Behavior is identical when I start with an empty .emacs, for the record)
I suppose people who only write and handle text with Internet-style line
breaks between paragraphs won't notice any change. Those who don't will
either get "cannot" messages, or they will be quite surprised when org
scans down, down, down for the next line break and ends up shifting 20
paragraphs as one element.
next reply other threads:[~2012-09-19 14:44 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-19 14:44 Trevor Vartanoff [this message]
2012-09-19 14:50 ` org-metaup / org-metadown nerfed in 7.9.1 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
-- strict thread matches above, loose matches on Subject: below --
2012-09-27 2:09 Trevor Vartanoff
2012-09-26 23:18 Trevor Vartanoff
2012-09-27 1:49 ` Jonathan Leech-Pepin
2012-09-27 8:18 ` Bastien
2012-09-20 14:29 Trevor Vartanoff
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:
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=5059DA33.3030109@codepuzzles.org \
--to=tv@codepuzzles.org \
--cc=emacs-orgmode@gnu.org \
/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).