On Mon, Jun 05, 2006 at 03:02:26AM EDT, A.J.Mechelynck wrote:
> cga2000 wrote:
> >On Sun, Jun 04, 2006 at 08:50:18PM EDT, A.J.Mechelynck wrote:
> >
> >>cga2000 wrote:
> >>
> >>>On Sun, Jun 04, 2006 at 03:11:10PM EDT, A.J.Mechelynck wrote:
> >>>
> >>>[...]
> >>>
> >>>
> >>>>Note that the same highlight group also governs the @ or @@@ for a
> >>>>partial line at the end of a window, and possibly other things too.
> >>>>
> >>>>
> >>>I had thought of that while experimenting - although I have no idea
> >>>what the "@" and "@@@" are .. or the "partial lines".
> >>>
> >>>
> >>When using 'wrap', one "file line" can be wrapped onto several "screen
> >>lines". When the last "file line" in a buffer window overflows below the
> >>bottom of the window, then one of two things can happen:
> >>
> >>- if 'display' includes "lastline", the bottom three characters at lower
> >>right of the window are replaced by @@@, the rest of that "file line" is
> >>displayed, or as much of it as fits into the window.
> >>- Otherwise (the default) the last "file line" in the window is replaced
> >>by as many "screen lines" as necessary consisting of @ at left, the rest
> >>empty.
> >>
> >>
> >Thanks. Great explanation.
> >
> >
> >>>Is there any way I can query vim to find out what a group (?) like
> >>>NonText actually covers?
> >>>
> >>>
> >>:help NonText
> >>
> >>
> >Looks like setting it to "invisible" the way you recommend is fairly
> >harmless. Hope it doesn't come back and bite me when I've forgotten all
> >about it.
> >
> >I think I should stick these doubtful customizations of mine in some
> >separate file rather than modifying individual colorschemes. I've just
> >tested:
> >
> >:set FoldColumn=2
> >:hi Foldcolumn ctermbg=black
> >
> >.. and it adds a 2-column margin to the left of my display and thought
> >I could add these to my .vimrc but then this will be lost whenever I
> >change colorscheme on the fly.
> >
>
> About 'foldcolumn', you can keep that in your vimrc, or, if you want it
> for some particular filetype only, create a filetype-plugin (for
> instance for HTML, in $HOME/vimfiles/after/ftplugin/html.vim for
> Windows, $HOME/.vim/after/ftplugin/html.vim for Unix). An "after-plugin"
> means it runs after the standard plugin, which you can let run its course.
so much stuff in vim. I'll make sure I remember the general idea at
least.
>
> About :hi statements, you can set up your own colorscheme: copy some
> existing colorscheme (for the default colors,
> $VIMRUNTIME/colors/default.vim) to your "colors" directory under another
> name (for instance $HOME/vimfiles/colors/cga2000.vim for Windows,
> $HOME/.vim/colors/cga2000.vim for Unix), modify it there, and add
> "colorscheme cga2000" to your vimrc. You can set colors for all three
> modes (B&W console, color console, GUI) in a single colorscheme by using
> the appropriate term= cterm= ctermfg= ctermbg= gui= guifg= guibg=
> arguments. Normally you will stick to a single colorscheme which "fits
> you best" so this shouldn't be a problem.
>
> Note that anything in or under $VIMRUNTIME can be added, deleted or
> modified silently by any upgrade, so it is best not to change anything
> there -- any changes you make could disappear without warning at an
> unspecified future time.
.. isn't there a way one could add the customization - once it's duly
tested - to a system-wide tree so other users of the system could
benefit by it? Some sort of $VIMRUNTIME/local so-to-speak..?
>
> >
> >>>[...]
> >>>
> >awful thing about vim is that the more you learn the more you realize
> >how complex it is and how much more there is to learn.. But thanks to
> >all the help I am getting on this list I am now a bit more able to find
> >my own answers. The help files are great but it's really a maze.. You
> >could spend hours and hours just following these tags.. Sometimes it
> >gets to the point where I can't remember what I was looking for in the
> >first place.
> >
> >:-)
> >
> >>Best regards,
> >>Tony.
> >>
> >
> >Thanks,
> >
> >cga
> >
> >
> >
> Vim is a complex (read: powerful) tool, and it does take some time to
> learn all its capabilities.
like.. forever..? :-)
sometimes I think Bram himself cannot know everything that's in it..
> It is also the best-documented piece of
> software that I've ever seen (hence the needle-and-haystack problem), it
> has great tools for searching its own help (such as helptag completion
> and the :helpgrep command) and if there is something you still can't
> find in the help (usually it is there but you can't find it) there are
> these mailing lists which I've found very useful too; nowadays I take my
> part of answering questions but I am still learning, mostly from the
> questions that other people are asking and to which I don't know the answer.
>
> see
> :help :help
> :help {subject}
> the above is not just any subject but the word "subject" itself, between
> braces
> :help CTRL-]
> :help :helptags
>
> and the "wild" options, some of which we spoke about in an earlier post
> on this thread,
> :help 'wildchar'
> :help 'wildmenu'
> :help 'wildmode'
> :help 'wildoptions'
>
I think I need to schedule a sabbatical day once a month to work on
improving my vim skills. Jotted :helpgrep on a piece of paper.. sounds
promising. All the others you mention I already use.. though probably
not to their fullest extent.
Thanks,
cga
