From: Ihor Radchenko <yantar92@posteo.net>
To: Michael Dauer <mick.dauer@gmail.com>
Cc: emacs-orgmode@gnu.org
Subject: [POLL] Should org-copy/cut/paste-special handle inlinetasks specially? (was: BUG: org-cut-special on inlinetask kill until point-max)
Date: Thu, 17 Aug 2023 17:50:57 +0000 [thread overview]
Message-ID: <87msyppnge.fsf@localhost> (raw)
In-Reply-To: <CAP7OBxJpjA-oJwUEd8jcm4uD47_3d-OCanr1qoSnPNurraCuTQ@mail.gmail.com>
Michael Dauer <mick.dauer@gmail.com> writes:
> I understand your view. From the user perspective inline task are still
> more a specialization of a task, which is a specialisation of a heading.
>
> Here is my implementation of how I see it that it should behave:
> (defun pm-cut-special ()
> "Like org-cut-special but also works on inlinetask."
> (interactive)
> (if (not (eq 'inlinetask (save-excursion (org-back-to-heading t)
> (org-element-type (org-element-context)))))
> (funcall-interactively 'org-cut-special)
> (org-inlinetask-goto-beginning)
> (let ((begin (point)))
> (org-inlinetask-goto-end)
> (kill-region begin (point))
> (message "Cut: Inline Task"))))
I looked into this further, and I can see that in the earlier versions
of Org org-cut-special on inlinetask killed that inlinetask, not the
containing subtree:
* Heading
Text
****************** Inlinetask<point>
****************** END
More text
* Another heading
C-c C-x C-w
* Heading
Text
<point>
More text
* Another heading
It was by accident, AFAIU. Also, when point was at END, it was buggy
(only removed "END" line).
So, technically, the current behaviour cutting the actual subtree (not
inlinetask) can be considered a feature regression (if we call the
previously existing bug a "feature").
I think that it would be slightly better to keep special behaviour for
inlinetasks. But other opinions would be appreciated.
--
Ihor Radchenko // yantar92,
Org mode contributor,
Learn more about Org mode at <https://orgmode.org/>.
Support Org development at <https://liberapay.com/org-mode>,
or support my work at <https://liberapay.com/yantar92>
prev parent reply other threads:[~2023-08-17 17:51 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-16 11:14 BUG: org-cut-special on inlinetask kill until point-max Michael Dauer
2023-08-16 11:48 ` Ihor Radchenko
2023-08-16 11:57 ` Michael Dauer
2023-08-16 12:12 ` Ihor Radchenko
2023-08-16 15:55 ` Michael Dauer
2023-08-16 16:02 ` Ihor Radchenko
2023-08-17 8:42 ` Michael Dauer
2023-08-17 8:56 ` Ihor Radchenko
2023-08-17 9:00 ` Michael Dauer
2023-08-17 11:30 ` Ihor Radchenko
2023-08-17 13:05 ` Michael Dauer
2023-08-17 17:50 ` Ihor Radchenko [this message]
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=87msyppnge.fsf@localhost \
--to=yantar92@posteo.net \
--cc=emacs-orgmode@gnu.org \
--cc=mick.dauer@gmail.com \
/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).