From: Michael Dauer <mick.dauer@gmail.com>
To: Ihor Radchenko <yantar92@posteo.net>
Cc: emacs-orgmode@gnu.org
Subject: Re: BUG: org-cut-special on inlinetask kill until point-max
Date: Wed, 16 Aug 2023 13:57:43 +0200 [thread overview]
Message-ID: <CAP7OBxJQrNDxVHdyYApg1q-yj+Rz0F-M2kUipLbWvuy6_XwxJQ@mail.gmail.com> (raw)
In-Reply-To: <877cpvqkcb.fsf@localhost>
[-- Attachment #1: Type: text/plain, Size: 723 bytes --]
Put the point on the second line - the inlinetask "ilt".
Am Mi., 16. Aug. 2023 um 13:47 Uhr schrieb Ihor Radchenko <
yantar92@posteo.net>:
> Michael Dauer <mick.dauer@gmail.com> writes:
>
> >>>>
> > * h1
> > *************** ilt
> > *************** END
> > ** h11
> > * h2
> > <<<
> > org-cut-special somewhere on the send line kills all but the first line.
>
> I am unable to reproduce.
> May you please provide more detailed steps?
> In particular, which line are you referring to?
>
> --
> 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>
>
[-- Attachment #2: Type: text/html, Size: 1426 bytes --]
next prev parent reply other threads:[~2023-08-16 11:58 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 [this message]
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 ` [POLL] Should org-copy/cut/paste-special handle inlinetasks specially? (was: BUG: org-cut-special on inlinetask kill until point-max) Ihor Radchenko
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=CAP7OBxJQrNDxVHdyYApg1q-yj+Rz0F-M2kUipLbWvuy6_XwxJQ@mail.gmail.com \
--to=mick.dauer@gmail.com \
--cc=emacs-orgmode@gnu.org \
--cc=yantar92@posteo.net \
/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).