You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
VimOrganizer overrides my custom foldcolumn settings with its -- IMHO not very useful -- values: foldcolumn is set to 1 and FoldColumn is highlighted with ctermfg=0 ctermbg=0. I would like VimOrganizer not to mess with merely cosmetic settings which are not really required for its functionality.
The text was updated successfully, but these errors were encountered:
VimOrganizer overrides my custom foldcolumn settings with its -- IMHO not
very useful -- values: foldcolumn is set to 1 and FoldColumn is
highlighted with ctermfg=0 ctermbg=0. I would like VimOrganizer not to
mess with merely cosmetic settings which are not really required for its
functionality.
—
Reply to this email directly or view it on GitHubhttps://github.com//issues/58
.
seschwar -- I'll have to check into that, don't recall reason why
VimOrganizer changes foldcolumn. Out of town for next couple days but will
try to take a look. Not sure, but my guess is it's not something likely to
be changed. A lot of what VimOrganizer does is merely cosmetic, that's
what's needed for good experience using Vimorganizer. Easiest cure is to
run VimOrganizer docs in different Vim instance. Anyway, like I said I'll
try to take a look later this week.
My first guess is to why foldcolumns was changed is that the level info in
foldcolumns is misleading to anyone using a VimOrganizer document. If
that's all it is then it's probably an easy default to add option to
change, with end result that you hav e foldcolumn that is misleading
regarding the VimOrganizer doc . . . .
VimOrganizer overrides my custom foldcolumn settings with its -- IMHO not very useful -- values:
foldcolumn
is set to 1 andFoldColumn
is highlighted withctermfg=0 ctermbg=0
. I would like VimOrganizer not to mess with merely cosmetic settings which are not really required for its functionality.The text was updated successfully, but these errors were encountered: