Samuel Wales writes:
> so here i go again with new decription: i am taking an entry and putting a
> whole other entry into the middle of it at the same level like this:
>
> ===
> * a new idea i had
> regarding snicker snacks
> * jabberwoky
> some sophomoric comments on a poem
>
> more sophomoric
to be clear, i am not suggesting violating outline mode's inability to
continue text after children, or violating levels. let me redo.
i am ONLY saying i sometimes have the need to yank into the middle of the
text of an entry, even if what i am yanking is an entry.
it was probalby confusing that
not sure i am fully following but it seems useful.
i thought i would report on a use case thtat might or might not be
relevant. it seems so.
i often have
===
* heading 1
text of heading 1
* heading 2
text of heading 2
|
and more text
===
where | just shows where i want to yank.
and i want to
Philipp Kiefer writes:
> To be honest, I don't see much need for fine-grained special cases. I'd
> be very happy with C-u yanking at the level of the heading at point and
> C-u C-u yanking at one level below that, regardless of the exact
> position of point. I realize that would mean C-u doubl
Ihor Radchenko writes:
> Steps to reproduce:
>
> 1. Create a file
>
> 1.1.1.1
> 1.1.1.2
> * 3
> ** 3.1
> *** 3.1.1
> low-level item
> *** 3.1.2
> *** 3.1.3
>
> 2. Copy the first two headings
> 3. Move point as indicated
> 4. M-x org-paste-subtree
>
> Observed: 1.* headings
On 20.01.2023 11:21, Ihor Radchenko wrote:
Philipp Kiefer writes:
Further, you suggest I use C-S- to demote the subtree after
pasting it at the same level as the subtree at point. But what if I used
a numerical prefix argument to copy or cut several subtrees, maybe 5 or
10? Not very convenie
Philipp Kiefer writes:
> Further, you suggest I use C-S- to demote the subtree after
> pasting it at the same level as the subtree at point. But what if I used
> a numerical prefix argument to copy or cut several subtrees, maybe 5 or
> 10? Not very convenient at all to demote them all by hand.
Philipp Kiefer writes:
> 1. Org Mode-paste subtree low-level item swallowed:
> https://imgur.com/a/CZ5lDaH . This relates to what I assume the passage
> from the manual is trying to say should not happen:
>
> "makes sure that the subtree
> remains an independent subtree and does not swallow low
I've uploaded two screencasts to illustrate the issues described in my
last message:
1. Org Mode-paste subtree low-level item swallowed:
https://imgur.com/a/CZ5lDaH . This relates to what I assume the passage
from the manual is trying to say should not happen:
"makes sure that the subtree
re
Philipp Kiefer writes:
> Thanks for addressing my concern, Ihor.
>
> So I can force same-level yank by navigating to the beginning of the
> current headline before calling org-paste-subtree, I see. However, I
> still do not see a way to force it to paste one level below the current
> headline,
Thanks for addressing my concern, Ihor.
So I can force same-level yank by navigating to the beginning of the
current headline before calling org-paste-subtree, I see. However, I
still do not see a way to force it to paste one level below the current
headline, i. e. to add the trees on the clip
Philipp Kiefer writes:
> Unfortunately, org-paste-subtree currently attempts to "modify the level of
> the subtree to make sure the tree fits in nicely at the yank position"
> [from Org Manual].
> ...
> My suggestion would be to make a fundamental change to how the command
> works, prioritizing d
Hello there, orgmode list, this is my first contribution here, so please be
gentle with me.
I've now used outlining software for the last twenty years at least and it
is my belief that when a user pastes headlines into an outline, they
usually want to make them either A) siblings of (i. e. paste t
13 matches
Mail list logo
