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

Peter Princz princzp at gmail.com
Wed Sep 6 09:30:52 EDT 2006


Steve,

On 04/09/06, Steve Litt <slitt at troubleshooters.com> wrote:
> Yeah, I didn't do anything about it either. Back in those days I didn't take
> VO on Windows seriously, but now that a lot of people are using it on
> Windows, a more OS independent method of interoutline linking might be
> preferable.
>
> If/when we implement it, we need to do so in a way that doesn't screw up
> traditional interoutline linking. I've been using Ctags interoutline linking
> since 2001.
>
> I'd suggest we have a config flag for linking_portable or linking_classic, and
> to start out with default it to linking_classic. As it proves itself able,
> (and this includes performance), switch the default to linking_portable. If,
> over a period of a year or 2 the portable method proves as good as or better
> than classic in every respect, we can then deprecate classic.
>
> Which leaves just one question -- who will develop the linking_portable code?
> Probably the people with the biggest itch (and the greatest opportunity to
> test it) will be the VO on Windows users. Perhaps some of them can develop
> it, and of course, we VO on Linux people will test their code on Linux.
>
> Sound like a reasonable plan?
>
> SteveT
>

it's maybe a stupid question, but what's wrong with ctags on Windows?
I do have it anyway for coding reasons.
It is you don't want to have yet another dependency to 3rd party tool?
Then we already have vimoutliner scriptified around in perl, python,
ruby, etc...

Or: do ctags's features differ on Windows and Linux?

I personally can't see any problem setting a requirement on installing
ctags to use outline linking...

Have a nice day,
  Peter

-- 
Keep cool. Develop in total darkness.


More information about the VimOutliner mailing list