Steve Litt | 16 May 21:37
Favicon

Vimoutliner

Hi Edward,

VimOutliner has reached a crossroads. Every outlining feature that can
reasonably be added to the Vim engine has been added to the Vim engine.
And a lot of people want more features. Just as a tiny example, cloning
and hoisting aren't reasonable to add to VimOutliner, at least without
involving databases, metatadata files, or other stuff that makes
VimOutliner not VimOutliner. A lot of people are wanting GTD modules,
and calendaring (we actually have a calendering module but it's not
popular anymore).

So all of us are pretty much in agreement that we need to build a new,
differently named outliner with all the features, and keep VimOutliner
in its current state (except for bug fixes) for those who want the
fastest outline authoring on the planet. 

The new outliner must have an available round-trip conversion, at least
for all VimOutliner features, between VimOutliner and the new outliner.
That way VimOutliner continues to be used for the fastest outlining on
the planet, while the new outliner prioritizes the ability to assist in
a plethora of human tasks.

If I read between the lines, the group is not married to the idea of
the new outliner exactly implementing VimOutliner's keystroke
interface, because the new outliner's priority is not necessarily speed
(not that we want it to be slow).

It's been about 4 years since I used Leo, but from what I remember it's
extremely featureful. I have no idea if Leo could easily incorporate
all our group's needed functions, nor whether its user interface
(Continue reading)

Rick | 23 Apr 23:10
Picon

MaxThink 89 Running As An Almost Native Linux App

The DOS version of MaxThink 89 can run as an almost native Linux app using 
dosemu. To duplicate this behavior do the following:

1) Install the dosemu package for your distro.

2) Create a directory named max hanging off your home directory:

mkdir ~/max

3) Copy all your MaxThink files to this directory (i.e., MAX.EXE, CONFIG89.MT, 
MESSAGES.MT, etc).

4) Add the following to your .bashrc file:

alias max="dosemu ~/max/MAX.EXE"

5) Instantiate the alias the first time:

source ~/.bashrc

6) You can now invoke max from the Linux command prompt as follows:

max file.mt

7) Familiarize yourself with some of the Linux helper apps like expand, 
unexpand, unix2dos and dos2unix. For example, to convert from otl format to mt 
do the following:

expand --tabs=1 file.otl > file.mt
printf "\x1A" >> file.mt
(Continue reading)

Steve Litt | 16 Apr 01:04
Favicon

A possible idea for high level architecture of new outliner

Hi all,

Attached are a .png showing a possible new architecture, and its .dia
source.

As Noel suggested, this keeps the application logic COMPLETELY separate
from the UI, through a thin interface called a Domain Specific Language
(DSL). The DSL defines and restricts the command set by which the
client can influence the server and vice versa. In this scenario, the
DSL becomes the #1 early design priority, because it almost completely
defines what the software is and isn't. Meanwhile, the UI designer
needs know ONLY the DSL in order to do his job, and the application
logic designer also needs know ONLY the DSL in order to do his job. If
there's a mismatch between the client or server (UI or app logic),
there are two and only two correct fixes:

1) Whomever has departed from the DSL gets his section DSL compliant.

2) The DSL is enhanced with a new command or new syntax to an existing
   command.

From my perspective, this takes one hugely difficult program and breaks
it into two quite manageable programs. And like I said before, the
client-server aspect gives us room to grow into a groupware outliner.
For that reason I think, as much as possible, we should define
groupware DSL commands even if they do nothing right now.

For securities sake, obviously any command going through the port that
doesn't start with a known command is thrown away. Or maybe aborted
with a security-tinged error message, with info necessary for the
(Continue reading)

Noel Henson | 13 Apr 16:46
Favicon

NewVO (for lack of a better name) Goals and Features Request

NewVO Brainstorming List

Goals 
**********************************************************************************************

Features 
*******************************************************************************************

Implementation Ideas 
*****************************************************************************

