From: Christian Hemminghaus <chrhemmi@gmail.com>
To: Bastien <bzg@gnu.org>
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: Mon, 7 Sep 2020 08:45:26 +0200 [thread overview]
Message-ID: <CAE47VCk1vCVRbpEiq3Q=n8JW-uP=i3wb7psbp2ucoWLkgZ3sCQ@mail.gmail.com> (raw)
In-Reply-To: <875z8s5wu7.fsf@gnu.org>
Hi Bastien,
> 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)?
This would probably be the clean solution. As a (temporary)
workaround, I hooked org-metaup/-down and ask for org-inlintask at
point explicitly.
```
(defun ch/org-metaup-inlinetask ()
"If at inline task and not active region, drag inline task backward."
(if (and (not (org-region-active-p)) (org-inlinetask-at-task-p))
(org-drag-element-backward)
nil))
(defun ch/org-metadown-inlinetask ()
"If at inline task and not active region, drag inline task forward."
(if (and (not (org-region-active-p)) (org-inlinetask-at-task-p))
(org-drag-element-forward)
nil))
(add-hook 'org-metaup-hook 'ch/org-metaup-inlinetask t)
(add-hook 'org-metadown-hook 'ch/org-metadown-inlinetask t)
```
Regards,
Christian
next prev parent reply other threads:[~2020-09-07 6:46 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
2020-09-07 6:45 ` Christian Hemminghaus [this message]
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:
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='CAE47VCk1vCVRbpEiq3Q=n8JW-uP=i3wb7psbp2ucoWLkgZ3sCQ@mail.gmail.com' \
--to=chrhemmi@gmail.com \
--cc=bzg@gnu.org \
--cc=emacs-orgmode@gnu.org \
--cc=mail@nicolasgoaziou.fr \
/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).