emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Bastien <bzg@gnu.org>
To: Christian Hemminghaus <chrhemmi@gmail.com>
Cc: emacs-orgmode@gnu.org, mail <mail@nicolasgoaziou.fr>
Subject: Re: Bug: Moving org-inline-tasks produces error message [9.3.6 (9.3.6-elpa @ /home/c.hemminghaus/.emacs.d/elpa/org-9.3.6/)]
Date: Sat, 05 Sep 2020 12:42:08 +0200	[thread overview]
Message-ID: <875z8s5wu7.fsf@gnu.org> (raw)
In-Reply-To: <CAE47VC=yhObXs3jexLUkf53cNzcOWUkTMqpF8QK4Dcg98QijyQ@mail.gmail.com> (Christian Hemminghaus's message of "Wed, 15 Jul 2020 11:07:07 +0200")

Hi Christian,

Christian Hemminghaus <chrhemmi@gmail.com> writes:

> I ran into an error message while composing structured text with
> org-mode using org-inline-tasks. The error appears when moving around
> inline tasks in my document.

yes, I confirm this bug.

The wrong behavior is here, whether you loaded org-inlinetask or not,
but the error ("Invalid...") is only triggered when org-inlinetask is

I guess this is due to `org-element-at-point' considering inline tasks
as headlines, thus trying to move only one line.

Nicolas, would you know how to solve this (if it does not get us into
hard syntactic decisions)?


  reply	other threads:[~2020-09-05 10:42 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-07-15  9:07 Bug: Moving org-inline-tasks produces error message [9.3.6 (9.3.6-elpa @ /home/c.hemminghaus/.emacs.d/elpa/org-9.3.6/)] Christian Hemminghaus
2020-09-05 10:42 ` Bastien [this message]
2020-09-07  6:45   ` Christian Hemminghaus
2021-05-13 13:06   ` Bastien
2021-05-14 18:08     ` Michael Dauer
2021-05-15  9:02       ` Bastien
2021-05-15 16:20         ` Michael Dauer
2021-05-15 11:06     ` Ihor Radchenko
2021-05-15 12:35       ` Bastien
2021-05-15 13:00         ` Ihor Radchenko
2021-05-15 13:06           ` 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=875z8s5wu7.fsf@gnu.org \
    --to=bzg@gnu.org \
    --cc=chrhemmi@gmail.com \
    --cc=emacs-orgmode@gnu.org \
    --cc=mail@nicolasgoaziou.fr \


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