The main advantage is that all org-mode actions on subtrees would work
without any specific handling of inline tasks. e.g. visibility cycling,
hiding of none context, cut/copy, moving. With many of these actions I
experience some issues with inline tasks. And even from my personal user
perception I
Ihor Radchenko writes:
> Bastien writes:
>> Can you make a patch for this?
>
> It was easier than I anticipated. See the attached.
Indeed! Thanks, applied.
--
Bastien
Bastien writes:
> Can you make a patch for this?
It was easier than I anticipated. See the attached.
>From f681dcb12df823cafe388973bb93c83ce2e0f6bb Mon Sep 17 00:00:00 2001
Message-Id:
From: Ihor Radchenko
Date: Sat, 15 May 2021 20:57:00 +0800
Subject: [PATCH] Allow moving inlinetasks using or
Ihor Radchenko writes:
> Bastien writes:
>> Carsten proposed a patch that I adapted a little bit and pushed to the
>> maint branch. We now throw an error saying that dragging inline tasks
>> is not supported.
>
> Isn't it easy to implement using org-element-swap-A-B?
Well, probably, I didn't
Bastien writes:
> Carsten proposed a patch that I adapted a little bit and pushed to the
> maint branch. We now throw an error saying that dragging inline tasks
> is not supported.
Isn't it easy to implement using org-element-swap-A-B?
Something like
(defun org-element-swap-at-point (&optiona
Hi Michael,
Michael Dauer writes:
> Wouldn't it be the much better approach to changeĀ inlineĀ tasks so
> that the END line is one level below the "begin" line?
I'm not sure how this would be better, and I would rather find this
more confusing. What is the expected benefit?
--
Bastien
Hi,
Wouldn't it be the much better approach to change inline tasks so that the
END line is one level below the "begin" line?
I did not think it through. But IMO it would make IT more compatible with
normal org behavior, and also more visually appealing.
With the END notation it would still be un
Hi Christian,
Bastien writes:
> Christian Hemminghaus 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.
Carsten proposed a patch tha
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
Hi Christian,
Christian Hemminghaus 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-inli
Hello everyone,
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.
Here is the example:
# # BEGIN EXAMPLE
This is a paragraph in my document.
It may contain multiple lines.
11 matches
Mail list logo