Sandbox (for what doesn't fit into the above categories) 
*******************************************
Ludo Beckers | 20 Feb 22:39
Picon

setting for "freezing" folds?

If I have an otl-file that I want to close and have it reopen exactly as I left it, regarding folds, is that possible?

Something like this idea:
- important stuff (unfolded)
- less imp stuff - 65 lines folded
- obscure stuff - 20 lines folded
- new project (unfolded)

Ludo

_______________________________________________
VimOutliner mailing list
VimOutliner <at> vimoutliner.org
http://www.lists.vimoutliner.org/mailman/listinfo
Ludo Beckers | 1 Jan 18:12
Picon

Re: Vim-Outliner for newbies please

Just wanted to say thanks!
The command
vim-addons install vimoutliner
simply worked :-)
I was trying to get Vim-outliner to work on my main os (Crunchbang
Statler) too, and found this is by far the easiest way.

Happy New Year wishes to all
Ludo

> On debian testing I installed vim-vimoutliner and vim-addon-manager, ran
> % vim-addons install vimoutliner
> restarted gvim, and vimoutliner just worked.  I had already updated my .vimrc
> to add
> filetype plugin on
> for other reasons.
>
> --
> Eric Krohn
Ludo Beckers | 3 Dec 11:54
Picon

Vim-Outliner for newbies please

I'm puzzled...
I have Gvim and Vim 2:7.3.035+hg~8fdc and through Synaptic I downloaded Vimoutliner, but I can't seem to get the Outliner working.
:help vimoutliner (and variations I tried) can't find help.
:help vo  gives help on Options instead of Outliner.
Documentation I found online is mostly very old with broken links.
I also downloaded an example.otl but apart from looking neatly divided into lines with tab inserts, nothing seems to work like what I would expect.
No comma comma command for example works.

I must add I'm quite new to Vim, so don't know the ins and outs of folding and such.
Is there any usable documentation for newbies?
I'd love to learn more about Vim, starting with using Outliner as a tool that I can deploy for every day usage.

Ludo

_______________________________________________
VimOutliner mailing list
VimOutliner <at> vimoutliner.org
http://www.lists.vimoutliner.org/mailman/listinfo
Wolfram Volpi | 27 Nov 09:36
Picon
Favicon

What are the folding rules?

What are the folding rules for Vimoutliner? The folding seems so random.

Thank you,
wolfv
Wolfram Volpi | 24 Nov 12:45
Picon
Favicon

formatter to convert MediaWiki to otl

Hello Vim Outliners,

I want to migrate some word processor documents to otl.  If you know of a formatter to convert "MediaWiki
to otl" or "odt to otl" or "doc to otl" please let me know.  I did not find one.

I am attempting to write ex script to convert MediaWiki to otl.  This would be useful
because LibreOffice Writer can export to MediaWiki format, and then the script would convert it to otl.

The heading format in MediaWiki is simple; one equal sign for each level in the heading hierarchy e.g.:

= head1 =
body text
== head2 ==
body text
=== head3 ===
body text

The above MediaWiki text should convert to otl like this:

head1
:body text
head2
:body text
head3
:body text

The attached MediaWiki2otl script converts MediaWiki to otl except for one thing.  I can not
figure out how to indent the body text lines (indent lines that start with “:”). Here is the pseudo code:

if current line has “=”
set count to number of “=”
else  
insert count “\t”

Can this be done in ex script? i.e. Is there an ex command that can set a variable (or register) and an ex
command to read that variable in the following lines?

Thank you,
wolfv
James Miller | 2 Nov 16:58

vimoutliner and bulleting/numbering

Hello all. I had a little trouble joining this list and so, having found 
Steve Litt's e-mail address, exchanged a couple of e-mails with him about 
the issues I will address below. It seemed that he might even have been 
entertaining the idea of putting together some sort of conversion utility 
geared toward my needs--which would be wonderful, since doing something 
like that is far beyond my competence. But I haven't heard back from him 
on that for a couple of days, so perhaps I misunderstood him. In any case, 
the following.

