Correct objects behavior

classic Classic list List threaded Threaded
7 messages Options
Reply | Threaded
Open this post in threaded view
|

Correct objects behavior

Claus Atzenbeck
Hi,

I have problems with vimoutliner (v0.3.4 running on vim 7) objects
starting with ":", ";", and "<".

For example, each line of the following text block is supposed to start
with ":", but after the automatic line wrap, the second line did not get
a colon inserted:

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Test
        : alsdkf jalsdkf jasdlfkajsd flaskdfj asldfkajs df laksdf jalsdkfja
        sdflkadfj asldfkajds flasdkfja sdlfkasdj falsdfkadjs
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

The next two examples are interesting, because neither "<" nor ";"
should wrap text, but both do:

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Test
        < alsdkfj alsdfkaj dslaksdjf alsdkfj asldkfa jsdlfkadsj flasdkfj asdlkfaj
        sdlfkasdj flasdkfj asdlfkda j

Test
        ; alsdkfja sldkfasjd laksdfj alsdkfa jsdflkasdfj alsdfkaj sdflkasdjf
        lasdkfj asldkf akj
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

The next one is the only one which works correctly, possibly caused by
some other settings than the ones in vimoutliner (since ">" also is used
for e-mail quotes):

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Test
        > lasdk fjlasdkfj alsdkfj alksdf jalsdf jalskdfj asdlkfj alskdf jalsdkf
        > jasldkfj alsdkjf lkas djflkds jfla sjdflk ajldfkj alsdkjf
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

Any idea what is wrong? ~/.vimoutlinerrc does not set anything wrap
related. setlocal nowrap does not help either.

Claus
_______________________________________________
VimOutliner mailing list
[hidden email]
http://www.lists.vimoutliner.org/mailman/listinfo/vimoutliner
Reply | Threaded
Open this post in threaded view
|

Re: Correct objects behavior

Claus Atzenbeck
Hello:

I played around with VimOutliner 0.3.4 on Vim 7. However, as I wrote in
an earlier posting, I do not manage to deal with the text body parts,
which show leading ":".

In ":help outline" I found what I have been looking for:

~~~~~~~~~~~~~~~~~~~~
Lines starting with a colon and space word-wrap
     Lines starting with colons are body text. They should
     word wrap and should be a special color (typically
     green, but it can vary). Verify that paragraphs of body
     text can be reformatted with the Vim gq commands.
~~~~~~~~~~~~~~~~~~~~

If I understand this correctly, line wrapping should be on, but there
also should be a leading ":" at the next line automatically inserted.
Additionally, reformatting using gq should not mess up the leading ":".
Right?

Both do not work for me: After a line break, there is no leading ":"
inserted. Also, gq reformats also colons as if their would be normal
text, which may make them appear anywhere, but not necessarily at the
lines' leading position.

Am I the only one with this behavior?

Another question: When writing a heading line in VimOutliner, the line
breaks automatically and starts a second line at the same level. Is this
intended?

Thanks!
Claus
_______________________________________________
VimOutliner mailing list
[hidden email]
http://www.lists.vimoutliner.org/mailman/listinfo/vimoutliner
Reply | Threaded
Open this post in threaded view
|

Re: Correct objects behavior

Steve Litt
On Tuesday 13 March 2007 06:06, Claus Atzenbeck wrote:

> Hello:
>
> I played around with VimOutliner 0.3.4 on Vim 7. However, as I wrote in
> an earlier posting, I do not manage to deal with the text body parts,
> which show leading ":".
>
> In ":help outline" I found what I have been looking for:
>
> ~~~~~~~~~~~~~~~~~~~~
> Lines starting with a colon and space word-wrap
>      Lines starting with colons are body text. They should
>      word wrap and should be a special color (typically
>      green, but it can vary). Verify that paragraphs of body
>      text can be reformatted with the Vim gq commands.
> ~~~~~~~~~~~~~~~~~~~~
>
> If I understand this correctly, line wrapping should be on, but there
> also should be a leading ":" at the next line automatically inserted.
> Additionally, reformatting using gq should not mess up the leading ":".
> Right?
>
> Both do not work for me: After a line break, there is no leading ":"
> inserted. Also, gq reformats also colons as if their would be normal
> text, which may make them appear anywhere, but not necessarily at the
> lines' leading position.
>
> Am I the only one with this behavior?

It's certainly not normal. Do your files end in .otl? If not, that would
explain it.

How did you install VO -- with the install script, or manually? Are you
running it on Linux?

>
> Another question: When writing a heading line in VimOutliner, the line
> breaks automatically and starts a second line at the same level. Is this
> intended?

No -- that's the opposite of what's intended. Body text should word wrap,
normal headlines should not.

Steve

Steve Litt
Author: Universal Troubleshooting Process books and courseware
http://www.troubleshooters.com/
_______________________________________________
VimOutliner mailing list
[hidden email]
http://www.lists.vimoutliner.org/mailman/listinfo/vimoutliner
Reply | Threaded
Open this post in threaded view
|

