> Not 100% clear on your goal - basically cut / yank / push a subtree,
> which you're identifying by hoisting, to a stack, rather than the
> single content clipboard, and the copy / pop it somewhere else later?
> I guess I'm confused by the mix of moving subtrees and hoisting.
>
> The
Hmm...
Chapters provide a similar function. I use them all the time for this
functionality.
Hope this helps!
-->Jake
On 12/2/2015 9:44 AM, Phil wrote:
Not 100% clear on your goal - basically cut / yank / push a subtree,
which you're identifying by hoisting, to a stack, rather than
> Chapters provide a similar function. I use them all the time for this
> functionality.
>
>
> Thanks for the tip, that is helpful. I had looked at chapters in the past
but didn't really get how they work. Playing with it again, now I get it.
--
You received this message because you are
The 'problem' with chapters, if you can call it that, is that they
'feel' more permanent -- you're making a change to the tree structure
(with @chapter nodes) to accommodate it -- of course, they're disposable
if you wish, just not transparently so.
-->Jake
On 12/2/2015 10:36 AM, Phil wrote:
> The 'problem' with chapters, if you can call it that, is that they 'feel'
> more permanent -- you're making a change to the tree structure (with
> @chapter nodes) to accommodate it -- of course, they're disposable if you
> wish, just not transparently so.
>
> Sure, that's a good point. I
On Wed, 2 Dec 2015 11:52:20 -0800 (PST)
Phil wrote:
> > The 'problem' with chapters, if you can call it that, is that they
> > 'feel' more permanent -- you're making a change to the tree
> > structure (with @chapter nodes) to accommodate it -- of course,
> > they're
Is there a command that can push the current (hoisted) root node onto a
stack, which can later be popped back to the hoisted root position? If not,
can someone provide some guidance for how I would implement this
functionality myself in a @button?
Thanks!
Phil
--
You received this message
On Tue, 1 Dec 2015 14:16:03 -0800 (PST)
Phil wrote:
> Is there a command that can push the current (hoisted) root node onto
> a stack, which can later be popped back to the hoisted root position?
> If not, can someone provide some guidance for how I would implement
> this