I've tried vim a few times during the years I've struggled to learn to use 
GNU/Linux. It was never very successful, in part, because I couldn't see 
how it was at all suited to my needs (academic writing in the humanities, 
for which WYSIWYG word processors seem to have been created). But as I've 
begun writing out lecture notes--being very displeased with Open/Libre 
Office's outlining functionality for that purpose and in search for 
something less resource-intensive--I came across VimOutliner, and now I 
finally see a really good use for vim in my work.

My experiments this time with vim and VO are going more smoothly. VO seems 
to hold great promise as a tool for creating my lecture notes, which take 
the form of an outline: VO seems a great way to record and organize the 
thoughts and ideas that go into my lectures. But my lecture notes, once 
created, need to be useful outside my computer's hard drive as well: 
namely, they must be printed and taken to the lecture hall, where I can 
use them for reference during my lecture. And, as good as VO is for the 
process of recording and organizing thoughts, it is not good at all as a 
tool for getting the recorded and organized thought into a printed 
document useful at the podium.

For the notes to be useful as a document at the podium, several changes 
from the form the VO outline takes on the screen are needed: the font 
needs to be enlarged (14 pt. is about right for my aging eyes), 
line-spacing needs to be about 1.5, the document should have a header, 
there should be page numbering, and there should be bullets or numbering 
at the various levels of the outline (to act as visual cues and reference 
points). VO cannot, of course, do any of this.

Steve mentioned LaTeX as a good tool for introducing such things, and, 
having experimented a little with LaTeX, I'm aware it can do this and that 
the output looks very nice. As to how to make the VO file import into 
LaTeX without having manually to introduce all the necessary mark-up, 
well, I'm at a loss.

I did manage to get a good portion of the way toward the printed form I 
need by using another program, though. I discovered that .otl files import 
fine into Libre Writer, and from there, it is a very simple matter to 
enlarge the font and add a header and page numbering. The one thing that 
Writer cannot, apparently, help me to do, though, is to insert bullets or 
numbering: that would all, so far as I can tell, have to be done manually.

So, my question to the list at this point is whether there has already 
been developed, or might be developed by someone with the requisite 
technical skills, a way to insert bullets or numbering into the outline 
that has been created in VO? Ideally those bullets or numbering would vary 
according to the level of outline headings. But at this point, I think I 
would be satisfied even with the same type of bullet at every level: that 
would be better than no bullets at all.

I should mention in closing that, before Steve realized my lack of ability 
with programming, he suggested the following as a way to insert bullets: 
"Bullets are trivial -- if a line begins with anything but a colon or 
whitespace then a colon, prepend an asterisk and a star to the line's 
first non-blank. I think you could even do it within VimOutliner with a 
command such as this:

:g!/\s*:/s/^(\s+)/\1* "

That line of symbols means nothing to me, but since I do have sufficient 
competence to copy and paste (in fact, this is one of my key areas of 
expertise when it comes to computing), I pasted that string into vim while 
viewing a test document in command mode. But it did nothing.

With respect to that string of characters, then, I need to ask whether I 
utilized it properly, or whether there might be some mistake there? Does 
it seem to others that this might offer a way of inserting bullets into a 
VO outline--most probably one and the same bullet symbol for all headline 
levels? As I said, the same bullet symbol at all levels, while less 
desirable than differing bullet symbols at differing levels, is 
nonetheless preferable to no bullets at all.

Any help with this bulleting/numbering query will be highly appreciated.

Thanks,
James
Jostein Berntsen | 17 Sep 18:38
Picon
Favicon
Gravatar

Latest updates

Latest updates at the development branch:

https://github.com/vimoutliner/vimoutliner/tree/development

Changelog:

https://github.com/vimoutliner/vimoutliner/blob/development/CHANGELOG

Jostein

Gmane