Re: Correct objects behavior

Noel Henson
In reply to this post by Claus Atzenbeck
Claus,

It sounds like your formatting string has been modified. What does 'set fo'
yield?

Noel

On Sunday 11 March 2007 12:23, Claus Atzenbeck wrote:

> Hi,
>
> I have problems with vimoutliner (v0.3.4 running on vim 7) objects
> starting with ":", ";", and "<".
>
> For example, each line of the following text block is supposed to start
> with ":", but after the automatic line wrap, the second line did not get
> a colon inserted:
>
> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
> Test
>
> : alsdkf jalsdkf jasdlfkajsd flaskdfj asldfkajs df laksdf jalsdkfja
>
> sdflkadfj asldfkajds flasdkfja sdlfkasdj falsdfkadjs
> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
>
> The next two examples are interesting, because neither "<" nor ";"
> should wrap text, but both do:
>
> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
> Test
> < alsdkfj alsdfkaj dslaksdjf alsdkfj asldkfa jsdlfkadsj flasdkfj
> asdlkfaj sdlfkasdj flasdkfj asdlfkda j
>
> Test
> ; alsdkfja sldkfasjd laksdfj alsdkfa jsdflkasdfj alsdfkaj sdflkasdjf
> lasdkfj asldkf akj
> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
>
> The next one is the only one which works correctly, possibly caused by
> some other settings than the ones in vimoutliner (since ">" also is used
> for e-mail quotes):
>
> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
> Test
>
> > lasdk fjlasdkfj alsdkfj alksdf jalsdf jalskdfj asdlkfj alskdf jalsdkf
> > jasldkfj alsdkjf lkas djflkds jfla sjdflk ajldfkj alsdkjf
>
> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
>
> Any idea what is wrong? ~/.vimoutlinerrc does not set anything wrap
> related. setlocal nowrap does not help either.
>
> Claus
> _______________________________________________
> VimOutliner mailing list
> [hidden email]
> http://www.lists.vimoutliner.org/mailman/listinfo/vimoutliner

--

------------------------------------------------------------------
  Noel Henson
  www.noels-lab.com Chips, firmware and embedded systems
  www.vimoutliner.org Work fast. Think well.

_______________________________________________
VimOutliner mailing list
[hidden email]
http://www.lists.vimoutliner.org/mailman/listinfo/vimoutliner
Reply | Threaded
Open this post in threaded view
|

Re: Correct objects behavior

Claus Atzenbeck
On Tue, 13 Mar 2007, Noel Henson wrote:

> It sounds like your formatting string has been modified. What does 'set fo'
> yield?

Now it becomes interesting: I found out that VimOutliner's behavior
changes when an .otl file is opened versus a new file is created:

After opening an existing .otl file:
:set fo
  formatoptions=tcql

After creating a new file (via "vim newfile.otl"):
:set fo
  formatoptions=crqno

This can be reproduced.

I also found a file "~/.vim/view/~=+Documents=+outline.otl=" (apparently
belonging to my outline file ~/Documents/outline.otl), of which I don't
know where it came from. This file has "setlocal formatoptions=tcql",
but removing the complete directory did not change anything.

Any idea why VimOutliner behaves so strange?
Claus
_______________________________________________
VimOutliner mailing list
[hidden email]
http://www.lists.vimoutliner.org/mailman/listinfo/vimoutliner
Reply | Threaded
Open this post in threaded view
|

Re: Correct objects behavior

Claus Atzenbeck
In reply to this post by Steve Litt
On Tue, 13 Mar 2007, Steve Litt wrote:

> It's certainly not normal. Do your files end in .otl? If not, that would
> explain it.

Yes, they all do.

> How did you install VO -- with the install script, or manually? Are you
> running it on Linux?

I installed it twice. The first time I don't remember, the second one I
used the script.

I use VimOutliner 0.3.4 on Mac OS 10.4.8 (bash 3).

> No -- that's the opposite of what's intended. Body text should word wrap,
> normal headlines should not.

In my previous mail I mentioned a strange behavior where VimOutliner
works correctly on new files, but not on files loaded from the hard
drive. This also includes the wrapping of headlines.

Cheers,
Claus
_______________________________________________
VimOutliner mailing list
[hidden email]
http://www.lists.vimoutliner.org/mailman/listinfo/vimoutliner
Reply | Threaded
Open this post in threaded view
|

Re: Correct objects behavior

Claus Atzenbeck
In reply to this post by Claus Atzenbeck
On Tue, 13 Mar 2007, Claus Atzenbeck wrote:

> Now it becomes interesting: I found out that VimOutliner's behavior
> changes when an .otl file is opened versus a new file is created:

I solved the problem. I have overseen a line in my .vimrc:

    autocmd BufRead * set formatoptions=tcql nocindent comments&

Deleting this line (among some others) solved the problem.

Anyway, thanks to anyone replying to my problem.

Cheers,
Claus
_______________________________________________
VimOutliner mailing list
[hidden email]
http://www.lists.vimoutliner.org/mailman/listinfo/vimoutliner