[Vimoutliner] Obvious but don't get it: how do I move outline at N+1 to N

[Peter Princz]

Noel,

On 03/09/06, Noel Henson <noel at noels-lab.com> wrote:
> I need to know how hoisting messed up your files. I'd like to fix it.
> I use hoisting and haven't seen any problems.
>
> Noel
>
> On Sunday 03 September 2006 08:11, Steve Litt wrote:
> > On Sunday 03 September 2006 09:47 am, Peter Princz wrote:
> > > I'm still afraid of the hoisting feature of vimoutliner, as it
> > > corrupted/messed up my file once.
> >
> > Ditto.
> >
> > > So I have a "hoisting/indent manipulation sandbox" within my outline
> > > file
> >
> > I just don't use hoisting. ,,1 and then drilling down gives you pretty
> > much the same thing, and is safe. Yeah, drilling down is nice, but not
> > essential.
> >
> > Also, it's always possible that the need to hoist possibly implies a
> > need to create a suboutline and use interoutline linking.
> >
> > SteveT

take it easy, it isn't that serious. Here is a use-case realisation I
just reproduced. As you'll see, in most of the inconveniences hoisting
per se cannot be blamed.

0. As I wrote earlier in several posts, I maintain a one-and-only,
huge outline file, that for the moment contains even it's own archive.
:o
I wanted to see at which point in time it grows to an unmanageable
size. Now it  has: 17999 lines, 88882 words, 730822 bytes.
It is password-protected, opening it takes almost one minute on my
computer, while processor is 100% busy, so I can't do anything but
drink my morning coffee while it opens. :)
(One of the outstanding tasks is to figure out how to archive it, so
to downsize it sometime the end of this year to approx. 300 kBytes, or
get a faster computer.)

1. I do hoisting. The cursor is blinking on the status line, no
indication it is waiting for a password. Took 30 minutes for the first
time to realise it. :)

2. The newly created hoisting file has wrong file type (not vo_base,
but outliner), wrong colorscheme, tabstop settings, foldcolumn, etc,
all of this despite the .otl extension. So the first minute goes away
to type password, and reshape the hoisted file to look like an .otl
should look like. :(

3. Upon exiting back to the main file, again, no notification it asks
for a password, just a blinking cursor. However, now it doesn't need
any password to open my file, which I think is a security hole: my
intention with hoisting would be to hide the surrounding of the item
from curious eye, even to hand over the keyboard and let a contributor
to work on the hoisted subtree. Az accidental :q wold bring him/her
back to my outline file, which I do not like.

4. The encryption of this huge file is again lot of time. Not an issue
once in the morning, but I can't have a cup of coffee after each
hoisting. :)

5. By accident, my outline file is placed on my Windows desktop at the
moment, (which will be changed soon), but still, the desktop gets
cluttered with icons of the log files, which I have to delete
manually. Again, a little extra overhead.

6. I can't see and track the changes made in the hoisting session in
:changes. One single :undo is rolling back the whole hoisting session,
which could be a good idea, however, it modifies the hoisting point
with its fingerprint that has to removed manually again. (e.g.
__hoist:vo_hoist.14789.20060903200225.otl)

So, because of all of these inconveniences, I yank/move the desired
leaf into the aforementioned hoisting/indent manipulation area at the
tail of the file, and do the wizardry there. Or simply write out part
of the file into an external and unencrypted one if I want to hand
over a leaf to a contributor.

Well, as I wrote above, most of these issues don't point to any
implementation error in hoisting. It's just more convenient for me not
to use this particular feature of vimoutliner, and fall back to
traditional vim features instead.
Right now I'm in the process of changing my job, so I'll get a new,
perhaps faster computer (maybe not even with Windows), will redesign
the folder structure around The Outline File, so most of the problems
I expect to vanish in two weeks.

Have a nice day,
  Peter

-- 
Keep cool. Develop in total darkness.