Some highlight groups may have both settings and links. What does it depend from?
For instance, in the color scheme I am using (but I have noticed this in many others):
:hi StatusLineTerm
StatusLineTerm xxx term=bold,reverse cterm=bold ctermfg=0 ctermbg=121 gui=bold guifg=bg guibg=LightGreen
links to StatusLine
The color scheme links StatusLineTerm to StatusLine and the shown settings are those from StatusLine.
For other linked groups, however, only the link is shown, e.g.:
:hi QuickFixLine
QuickFixLine xxx links to Search
Why the difference?
I have noticed this because runtime/hitest.vim chokes at line 55 on highlight groups such as StatusLineTerm above, and spits a
line 55:
E348: No string under cursor
error. I have tried to contact its author a few days ago but I've got no answer so far.
Thanks,
Life.
--
--
You received this message from the "vim_use" maillist.
Do not top-post! Type your reply below the text you are replying to.
For more information, visit http://www.vim.org/maillist.php
---
You received this message because you are subscribed to the Google Groups "vim_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/vim_use/1DE53983-9319-402C-B434-86654746E8D2%40icloud.com.
For more options, visit https://groups.google.com/d/optout.
Sunday, June 2, 2019
Re: :help :check inconsistent with :check
John Little wrote:
> On Sunday, June 2, 2019 at 1:54:53 PM UTC+12, Tony Mechelynck wrote:
> > for this, line 827 of doc/tagsrch.txt would have had to be:
> > *che* *chec* *check* *checkp* *checkpa* *checkpat* *checkpath*
> > instead of just the first and last ones of these; similarly for _all_
> > other ex-commands, which I believe would have made the doc/tags file
> > much bigger.
>
> Extra tags would only be needed where there's ambiguity. I compiled a
> list; the middle column is what you get if you type the given at the :
> command prompt, and the third column is the topic you get if you ask
> for help for the given:
Thanks, that is very useful. I don't know how you generated this, but I
assume these are the useful ones.
>
> given | : | :help :
> --------+--------------+-------------
> arg | args | arga
> bre | brewind | break
> cab | cabbrev | cabclear
> cadd | caddbuffer | caddexpr
> chec | checkpath | checktime
> cne | cnext | cnewer
> cnor | cnoremap | cnoreabbrev
> cun | cunmap | cunabbrev
> diff | diffupdate | diffget
> doaut | doautocmd | doautoall
> end | endif | endfunction
> folddo | folddopen | folddoc
> inor | inoremap | inoreabbrev
> keep | keepmarks | keepalt
> ladd | laddbuffer | laddexpr
This one is the wrong way around, :ladd stands for :laddexpr.
> lfi | lfile | lfirst
> lge | lgetfile | lgetbuffer
> lma | lmap | lmake
> lock | lockmarks | lockvar
> mkvi | mkvimrc | mkview
> sfi | sfind | sfirst
> snore | snoremap | snoremenu
> ver | version | verbose
>
> One or two extra tags for each of these is not going to significantly
> add to vim's 10,000 or so.
>
> > :help :check<Tab> (with 'wildmenu' on) or :help :check<Ctrl-D> would
> > have shown you all helptags beginning with :check
>
> How would I have known to do that, when I did not know that there
> might be another command starting with "check"? I use the help when I
> don't know stuff, that's the point of it.
--
Ed's Radiator Shop: The Best Place in Town to Take a Leak.
/// Bram Moolenaar -- Bram@Moolenaar.net -- http://www.Moolenaar.net \\\
/// sponsor Vim, vote for features -- http://www.Vim.org/sponsor/ \\\
\\\ an exciting new programming language -- http://www.Zimbu.org ///
\\\ help me help AIDS victims -- http://ICCF-Holland.org ///
--
--
You received this message from the "vim_use" maillist.
Do not top-post! Type your reply below the text you are replying to.
For more information, visit http://www.vim.org/maillist.php
---
You received this message because you are subscribed to the Google Groups "vim_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/vim_use/201906021148.x52BmXEI007959%40masaka.moolenaar.net.
For more options, visit https://groups.google.com/d/optout.
> On Sunday, June 2, 2019 at 1:54:53 PM UTC+12, Tony Mechelynck wrote:
> > for this, line 827 of doc/tagsrch.txt would have had to be:
> > *che* *chec* *check* *checkp* *checkpa* *checkpat* *checkpath*
> > instead of just the first and last ones of these; similarly for _all_
> > other ex-commands, which I believe would have made the doc/tags file
> > much bigger.
>
> Extra tags would only be needed where there's ambiguity. I compiled a
> list; the middle column is what you get if you type the given at the :
> command prompt, and the third column is the topic you get if you ask
> for help for the given:
Thanks, that is very useful. I don't know how you generated this, but I
assume these are the useful ones.
>
> given | : | :help :
> --------+--------------+-------------
> arg | args | arga
> bre | brewind | break
> cab | cabbrev | cabclear
> cadd | caddbuffer | caddexpr
> chec | checkpath | checktime
> cne | cnext | cnewer
> cnor | cnoremap | cnoreabbrev
> cun | cunmap | cunabbrev
> diff | diffupdate | diffget
> doaut | doautocmd | doautoall
> end | endif | endfunction
> folddo | folddopen | folddoc
> inor | inoremap | inoreabbrev
> keep | keepmarks | keepalt
> ladd | laddbuffer | laddexpr
This one is the wrong way around, :ladd stands for :laddexpr.
> lfi | lfile | lfirst
> lge | lgetfile | lgetbuffer
> lma | lmap | lmake
> lock | lockmarks | lockvar
> mkvi | mkvimrc | mkview
> sfi | sfind | sfirst
> snore | snoremap | snoremenu
> ver | version | verbose
>
> One or two extra tags for each of these is not going to significantly
> add to vim's 10,000 or so.
>
> > :help :check<Tab> (with 'wildmenu' on) or :help :check<Ctrl-D> would
> > have shown you all helptags beginning with :check
>
> How would I have known to do that, when I did not know that there
> might be another command starting with "check"? I use the help when I
> don't know stuff, that's the point of it.
--
Ed's Radiator Shop: The Best Place in Town to Take a Leak.
/// Bram Moolenaar -- Bram@Moolenaar.net -- http://www.Moolenaar.net \\\
/// sponsor Vim, vote for features -- http://www.Vim.org/sponsor/ \\\
\\\ an exciting new programming language -- http://www.Zimbu.org ///
\\\ help me help AIDS victims -- http://ICCF-Holland.org ///
--
--
You received this message from the "vim_use" maillist.
Do not top-post! Type your reply below the text you are replying to.
For more information, visit http://www.vim.org/maillist.php
---
You received this message because you are subscribed to the Google Groups "vim_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/vim_use/201906021148.x52BmXEI007959%40masaka.moolenaar.net.
For more options, visit https://groups.google.com/d/optout.
Re: :help :check inconsistent with :check
John Little wrote:
> I just struck an inconsistency that had me confused.
>
> I was watching a steadily growing log file, and with autoread set, I used the command
>
> :check
>
> and nothing happened (but for a message I didn't understand). So I went to the help and ran
>
> :help :check
>
> and got the help for the command I thought I was running. Eventually I worked out that :check is actually :checkpath, and I should have used :checktime.
>
> But surely ":h :xyz" should give the help for ":xyz", but am I missing something?
The tag of :checkpath is ":che", which is the shortest form. Apparently
for ":help :check" it finds ":checkt" or ":checktime" first.
I'll add a tag for ":check" at ":checkpath", that will fix it.
--
hundred-and-one symptoms of being an internet addict:
83. Batteries in the TV remote now last for months.
/// Bram Moolenaar -- Bram@Moolenaar.net -- http://www.Moolenaar.net \\\
/// sponsor Vim, vote for features -- http://www.Vim.org/sponsor/ \\\
\\\ an exciting new programming language -- http://www.Zimbu.org ///
\\\ help me help AIDS victims -- http://ICCF-Holland.org ///
--
--
You received this message from the "vim_use" maillist.
Do not top-post! Type your reply below the text you are replying to.
For more information, visit http://www.vim.org/maillist.php
---
You received this message because you are subscribed to the Google Groups "vim_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/vim_use/201906021122.x52BMdJu003159%40masaka.moolenaar.net.
For more options, visit https://groups.google.com/d/optout.
> I just struck an inconsistency that had me confused.
>
> I was watching a steadily growing log file, and with autoread set, I used the command
>
> :check
>
> and nothing happened (but for a message I didn't understand). So I went to the help and ran
>
> :help :check
>
> and got the help for the command I thought I was running. Eventually I worked out that :check is actually :checkpath, and I should have used :checktime.
>
> But surely ":h :xyz" should give the help for ":xyz", but am I missing something?
The tag of :checkpath is ":che", which is the shortest form. Apparently
for ":help :check" it finds ":checkt" or ":checktime" first.
I'll add a tag for ":check" at ":checkpath", that will fix it.
--
hundred-and-one symptoms of being an internet addict:
83. Batteries in the TV remote now last for months.
/// Bram Moolenaar -- Bram@Moolenaar.net -- http://www.Moolenaar.net \\\
/// sponsor Vim, vote for features -- http://www.Vim.org/sponsor/ \\\
\\\ an exciting new programming language -- http://www.Zimbu.org ///
\\\ help me help AIDS victims -- http://ICCF-Holland.org ///
--
--
You received this message from the "vim_use" maillist.
Do not top-post! Type your reply below the text you are replying to.
For more information, visit http://www.vim.org/maillist.php
---
You received this message because you are subscribed to the Google Groups "vim_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/vim_use/201906021122.x52BMdJu003159%40masaka.moolenaar.net.
For more options, visit https://groups.google.com/d/optout.
Re: :help :check inconsistent with :check
On Sun, Jun 2, 2019 at 12:48 PM John Little <john.b.little@gmail.com> wrote:
> > :help :check<Tab> (with 'wildmenu' on) or :help :check<Ctrl-D> would
> > have shown you all helptags beginning with :check
>
> How would I have known to do that, when I did not know that there might be another command starting with "check"? I use the help when I don't know stuff, that's the point of it.
>
> Regards, John Little
Well, I suppose it's a question of how we relate to encyclopaedic
sources of information. When I was a little kid, I would spend hours
with the 7-volume dictionary (7 thick folio volumes IIRC); nowadays I
can spend hours going from subject to subject by following hotlinks in
the Wikipedia — or in the Vim help; and it proves to me how true was
the remark of Socrates: «The more I know, and the more I'm conscious
of how little I know».
How would you have known, when you didn't know there was another
comand starting with :check? Well, seeing that the help didn't jibe
with what you saw, you might have wondered if there weren't another
command starting with :check, and asked for a list — if you had known
how to; though the <Tab> key is used for more than one kind of
completion, and it is very useful.
Best regards,
Tony.
--
--
You received this message from the "vim_use" maillist.
Do not top-post! Type your reply below the text you are replying to.
For more information, visit http://www.vim.org/maillist.php
---
You received this message because you are subscribed to the Google Groups "vim_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/vim_use/CAJkCKXsj-9xmssmp-grApFQmmD5gLYUGPy_C0_jUuj-ttpPsnQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.
> > :help :check<Tab> (with 'wildmenu' on) or :help :check<Ctrl-D> would
> > have shown you all helptags beginning with :check
>
> How would I have known to do that, when I did not know that there might be another command starting with "check"? I use the help when I don't know stuff, that's the point of it.
>
> Regards, John Little
Well, I suppose it's a question of how we relate to encyclopaedic
sources of information. When I was a little kid, I would spend hours
with the 7-volume dictionary (7 thick folio volumes IIRC); nowadays I
can spend hours going from subject to subject by following hotlinks in
the Wikipedia — or in the Vim help; and it proves to me how true was
the remark of Socrates: «The more I know, and the more I'm conscious
of how little I know».
How would you have known, when you didn't know there was another
comand starting with :check? Well, seeing that the help didn't jibe
with what you saw, you might have wondered if there weren't another
command starting with :check, and asked for a list — if you had known
how to; though the <Tab> key is used for more than one kind of
completion, and it is very useful.
Best regards,
Tony.
--
--
You received this message from the "vim_use" maillist.
Do not top-post! Type your reply below the text you are replying to.
For more information, visit http://www.vim.org/maillist.php
---
You received this message because you are subscribed to the Google Groups "vim_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/vim_use/CAJkCKXsj-9xmssmp-grApFQmmD5gLYUGPy_C0_jUuj-ttpPsnQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.
Re: Vim terminal syntax highlights
On Sun, Jun 02, 2019 at 01:18:35AM -0700, Tatenda Biti wrote:
> Might be a silly question. But why doesn't vim's terminal on windows 10 have syntax highlighting like neovim
it probably depends on the colorscheme you use (what and how your syntax
is displayed) and on a line in your .vimrc: `syntax enable'
see also `:help syntax' for further instructions on the use and
possibilities.
//meine
--
--
You received this message from the "vim_use" maillist.
Do not top-post! Type your reply below the text you are replying to.
For more information, visit http://www.vim.org/maillist.php
---
You received this message because you are subscribed to the Google Groups "vim_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/vim_use/20190602105953.GB931%40trackstand.
For more options, visit https://groups.google.com/d/optout.
> Might be a silly question. But why doesn't vim's terminal on windows 10 have syntax highlighting like neovim
it probably depends on the colorscheme you use (what and how your syntax
is displayed) and on a line in your .vimrc: `syntax enable'
see also `:help syntax' for further instructions on the use and
possibilities.
//meine
--
--
You received this message from the "vim_use" maillist.
Do not top-post! Type your reply below the text you are replying to.
For more information, visit http://www.vim.org/maillist.php
---
You received this message because you are subscribed to the Google Groups "vim_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/vim_use/20190602105953.GB931%40trackstand.
For more options, visit https://groups.google.com/d/optout.
Re: :help :check inconsistent with :check
On Sunday, June 2, 2019 at 1:54:53 PM UTC+12, Tony Mechelynck wrote:
> for this, line 827 of doc/tagsrch.txt would have had to be:
> *che* *chec* *check* *checkp* *checkpa* *checkpat* *checkpath*
> instead of just the first and last ones of these; similarly for _all_
> other ex-commands, which I believe would have made the doc/tags file
> much bigger.
Extra tags would only be needed where there's ambiguity. I compiled a list; the middle column is what you get if you type the given at the : command prompt, and the third column is the topic you get if you ask for help for the given:
given | : | :help :
--------+--------------+-------------
arg | args | arga
bre | brewind | break
cab | cabbrev | cabclear
cadd | caddbuffer | caddexpr
chec | checkpath | checktime
cne | cnext | cnewer
cnor | cnoremap | cnoreabbrev
cun | cunmap | cunabbrev
diff | diffupdate | diffget
doaut | doautocmd | doautoall
end | endif | endfunction
folddo | folddopen | folddoc
inor | inoremap | inoreabbrev
keep | keepmarks | keepalt
ladd | laddbuffer | laddexpr
lfi | lfile | lfirst
lge | lgetfile | lgetbuffer
lma | lmap | lmake
lock | lockmarks | lockvar
mkvi | mkvimrc | mkview
sfi | sfind | sfirst
snore | snoremap | snoremenu
ver | version | verbose
One or two extra tags for each of these is not going to significantly add to vim's 10,000 or so.
> :help :check<Tab> (with 'wildmenu' on) or :help :check<Ctrl-D> would
> have shown you all helptags beginning with :check
How would I have known to do that, when I did not know that there might be another command starting with "check"? I use the help when I don't know stuff, that's the point of it.
Regards, John Little
--
--
You received this message from the "vim_use" maillist.
Do not top-post! Type your reply below the text you are replying to.
For more information, visit http://www.vim.org/maillist.php
---
You received this message because you are subscribed to the Google Groups "vim_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/vim_use/ffb53d57-66be-413a-a978-20a05f48c19a%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
> for this, line 827 of doc/tagsrch.txt would have had to be:
> *che* *chec* *check* *checkp* *checkpa* *checkpat* *checkpath*
> instead of just the first and last ones of these; similarly for _all_
> other ex-commands, which I believe would have made the doc/tags file
> much bigger.
Extra tags would only be needed where there's ambiguity. I compiled a list; the middle column is what you get if you type the given at the : command prompt, and the third column is the topic you get if you ask for help for the given:
given | : | :help :
--------+--------------+-------------
arg | args | arga
bre | brewind | break
cab | cabbrev | cabclear
cadd | caddbuffer | caddexpr
chec | checkpath | checktime
cne | cnext | cnewer
cnor | cnoremap | cnoreabbrev
cun | cunmap | cunabbrev
diff | diffupdate | diffget
doaut | doautocmd | doautoall
end | endif | endfunction
folddo | folddopen | folddoc
inor | inoremap | inoreabbrev
keep | keepmarks | keepalt
ladd | laddbuffer | laddexpr
lfi | lfile | lfirst
lge | lgetfile | lgetbuffer
lma | lmap | lmake
lock | lockmarks | lockvar
mkvi | mkvimrc | mkview
sfi | sfind | sfirst
snore | snoremap | snoremenu
ver | version | verbose
One or two extra tags for each of these is not going to significantly add to vim's 10,000 or so.
> :help :check<Tab> (with 'wildmenu' on) or :help :check<Ctrl-D> would
> have shown you all helptags beginning with :check
How would I have known to do that, when I did not know that there might be another command starting with "check"? I use the help when I don't know stuff, that's the point of it.
Regards, John Little
--
--
You received this message from the "vim_use" maillist.
Do not top-post! Type your reply below the text you are replying to.
For more information, visit http://www.vim.org/maillist.php
---
You received this message because you are subscribed to the Google Groups "vim_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/vim_use/ffb53d57-66be-413a-a978-20a05f48c19a%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Vim terminal syntax highlights
Might be a silly question. But why doesn't vim's terminal on windows 10 have syntax highlighting like neovim
--
--
You received this message from the "vim_use" maillist.
Do not top-post! Type your reply below the text you are replying to.
For more information, visit http://www.vim.org/maillist.php
---
You received this message because you are subscribed to the Google Groups "vim_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/vim_use/379e1f72-7e1b-47f5-935d-acb8a8c45bbb%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
--
--
You received this message from the "vim_use" maillist.
Do not top-post! Type your reply below the text you are replying to.
For more information, visit http://www.vim.org/maillist.php
---
You received this message because you are subscribed to the Google Groups "vim_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/vim_use/379e1f72-7e1b-47f5-935d-acb8a8c45bbb%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Subscribe to:
Posts (Atom)