Hi all,
I'm not sure when this started, but for some Python files there's a
noticeable lag due to syntax highlighting.
For example, using O to open a new line can take up to a few hundreds
of ms at some places of the file while it's instantaneous at some
other places of the same file. I say it's caused by syntax
highlighting because disabling it solves the issue. I couldn't find a
pattern explaining why some parts are slower.
The file is not a big one (457 lines / 17kB), its doesn't have long
lines (max is around 250 chars) and I'm using the syntax file provided
by Vim, not a custom one. I don't use any plugins at all (related to
Python or not).
I tried using :syntime (i.e., on / off / report) but I couldn't spot a
difference between a 'fast' place and a 'slow' place. I may not have
used it properly.
I'm using a huge 8.0.19 build on a 64 bits Debian Jessie. I'm using
Vim in a Gnome terminal, I don't use GVim.
Any suggestions where to look for?
Thanks.
--
--
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.
For more options, visit https://groups.google.com/d/optout.
Friday, September 30, 2016
Re: syntax match bug: 'keepend' not officially supported, but required in some cases
Brett Stahlman wrote:
> The syntax documentation suggests that the 'keepend' argument applies
> only to syntax regions, not syntax matches. But if I highlight a
> buffer containing only the following line...
>
> ABCDE
>
> ...with the following syntax definitions...
>
> syn match A /A/
> syn match Inside /[A-Z]\+/ transparent contained containedin=A
> hi A guifg=blue
>
> ...the match group "A" extends (apparently incorrectly) from A through
> E, though its pattern matches only the "A". Stranger still, one
> additional nested "Inside" group is recognized in each successive
> letter. I.e., "Inside" is contained within "Inside", in spite of the
> `containedin=A'. Thus, running synstack on successive characters, I
> see...
>
> -- cursor on A --
> A
> Inside
> -- cursor on B --
> A
> Inside
> Inside
> -- cursor on C --
> A
> Inside
> Inside
> Inside
>
>
> I can fix the problem by adding the 'keepend' argument to the
> definition for match group "A", but the "keepend" is highlighted as an
> error by the vim syntax, and the help on :syn-match gives me no reason
> to believe the argument should be supported.
>
Hello:
Since the help will be changed to reflect keepend being allowed at the
end of a match... well, try
http://www.drchip.org/astronaut/vim/index.html#SYNTAX_VIM for an update
to the highlighting thereof.
Regards,
Chip Campbell
--
--
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.
For more options, visit https://groups.google.com/d/optout.
> The syntax documentation suggests that the 'keepend' argument applies
> only to syntax regions, not syntax matches. But if I highlight a
> buffer containing only the following line...
>
> ABCDE
>
> ...with the following syntax definitions...
>
> syn match A /A/
> syn match Inside /[A-Z]\+/ transparent contained containedin=A
> hi A guifg=blue
>
> ...the match group "A" extends (apparently incorrectly) from A through
> E, though its pattern matches only the "A". Stranger still, one
> additional nested "Inside" group is recognized in each successive
> letter. I.e., "Inside" is contained within "Inside", in spite of the
> `containedin=A'. Thus, running synstack on successive characters, I
> see...
>
> -- cursor on A --
> A
> Inside
> -- cursor on B --
> A
> Inside
> Inside
> -- cursor on C --
> A
> Inside
> Inside
> Inside
>
>
> I can fix the problem by adding the 'keepend' argument to the
> definition for match group "A", but the "keepend" is highlighted as an
> error by the vim syntax, and the help on :syn-match gives me no reason
> to believe the argument should be supported.
>
Hello:
Since the help will be changed to reflect keepend being allowed at the
end of a match... well, try
http://www.drchip.org/astronaut/vim/index.html#SYNTAX_VIM for an update
to the highlighting thereof.
Regards,
Chip Campbell
--
--
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.
For more options, visit https://groups.google.com/d/optout.
Thursday, September 29, 2016
Re: syntax match bug: 'keepend' not officially supported, but required in some cases
On Thu, Sep 29, 2016 at 12:09 PM, Bram Moolenaar <Bram@moolenaar.net> wrote:
>
> Brett Stahlman wrote:
>
>> The syntax documentation suggests that the 'keepend' argument applies
>> only to syntax regions, not syntax matches. But if I highlight a
>> buffer containing only the following line...
>>
>> ABCDE
>>
>> ...with the following syntax definitions...
>>
>> syn match A /A/
>> syn match Inside /[A-Z]\+/ transparent contained containedin=A
>> hi A guifg=blue
>>
>> ...the match group "A" extends (apparently incorrectly) from A through
>> E, though its pattern matches only the "A". Stranger still, one
>> additional nested "Inside" group is recognized in each successive
>> letter. I.e., "Inside" is contained within "Inside", in spite of the
>> `containedin=A'. Thus, running synstack on successive characters, I
>> see...
>>
>> -- cursor on A --
>> A
>> Inside
>> -- cursor on B --
>> A
>> Inside
>> Inside
>> -- cursor on C --
>> A
>> Inside
>> Inside
>> Inside
>>
>>
>> I can fix the problem by adding the 'keepend' argument to the
>> definition for match group "A", but the "keepend" is highlighted as an
>> error by the vim syntax, and the help on :syn-match gives me no reason
>> to believe the argument should be supported.
>
> Yes, the "keepend" actually works, although it's not documented. I'll
> add a note in the documentation.
Thanks.
>
>> Here are the results of synstack() with the following, "fixed" definition for A:
>> syn match A /A/ keepend
>>
>> -- cursor on A --
>> A
>> Inside
>> -- cursor on B --
>> -- cursor on C --
>>
>> Is 'keepend' meant to be supported for syn-match? The purpose of
>> 'keepend' is to prevent a nested group from obscuring a match with a
>> containing group's "end pattern". Although a match group has no
>> explicit end pattern, the principle of checking for the end of the
>> match pattern certainly still applies, so I suppose it makes sense
>> that 'keepend' would be accepted for both syn-match and syn-region. If
>> that is the intent, then the documentation needs fixing.
>>
>> As for the infinitely nested "Inside" groups, I can't account for
>> that, and suspect it's a bug, but perhaps I'm misunderstanding
>> something about contained and containedin?
>
> This is actually working as intended. When using a transparent item,
> checking for contained items ignores that transparent item. So the
> "containedin=A" applies every time.
>
> This can be avoided by add "contains=NONE to the Inside item:
>
> syn match Inside /[A-Z]\+/ transparent contained containedin=A contains=NONE
Hmm... I see it now:
"The "contains=" argument is also inherited from the item it is contained in..."
Excluding the transparent item itself from the inherited list might
have produced less surprising behavior, but I guess this is sort of an
uncommon corner case, and I agree that Vim's behavior is consistent
with the documentation.
Thanks for looking into it.
Brett Stahlman
>
> --
> A mathematician is a device for turning coffee into theorems.
> Paul Erdos
> A computer programmer is a device for turning coffee into bugs.
> Bram Moolenaar
>
> /// 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.
For more options, visit https://groups.google.com/d/optout.
>
> Brett Stahlman wrote:
>
>> The syntax documentation suggests that the 'keepend' argument applies
>> only to syntax regions, not syntax matches. But if I highlight a
>> buffer containing only the following line...
>>
>> ABCDE
>>
>> ...with the following syntax definitions...
>>
>> syn match A /A/
>> syn match Inside /[A-Z]\+/ transparent contained containedin=A
>> hi A guifg=blue
>>
>> ...the match group "A" extends (apparently incorrectly) from A through
>> E, though its pattern matches only the "A". Stranger still, one
>> additional nested "Inside" group is recognized in each successive
>> letter. I.e., "Inside" is contained within "Inside", in spite of the
>> `containedin=A'. Thus, running synstack on successive characters, I
>> see...
>>
>> -- cursor on A --
>> A
>> Inside
>> -- cursor on B --
>> A
>> Inside
>> Inside
>> -- cursor on C --
>> A
>> Inside
>> Inside
>> Inside
>>
>>
>> I can fix the problem by adding the 'keepend' argument to the
>> definition for match group "A", but the "keepend" is highlighted as an
>> error by the vim syntax, and the help on :syn-match gives me no reason
>> to believe the argument should be supported.
>
> Yes, the "keepend" actually works, although it's not documented. I'll
> add a note in the documentation.
Thanks.
>
>> Here are the results of synstack() with the following, "fixed" definition for A:
>> syn match A /A/ keepend
>>
>> -- cursor on A --
>> A
>> Inside
>> -- cursor on B --
>> -- cursor on C --
>>
>> Is 'keepend' meant to be supported for syn-match? The purpose of
>> 'keepend' is to prevent a nested group from obscuring a match with a
>> containing group's "end pattern". Although a match group has no
>> explicit end pattern, the principle of checking for the end of the
>> match pattern certainly still applies, so I suppose it makes sense
>> that 'keepend' would be accepted for both syn-match and syn-region. If
>> that is the intent, then the documentation needs fixing.
>>
>> As for the infinitely nested "Inside" groups, I can't account for
>> that, and suspect it's a bug, but perhaps I'm misunderstanding
>> something about contained and containedin?
>
> This is actually working as intended. When using a transparent item,
> checking for contained items ignores that transparent item. So the
> "containedin=A" applies every time.
>
> This can be avoided by add "contains=NONE to the Inside item:
>
> syn match Inside /[A-Z]\+/ transparent contained containedin=A contains=NONE
Hmm... I see it now:
"The "contains=" argument is also inherited from the item it is contained in..."
Excluding the transparent item itself from the inherited list might
have produced less surprising behavior, but I guess this is sort of an
uncommon corner case, and I agree that Vim's behavior is consistent
with the documentation.
Thanks for looking into it.
Brett Stahlman
>
> --
> A mathematician is a device for turning coffee into theorems.
> Paul Erdos
> A computer programmer is a device for turning coffee into bugs.
> Bram Moolenaar
>
> /// 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.
For more options, visit https://groups.google.com/d/optout.
Re: How to anable lua for vim?
AM, <Meino.Cramer@gmx.de> wrote:
> Hi,
>
> To enable lua for vim I run configure as follows:
>
> ./configure --prefix=/usr/local --sysconfdir=/etc/vim --with-features=huge --with-luainterp=dynamic --with-lua-prefix=/usr/bin --enable-luainterp=yes --enable-pythoninterp
>
> . Vim compiles fine. But doing 'vim --version' produces (besides other
> output '-lua' instead of the exspected '+lua'.
>
> What did I wrong ?
>
> Thank you very much for any help in advance! :)
>
> Cheers,
> Meino
Probably you're missing the liblua dev package. Not sure which
OS or distribution you use, but on Ubuntu something like this
should install it:
$ sudo apt-get install liblua5.3-dev
Try "apt-cache search liblua" if you use Ubuntu to see what
versions of liblua are available.
Then:
$ cd vim
$ rm src/auto/config.cache
$ configure --enable-luainterp=yes --with-features=huge
$ make -j4
$ sudo make install
--
--
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.
For more options, visit https://groups.google.com/d/optout.
> Hi,
>
> To enable lua for vim I run configure as follows:
>
> ./configure --prefix=/usr/local --sysconfdir=/etc/vim --with-features=huge --with-luainterp=dynamic --with-lua-prefix=/usr/bin --enable-luainterp=yes --enable-pythoninterp
>
> . Vim compiles fine. But doing 'vim --version' produces (besides other
> output '-lua' instead of the exspected '+lua'.
>
> What did I wrong ?
>
> Thank you very much for any help in advance! :)
>
> Cheers,
> Meino
Probably you're missing the liblua dev package. Not sure which
OS or distribution you use, but on Ubuntu something like this
should install it:
$ sudo apt-get install liblua5.3-dev
Try "apt-cache search liblua" if you use Ubuntu to see what
versions of liblua are available.
Then:
$ cd vim
$ rm src/auto/config.cache
$ configure --enable-luainterp=yes --with-features=huge
$ make -j4
$ sudo make install
--
--
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.
For more options, visit https://groups.google.com/d/optout.
Re: How to anable lua for vim?
Ben Fritz <fritzophrenic@gmail.com> [16-09-29 19:24]:
> On Wednesday, September 28, 2016 at 9:16:34 PM UTC-5, Meino.Cramer@gmx.de wrote:
> > Hi,
> >
> > To enable lua for vim I run configure as follows:
> >
> > ./configure --prefix=/usr/local --sysconfdir=/etc/vim --with-features=huge --with-luainterp=dynamic --with-lua-prefix=/usr/bin --enable-luainterp=yes --enable-pythoninterp
> >
> > . Vim compiles fine. But doing 'vim --version' produces (besides other
> > output '-lua' instead of the exspected '+lua'.
> >
> > What did I wrong ?
> >
> > Thank you very much for any help in advance! :)
> >
> > Cheers,
> > Meino
>
> What's the output from that configure command?
>
> --
> --
> 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.
> For more options, visit https://groups.google.com/d/optout.
Hi Ben,
I found the problem myself -- thank you to point me to the output:
The problem is, that lua is switched on with --enable-lua instead
of --with-* as many other options to configure.
Cheers
Meino
--
--
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.
For more options, visit https://groups.google.com/d/optout.
> On Wednesday, September 28, 2016 at 9:16:34 PM UTC-5, Meino.Cramer@gmx.de wrote:
> > Hi,
> >
> > To enable lua for vim I run configure as follows:
> >
> > ./configure --prefix=/usr/local --sysconfdir=/etc/vim --with-features=huge --with-luainterp=dynamic --with-lua-prefix=/usr/bin --enable-luainterp=yes --enable-pythoninterp
> >
> > . Vim compiles fine. But doing 'vim --version' produces (besides other
> > output '-lua' instead of the exspected '+lua'.
> >
> > What did I wrong ?
> >
> > Thank you very much for any help in advance! :)
> >
> > Cheers,
> > Meino
>
> What's the output from that configure command?
>
> --
> --
> 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.
> For more options, visit https://groups.google.com/d/optout.
Hi Ben,
I found the problem myself -- thank you to point me to the output:
The problem is, that lua is switched on with --enable-lua instead
of --with-* as many other options to configure.
Cheers
Meino
--
--
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.
For more options, visit https://groups.google.com/d/optout.
Re: How to anable lua for vim?
On Wednesday, September 28, 2016 at 9:16:34 PM UTC-5, Meino.Cramer@gmx.de wrote:
> Hi,
>
> To enable lua for vim I run configure as follows:
>
> ./configure --prefix=/usr/local --sysconfdir=/etc/vim --with-features=huge --with-luainterp=dynamic --with-lua-prefix=/usr/bin --enable-luainterp=yes --enable-pythoninterp
>
> . Vim compiles fine. But doing 'vim --version' produces (besides other
> output '-lua' instead of the exspected '+lua'.
>
> What did I wrong ?
>
> Thank you very much for any help in advance! :)
>
> Cheers,
> Meino
What's the output from that configure command?
--
--
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.
For more options, visit https://groups.google.com/d/optout.
> Hi,
>
> To enable lua for vim I run configure as follows:
>
> ./configure --prefix=/usr/local --sysconfdir=/etc/vim --with-features=huge --with-luainterp=dynamic --with-lua-prefix=/usr/bin --enable-luainterp=yes --enable-pythoninterp
>
> . Vim compiles fine. But doing 'vim --version' produces (besides other
> output '-lua' instead of the exspected '+lua'.
>
> What did I wrong ?
>
> Thank you very much for any help in advance! :)
>
> Cheers,
> Meino
What's the output from that configure command?
--
--
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.
For more options, visit https://groups.google.com/d/optout.
Re: syntax match bug: 'keepend' not officially supported, but required in some cases
Brett Stahlman wrote:
> The syntax documentation suggests that the 'keepend' argument applies
> only to syntax regions, not syntax matches. But if I highlight a
> buffer containing only the following line...
>
> ABCDE
>
> ...with the following syntax definitions...
>
> syn match A /A/
> syn match Inside /[A-Z]\+/ transparent contained containedin=A
> hi A guifg=blue
>
> ...the match group "A" extends (apparently incorrectly) from A through
> E, though its pattern matches only the "A". Stranger still, one
> additional nested "Inside" group is recognized in each successive
> letter. I.e., "Inside" is contained within "Inside", in spite of the
> `containedin=A'. Thus, running synstack on successive characters, I
> see...
>
> -- cursor on A --
> A
> Inside
> -- cursor on B --
> A
> Inside
> Inside
> -- cursor on C --
> A
> Inside
> Inside
> Inside
>
>
> I can fix the problem by adding the 'keepend' argument to the
> definition for match group "A", but the "keepend" is highlighted as an
> error by the vim syntax, and the help on :syn-match gives me no reason
> to believe the argument should be supported.
Yes, the "keepend" actually works, although it's not documented. I'll
add a note in the documentation.
> Here are the results of synstack() with the following, "fixed" definition for A:
> syn match A /A/ keepend
>
> -- cursor on A --
> A
> Inside
> -- cursor on B --
> -- cursor on C --
>
> Is 'keepend' meant to be supported for syn-match? The purpose of
> 'keepend' is to prevent a nested group from obscuring a match with a
> containing group's "end pattern". Although a match group has no
> explicit end pattern, the principle of checking for the end of the
> match pattern certainly still applies, so I suppose it makes sense
> that 'keepend' would be accepted for both syn-match and syn-region. If
> that is the intent, then the documentation needs fixing.
>
> As for the infinitely nested "Inside" groups, I can't account for
> that, and suspect it's a bug, but perhaps I'm misunderstanding
> something about contained and containedin?
This is actually working as intended. When using a transparent item,
checking for contained items ignores that transparent item. So the
"containedin=A" applies every time.
This can be avoided by add "contains=NONE to the Inside item:
syn match Inside /[A-Z]\+/ transparent contained containedin=A contains=NONE
--
A mathematician is a device for turning coffee into theorems.
Paul Erdos
A computer programmer is a device for turning coffee into bugs.
Bram Moolenaar
/// 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.
For more options, visit https://groups.google.com/d/optout.
> The syntax documentation suggests that the 'keepend' argument applies
> only to syntax regions, not syntax matches. But if I highlight a
> buffer containing only the following line...
>
> ABCDE
>
> ...with the following syntax definitions...
>
> syn match A /A/
> syn match Inside /[A-Z]\+/ transparent contained containedin=A
> hi A guifg=blue
>
> ...the match group "A" extends (apparently incorrectly) from A through
> E, though its pattern matches only the "A". Stranger still, one
> additional nested "Inside" group is recognized in each successive
> letter. I.e., "Inside" is contained within "Inside", in spite of the
> `containedin=A'. Thus, running synstack on successive characters, I
> see...
>
> -- cursor on A --
> A
> Inside
> -- cursor on B --
> A
> Inside
> Inside
> -- cursor on C --
> A
> Inside
> Inside
> Inside
>
>
> I can fix the problem by adding the 'keepend' argument to the
> definition for match group "A", but the "keepend" is highlighted as an
> error by the vim syntax, and the help on :syn-match gives me no reason
> to believe the argument should be supported.
Yes, the "keepend" actually works, although it's not documented. I'll
add a note in the documentation.
> Here are the results of synstack() with the following, "fixed" definition for A:
> syn match A /A/ keepend
>
> -- cursor on A --
> A
> Inside
> -- cursor on B --
> -- cursor on C --
>
> Is 'keepend' meant to be supported for syn-match? The purpose of
> 'keepend' is to prevent a nested group from obscuring a match with a
> containing group's "end pattern". Although a match group has no
> explicit end pattern, the principle of checking for the end of the
> match pattern certainly still applies, so I suppose it makes sense
> that 'keepend' would be accepted for both syn-match and syn-region. If
> that is the intent, then the documentation needs fixing.
>
> As for the infinitely nested "Inside" groups, I can't account for
> that, and suspect it's a bug, but perhaps I'm misunderstanding
> something about contained and containedin?
This is actually working as intended. When using a transparent item,
checking for contained items ignores that transparent item. So the
"containedin=A" applies every time.
This can be avoided by add "contains=NONE to the Inside item:
syn match Inside /[A-Z]\+/ transparent contained containedin=A contains=NONE
--
A mathematician is a device for turning coffee into theorems.
Paul Erdos
A computer programmer is a device for turning coffee into bugs.
Bram Moolenaar
/// 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.
For more options, visit https://groups.google.com/d/optout.
gvim - not finding gtk icons when starting
I have vim 7.4 installed on PC-BSD. When I start gvim from the command line, I see hundreds (at least 1024 because that's my scroll length) of lines like these:
/usr/home/afalanga/.config/qtcurve/gtk-icons:911: Unable to locate image file in pixmap_path: "16x16/actions/bookmarks-organize.png"
/usr/home/afalanga/.config/qtcurve/gtk-icons:912: Unable to locate image file in pixmap_path: "16x16/actions/bookmarks-organize.png"
/usr/home/afalanga/.config/qtcurve/gtk-icons:913: Unable to locate image file in pixmap_path: "32x32/actions/bookmarks-organize.png"
/usr/home/afalanga/.config/qtcurve/gtk-icons:914: Unable to locate image file in pixmap_path: "16x16/actions/bookmarks-organize.png"
Fontconfig warning: "local.conf", line 1093: saw number, expected matrix
gvim actually does start and function correctly. These errors, though, are highly annoying. Can anyone here help explain to me what is wrong, and more importantly, what I must do to correct?
Thanks,
Andy
--
--
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.
For more options, visit https://groups.google.com/d/optout.
/usr/home/afalanga/.config/qtcurve/gtk-icons:911: Unable to locate image file in pixmap_path: "16x16/actions/bookmarks-organize.png"
/usr/home/afalanga/.config/qtcurve/gtk-icons:912: Unable to locate image file in pixmap_path: "16x16/actions/bookmarks-organize.png"
/usr/home/afalanga/.config/qtcurve/gtk-icons:913: Unable to locate image file in pixmap_path: "32x32/actions/bookmarks-organize.png"
/usr/home/afalanga/.config/qtcurve/gtk-icons:914: Unable to locate image file in pixmap_path: "16x16/actions/bookmarks-organize.png"
Fontconfig warning: "local.conf", line 1093: saw number, expected matrix
gvim actually does start and function correctly. These errors, though, are highly annoying. Can anyone here help explain to me what is wrong, and more importantly, what I must do to correct?
Thanks,
Andy
--
--
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.
For more options, visit https://groups.google.com/d/optout.
Determine key binding used to call a mapping
Is there a way to obtain the mapping used to call a function from within that function (like with "v:operator")?
E.g. to reduce this
map vax :call SFunc(0)
map vix :call SFunc(1)
function SFunc(inner)
if a:inner
...
endif
endfunction
to something like this:
function SFunc()
if <???> == "i" (or "ix")
...
endif
endfunction
--
--
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.
For more options, visit https://groups.google.com/d/optout.
E.g. to reduce this
map vax :call SFunc(0)
map vix :call SFunc(1)
function SFunc(inner)
if a:inner
...
endif
endfunction
to something like this:
function SFunc()
if <???> == "i" (or "ix")
...
endif
endfunction
--
--
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.
For more options, visit https://groups.google.com/d/optout.
Wednesday, September 28, 2016
How to anable lua for vim?
Hi,
To enable lua for vim I run configure as follows:
./configure --prefix=/usr/local --sysconfdir=/etc/vim --with-features=huge --with-luainterp=dynamic --with-lua-prefix=/usr/bin --enable-luainterp=yes --enable-pythoninterp
. Vim compiles fine. But doing 'vim --version' produces (besides other
output '-lua' instead of the exspected '+lua'.
What did I wrong ?
Thank you very much for any help in advance! :)
Cheers,
Meino
--
--
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.
For more options, visit https://groups.google.com/d/optout.
To enable lua for vim I run configure as follows:
./configure --prefix=/usr/local --sysconfdir=/etc/vim --with-features=huge --with-luainterp=dynamic --with-lua-prefix=/usr/bin --enable-luainterp=yes --enable-pythoninterp
. Vim compiles fine. But doing 'vim --version' produces (besides other
output '-lua' instead of the exspected '+lua'.
What did I wrong ?
Thank you very much for any help in advance! :)
Cheers,
Meino
--
--
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.
For more options, visit https://groups.google.com/d/optout.
Re: vim & ctags: how to jump to the definition in new window
-----BEGIN PGP SIGNATURE-----
Comment: GPGTools - https://gpgtools.org
iQIcBAEBCgAGBQJX7GxFAAoJENZCakLuo2TNQWkP/Rx1X/e4ueEiiSG47V7Fhfw6
L1Y92/Lt0XzNr9eyNQZL6giYcxl1DyA/4Ylh7ZSFlS2eXNQtEH5xfpRn1VtBE2aK
1TiDCt0uBpFKOvN+E4+WViFa4rBZ6NPUjstsik3d2RwF8E70mB8uz9FIuoQT7CNy
G2NUKs0FbZdeAterlbf0Q+wYNtwbsSLfmExChP04fKboPtWfLka2VR52BaHzizD3
uFphZ4Z3iFXBymkhVcLP9C9WZkDM0fDtDK/GADBYWs4g7JYuE6fCCDq64P5JwWzg
9Vfnvkgd6dGs8LaLnKbKI4MwbFuyHhXfkZEvlcZMlBWqDb/HLqzizUlYhkYVs3fn
oDrukX2Y/mnzyedxynBFaEj+o+wTFmih+65aOe6AwtIrZdiQH9w3fGFxRXC8Jw6b
hU30c3XfJCPkiATe+6/fSyzdJrfqbHfHTP/TQCzmviQ5417Xo8Xn9Zp2co3sqz4E
Dq8/eU1gmcSgamSUl7pyaOr85rBh6EdBc7Zq5ktICfV8o7CfNWFBXcdJ4AtV1HB+
KPx+msguRb5ocG87LfiW82IcHS5pp1rqaLIPau732ShOCj11Mjp7JnMQhDk8PNky
Et8EuaOyZryKLPhCZmAbicwlmzy6gLaJFnFGF+yKm+CYhhTv/BHNam/QU0EoOMAe
hxXQPfAquBvm8uWZ+jIh
=Fnle
-----END PGP SIGNATURE-----
Hi Nicola
On 9/28/16 6:33 PM, Nicola wrote:
>> On 9/22/16 2:28 PM, 张正宇 wrote:
>>
>> As I said, I struggled to write a plugin. Request for comment!
>>
>> https://github.com/freemandealer/CodeCoverFlow
>
> You've brilliantly solved your own problem, so this may be a bit late, but…
> using the commands and mappings described in :h preview-window might get
> you close to your workflow. Off the top of my head, assuming you start from
> a single window:
>
> :ptag or <c-w>} or <c-w>g} (to open a tag in the preview window)
> <c-w><c-x> (to exchange windows)
> :se nopreviewwindow (to turn the preview window into a normal window)
> <c-w><c-o> (to close the other window)
>
> and repeat.
>
Thanks for your reply. It is never to late to know new things :)
My plugin is just a simple wrapper of something similar to preview
window - most of my want is a new window, isn't it? The rest is to
create a bidirectional flow between these windows.
All the best!
zzy
--
--
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.
For more options, visit https://groups.google.com/d/optout.
Comment: GPGTools - https://gpgtools.org
iQIcBAEBCgAGBQJX7GxFAAoJENZCakLuo2TNQWkP/Rx1X/e4ueEiiSG47V7Fhfw6
L1Y92/Lt0XzNr9eyNQZL6giYcxl1DyA/4Ylh7ZSFlS2eXNQtEH5xfpRn1VtBE2aK
1TiDCt0uBpFKOvN+E4+WViFa4rBZ6NPUjstsik3d2RwF8E70mB8uz9FIuoQT7CNy
G2NUKs0FbZdeAterlbf0Q+wYNtwbsSLfmExChP04fKboPtWfLka2VR52BaHzizD3
uFphZ4Z3iFXBymkhVcLP9C9WZkDM0fDtDK/GADBYWs4g7JYuE6fCCDq64P5JwWzg
9Vfnvkgd6dGs8LaLnKbKI4MwbFuyHhXfkZEvlcZMlBWqDb/HLqzizUlYhkYVs3fn
oDrukX2Y/mnzyedxynBFaEj+o+wTFmih+65aOe6AwtIrZdiQH9w3fGFxRXC8Jw6b
hU30c3XfJCPkiATe+6/fSyzdJrfqbHfHTP/TQCzmviQ5417Xo8Xn9Zp2co3sqz4E
Dq8/eU1gmcSgamSUl7pyaOr85rBh6EdBc7Zq5ktICfV8o7CfNWFBXcdJ4AtV1HB+
KPx+msguRb5ocG87LfiW82IcHS5pp1rqaLIPau732ShOCj11Mjp7JnMQhDk8PNky
Et8EuaOyZryKLPhCZmAbicwlmzy6gLaJFnFGF+yKm+CYhhTv/BHNam/QU0EoOMAe
hxXQPfAquBvm8uWZ+jIh
=Fnle
-----END PGP SIGNATURE-----
Hi Nicola
On 9/28/16 6:33 PM, Nicola wrote:
>> On 9/22/16 2:28 PM, 张正宇 wrote:
>>
>> As I said, I struggled to write a plugin. Request for comment!
>>
>> https://github.com/freemandealer/CodeCoverFlow
>
> You've brilliantly solved your own problem, so this may be a bit late, but…
> using the commands and mappings described in :h preview-window might get
> you close to your workflow. Off the top of my head, assuming you start from
> a single window:
>
> :ptag or <c-w>} or <c-w>g} (to open a tag in the preview window)
> <c-w><c-x> (to exchange windows)
> :se nopreviewwindow (to turn the preview window into a normal window)
> <c-w><c-o> (to close the other window)
>
> and repeat.
>
Thanks for your reply. It is never to late to know new things :)
My plugin is just a simple wrapper of something similar to preview
window - most of my want is a new window, isn't it? The rest is to
create a bidirectional flow between these windows.
All the best!
zzy
--
--
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.
For more options, visit https://groups.google.com/d/optout.
I want a prompt to save Vim edits when closing window with "X" button
Hi,
I normally close Vim with either ":q" or ":wq" or "ZZ".
However yesterday at the end of the day, I closed a bunch of windows
and accidentally closed a Vim window and lost some edits :-(
I wish that Vim would display a prompt to save changes when I close
with the "X" button at the right top of the window (windows 7).
When I run Gvim, and close the window with the "X" button, I
get a prompt to "save changes yes or no".
I wish I could get a similar prompt with Vim.
I run Vim with mintty.exe using a batch file:
SET PRINTER="\\SR\Brother"
start mintty.exe -p 0,0 /usr/bin/vim.exe %1
Maybe a different terminal instead of mintty?
I did find an old post where someone wanted to disable the
"X" button when using Vim. The suggestion was to edit Vim
source and recompile. That could turn into a non trivial effort.
Any comments?
thanks
windows7
cygwin64
--
--
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.
For more options, visit https://groups.google.com/d/optout.
I normally close Vim with either ":q" or ":wq" or "ZZ".
However yesterday at the end of the day, I closed a bunch of windows
and accidentally closed a Vim window and lost some edits :-(
I wish that Vim would display a prompt to save changes when I close
with the "X" button at the right top of the window (windows 7).
When I run Gvim, and close the window with the "X" button, I
get a prompt to "save changes yes or no".
I wish I could get a similar prompt with Vim.
I run Vim with mintty.exe using a batch file:
SET PRINTER="\\SR\Brother"
start mintty.exe -p 0,0 /usr/bin/vim.exe %1
Maybe a different terminal instead of mintty?
I did find an old post where someone wanted to disable the
"X" button when using Vim. The suggestion was to edit Vim
source and recompile. That could turn into a non trivial effort.
Any comments?
thanks
windows7
cygwin64
--
--
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.
For more options, visit https://groups.google.com/d/optout.
Re: strip filename from full path in small vim
On Wednesday, September 28, 2016 at 10:38:48 AM UTC-7, Andy Wokula wrote:
> Am 28.09.2016 um 18:45 schrieb Bee:
> > In a 'normal' version of vim
> >
> > :lcd %:h
> >
> > will change to the directory of the current file by stripping the
> > filename from the full path.
> >
> > But in a 'small' vim '%:h' does not exist and '%' refers to the full
> > file path.
> >
> > Is there a way in 'small' vim to strip the filename from the path?
>
> Try
> :lcd %/..
>
> --
> Andy
testing with vim.tiny on lubuntu 16.04
:lcd %/..
E472: Command failed
--
--
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.
For more options, visit https://groups.google.com/d/optout.
> Am 28.09.2016 um 18:45 schrieb Bee:
> > In a 'normal' version of vim
> >
> > :lcd %:h
> >
> > will change to the directory of the current file by stripping the
> > filename from the full path.
> >
> > But in a 'small' vim '%:h' does not exist and '%' refers to the full
> > file path.
> >
> > Is there a way in 'small' vim to strip the filename from the path?
>
> Try
> :lcd %/..
>
> --
> Andy
testing with vim.tiny on lubuntu 16.04
:lcd %/..
E472: Command failed
--
--
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.
For more options, visit https://groups.google.com/d/optout.
Re: strip filename from full path in small vim
Am 28.09.2016 um 18:45 schrieb Bee:
> In a 'normal' version of vim
>
> :lcd %:h
>
> will change to the directory of the current file by stripping the
> filename from the full path.
>
> But in a 'small' vim '%:h' does not exist and '%' refers to the full
> file path.
>
> Is there a way in 'small' vim to strip the filename from the path?
Try
:lcd %/..
--
Andy
--
--
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.
For more options, visit https://groups.google.com/d/optout.
> In a 'normal' version of vim
>
> :lcd %:h
>
> will change to the directory of the current file by stripping the
> filename from the full path.
>
> But in a 'small' vim '%:h' does not exist and '%' refers to the full
> file path.
>
> Is there a way in 'small' vim to strip the filename from the path?
Try
:lcd %/..
--
Andy
--
--
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.
For more options, visit https://groups.google.com/d/optout.
strip filename from full path in small vim
In a 'normal' version of vim
:lcd %:h
will change to the directory of the current file by stripping the filename from the full path.
But in a 'small' vim '%:h' does not exist and '%' refers to the full file path.
Is there a way in 'small' vim to strip the filename from the path?
--
--
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.
For more options, visit https://groups.google.com/d/optout.
:lcd %:h
will change to the directory of the current file by stripping the filename from the full path.
But in a 'small' vim '%:h' does not exist and '%' refers to the full file path.
Is there a way in 'small' vim to strip the filename from the path?
--
--
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.
For more options, visit https://groups.google.com/d/optout.
Re: vim & ctags: how to jump to the definition in new window
On 2016-09-28 08:26:47 +0000, 张正宇 said:
>
>
> On 9/22/16 2:28 PM, 张正宇 wrote:
>> Hi Bryan & Marc
>>
>> On 9/21/16 9:30 PM, Bryan Richter wrote:
>>> On Wed, Sep 21, 2016 at 10:49:48AM +0800, 张正宇 wrote:
>>>> Hello list!
>>>>
>>>> I am reading some source code with vim & ctags these days. You know
>>>> sometimes people just forget those input/output parameters while
>>>> diving into functions ...
>>>>
>>>> So, is there some good way to open a new window to view the
>>>> definition after I press 'G+] ' while keep the previous file shown?
>>>
>>> The split version of 'g ]' is 'CTRL-W g ]'. The commands versions of
>>> those keybindings are :tselect and :stselect.
>>>
>>>> All I want is a 'Cover Flow' style. For example, after I press 'G+]'
>>>> in file A, a new window split up from A's to show file B. When I
>>>> press 'G+]' again in file B, file A is hidden and replaced by B,
>>>> while a new file C will show up in B's former window.
>>>
>>> Here's a sample workflow. It could be made easier with some custom
>>> commands...
>>>
>>> " Begin with a fresh tab page while in file A
>>>
>>> :tab split
>>>
>>> " Split and view a definition.
>>>
>>> CTRL-W g ]
>>>
>>> " Now A and B are visible. From file B, jump further forward.
>>>
>>> :only
>>> CTRL-W g ]
>>>
>>> " Further... (C and D become visible)
>>>
>>> :only
>>> CTRL-W g ]
>>>
>>> " Now backwards! (B and C are visible again)
>>>
>>> :only
>>> :below split
>>> :pop
>>>
>>> " ...
>>> "
>>> " Leave the 'Cover Flow' view
>>>
>>> :tabclose
>>>
>>
>>
>> Thanks for your reply. `Ctrl-W g ]` seems to be a good start. I will do
>> some homework on vim and try to figure out my own 'cover flow' solution
>> (maybe learn to write a shabby plugin script? :P)
>>
>>
>> Thanks!
>> zzy
>>
>
> As I said, I struggled to write a plugin. Request for comment!
>
> https://github.com/freemandealer/CodeCoverFlow
You've brilliantly solved your own problem, so this may be a bit late, but…
using the commands and mappings described in :h preview-window might get
you close to your workflow. Off the top of my head, assuming you start from
a single window:
:ptag or <c-w>} or <c-w>g} (to open a tag in the preview window)
<c-w><c-x> (to exchange windows)
:se nopreviewwindow (to turn the preview window into a normal window)
<c-w><c-o> (to close the other window)
and repeat.
Nicola
--
--
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.
For more options, visit https://groups.google.com/d/optout.
>
>
> On 9/22/16 2:28 PM, 张正宇 wrote:
>> Hi Bryan & Marc
>>
>> On 9/21/16 9:30 PM, Bryan Richter wrote:
>>> On Wed, Sep 21, 2016 at 10:49:48AM +0800, 张正宇 wrote:
>>>> Hello list!
>>>>
>>>> I am reading some source code with vim & ctags these days. You know
>>>> sometimes people just forget those input/output parameters while
>>>> diving into functions ...
>>>>
>>>> So, is there some good way to open a new window to view the
>>>> definition after I press 'G+] ' while keep the previous file shown?
>>>
>>> The split version of 'g ]' is 'CTRL-W g ]'. The commands versions of
>>> those keybindings are :tselect and :stselect.
>>>
>>>> All I want is a 'Cover Flow' style. For example, after I press 'G+]'
>>>> in file A, a new window split up from A's to show file B. When I
>>>> press 'G+]' again in file B, file A is hidden and replaced by B,
>>>> while a new file C will show up in B's former window.
>>>
>>> Here's a sample workflow. It could be made easier with some custom
>>> commands...
>>>
>>> " Begin with a fresh tab page while in file A
>>>
>>> :tab split
>>>
>>> " Split and view a definition.
>>>
>>> CTRL-W g ]
>>>
>>> " Now A and B are visible. From file B, jump further forward.
>>>
>>> :only
>>> CTRL-W g ]
>>>
>>> " Further... (C and D become visible)
>>>
>>> :only
>>> CTRL-W g ]
>>>
>>> " Now backwards! (B and C are visible again)
>>>
>>> :only
>>> :below split
>>> :pop
>>>
>>> " ...
>>> "
>>> " Leave the 'Cover Flow' view
>>>
>>> :tabclose
>>>
>>
>>
>> Thanks for your reply. `Ctrl-W g ]` seems to be a good start. I will do
>> some homework on vim and try to figure out my own 'cover flow' solution
>> (maybe learn to write a shabby plugin script? :P)
>>
>>
>> Thanks!
>> zzy
>>
>
> As I said, I struggled to write a plugin. Request for comment!
>
> https://github.com/freemandealer/CodeCoverFlow
You've brilliantly solved your own problem, so this may be a bit late, but…
using the commands and mappings described in :h preview-window might get
you close to your workflow. Off the top of my head, assuming you start from
a single window:
:ptag or <c-w>} or <c-w>g} (to open a tag in the preview window)
<c-w><c-x> (to exchange windows)
:se nopreviewwindow (to turn the preview window into a normal window)
<c-w><c-o> (to close the other window)
and repeat.
Nicola
--
--
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.
For more options, visit https://groups.google.com/d/optout.
Re: No such highlight group name: netrwMarkFile
Am Dienstag, 27. September 2016 16:06:17 UTC+2 schrieb DrChip:
> Johann Höchtl wrote:
> > Hi,
> >
> > I am using
> > Vim 8.0.7, netrw v156
> >
> > When I highlight a file in netrw using mf, it is not highlighted, neither on the console, nor in gvim.
> >
> > If I first mark files and later a target mt , I get the error
> >
> > Error detected while processing function <SNR>17_NetrwMarkFileTgt[63]..<SNR>17_LocalBrowseRefresh[57]..<SNR>17_Netr
> > wRefresh:
> > line 28:
> > E28: No such highlight group name: netrwMarkFile
> > Error detected while processing function <SNR>17_NetrwMarkFileTgt[69]..<SNR>17_NetrwRefresh:
> > line 28:
> > E28: No such highlight group name: netrwMarkFile
> >
> > However, a subsequent copy mc succeeds.
> >
> > It is very cumbersome to work without highlighting of marked files.
> >
> Hello:
>
> I see the problem; must be a new thing with vim 8. I'll look into it.
>
Thank you very much. However the biggest issue was that I didn't have highlighting enabled ;) Nonetheless without highlighting enabled, no such error should be given IMHO.
> Chip Campbell
--
--
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.
For more options, visit https://groups.google.com/d/optout.
> Johann Höchtl wrote:
> > Hi,
> >
> > I am using
> > Vim 8.0.7, netrw v156
> >
> > When I highlight a file in netrw using mf, it is not highlighted, neither on the console, nor in gvim.
> >
> > If I first mark files and later a target mt , I get the error
> >
> > Error detected while processing function <SNR>17_NetrwMarkFileTgt[63]..<SNR>17_LocalBrowseRefresh[57]..<SNR>17_Netr
> > wRefresh:
> > line 28:
> > E28: No such highlight group name: netrwMarkFile
> > Error detected while processing function <SNR>17_NetrwMarkFileTgt[69]..<SNR>17_NetrwRefresh:
> > line 28:
> > E28: No such highlight group name: netrwMarkFile
> >
> > However, a subsequent copy mc succeeds.
> >
> > It is very cumbersome to work without highlighting of marked files.
> >
> Hello:
>
> I see the problem; must be a new thing with vim 8. I'll look into it.
>
Thank you very much. However the biggest issue was that I didn't have highlighting enabled ;) Nonetheless without highlighting enabled, no such error should be given IMHO.
> Chip Campbell
--
--
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.
For more options, visit https://groups.google.com/d/optout.
Re: vim & ctags: how to jump to the definition in new window
-----BEGIN PGP SIGNATURE-----
Comment: GPGTools - https://gpgtools.org
iQIcBAEBCgAGBQJX637IAAoJENZCakLuo2TNtpUP/3mcZE+ma804MSZEw9CcE4v8
Ebh5L4geZkRPWoOZEyhBSecoK/NoOXnjR1oCrh28Y4myWBwBPp14OSBEvJwLBTHe
tNw4esM4ule5jHORlE3Tag1UhPrGmDjQFNAgZ2JQxZ0qKERbeioITUV+PtAJBNJd
0hVK4wV2RKOsphVVJUYfWZbFZ5I7T3vdZCrW9Vz1d5iTmFi7Rqwlu5TDQhocVLQp
bBbFd/pw96+K53xxqgHbslNjbCE3v2Flc6pjGZoWceyNVKR5KckQ166D9GMWsRSo
lgp+1SWKV+ueNI2WCJrOmK1CBY2y40R87QxLtJsRD9+BiQBJLnz7clq4f6GT4WeX
5qOz/osKAUA1tQSxhdeb4V7XmjgbyaQpI8zY0ETkVq0w+X1kDULHb5ZmFcQDPu66
uXWEBQKBjrvaQ2KGc6btIh5ItZuaBRR7H7xKEazBfwLzPqJw58++9qIOqBg5TvRF
U1PKalbYVx9reFQOBYoss5JRLSHBq8ShVuXgxW9R7+8MA5PdNttSxOTLUmu5DNf5
93kFQ9SagUAZE/f91MgTp2NY3nqS3tAu12qj8Mm5nVMuA9yfBUMCitIPNS+Dliij
AJJhDJC7tj1JwC81M9Z4G3lOdErCtBuZ5erFI61JOOsJG1m4Z8jok+PuBBmD69+j
BnsF+HCQryUTnsq4GoSM
=sigN
-----END PGP SIGNATURE-----
On 9/22/16 2:28 PM, 张正宇 wrote:
> Hi Bryan & Marc
>
> On 9/21/16 9:30 PM, Bryan Richter wrote:
>> On Wed, Sep 21, 2016 at 10:49:48AM +0800, 张正宇 wrote:
>>> Hello list!
>>>
>>> I am reading some source code with vim & ctags these days. You know
>>> sometimes people just forget those input/output parameters while
>>> diving into functions ...
>>>
>>> So, is there some good way to open a new window to view the
>>> definition after I press 'G+] ' while keep the previous file shown?
>>
>> The split version of 'g ]' is 'CTRL-W g ]'. The commands versions of
>> those keybindings are :tselect and :stselect.
>>
>>> All I want is a 'Cover Flow' style. For example, after I press 'G+]'
>>> in file A, a new window split up from A's to show file B. When I
>>> press 'G+]' again in file B, file A is hidden and replaced by B,
>>> while a new file C will show up in B's former window.
>>
>> Here's a sample workflow. It could be made easier with some custom
>> commands...
>>
>> " Begin with a fresh tab page while in file A
>>
>> :tab split
>>
>> " Split and view a definition.
>>
>> CTRL-W g ]
>>
>> " Now A and B are visible. From file B, jump further forward.
>>
>> :only
>> CTRL-W g ]
>>
>> " Further... (C and D become visible)
>>
>> :only
>> CTRL-W g ]
>>
>> " Now backwards! (B and C are visible again)
>>
>> :only
>> :below split
>> :pop
>>
>> " ...
>> "
>> " Leave the 'Cover Flow' view
>>
>> :tabclose
>>
>
>
> Thanks for your reply. `Ctrl-W g ]` seems to be a good start. I will do
> some homework on vim and try to figure out my own 'cover flow' solution
> (maybe learn to write a shabby plugin script? :P)
>
>
> Thanks!
> zzy
>
As I said, I struggled to write a plugin. Request for comment!
https://github.com/freemandealer/CodeCoverFlow
Thanks
zzy
--
--
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.
For more options, visit https://groups.google.com/d/optout.
Comment: GPGTools - https://gpgtools.org
iQIcBAEBCgAGBQJX637IAAoJENZCakLuo2TNtpUP/3mcZE+ma804MSZEw9CcE4v8
Ebh5L4geZkRPWoOZEyhBSecoK/NoOXnjR1oCrh28Y4myWBwBPp14OSBEvJwLBTHe
tNw4esM4ule5jHORlE3Tag1UhPrGmDjQFNAgZ2JQxZ0qKERbeioITUV+PtAJBNJd
0hVK4wV2RKOsphVVJUYfWZbFZ5I7T3vdZCrW9Vz1d5iTmFi7Rqwlu5TDQhocVLQp
bBbFd/pw96+K53xxqgHbslNjbCE3v2Flc6pjGZoWceyNVKR5KckQ166D9GMWsRSo
lgp+1SWKV+ueNI2WCJrOmK1CBY2y40R87QxLtJsRD9+BiQBJLnz7clq4f6GT4WeX
5qOz/osKAUA1tQSxhdeb4V7XmjgbyaQpI8zY0ETkVq0w+X1kDULHb5ZmFcQDPu66
uXWEBQKBjrvaQ2KGc6btIh5ItZuaBRR7H7xKEazBfwLzPqJw58++9qIOqBg5TvRF
U1PKalbYVx9reFQOBYoss5JRLSHBq8ShVuXgxW9R7+8MA5PdNttSxOTLUmu5DNf5
93kFQ9SagUAZE/f91MgTp2NY3nqS3tAu12qj8Mm5nVMuA9yfBUMCitIPNS+Dliij
AJJhDJC7tj1JwC81M9Z4G3lOdErCtBuZ5erFI61JOOsJG1m4Z8jok+PuBBmD69+j
BnsF+HCQryUTnsq4GoSM
=sigN
-----END PGP SIGNATURE-----
On 9/22/16 2:28 PM, 张正宇 wrote:
> Hi Bryan & Marc
>
> On 9/21/16 9:30 PM, Bryan Richter wrote:
>> On Wed, Sep 21, 2016 at 10:49:48AM +0800, 张正宇 wrote:
>>> Hello list!
>>>
>>> I am reading some source code with vim & ctags these days. You know
>>> sometimes people just forget those input/output parameters while
>>> diving into functions ...
>>>
>>> So, is there some good way to open a new window to view the
>>> definition after I press 'G+] ' while keep the previous file shown?
>>
>> The split version of 'g ]' is 'CTRL-W g ]'. The commands versions of
>> those keybindings are :tselect and :stselect.
>>
>>> All I want is a 'Cover Flow' style. For example, after I press 'G+]'
>>> in file A, a new window split up from A's to show file B. When I
>>> press 'G+]' again in file B, file A is hidden and replaced by B,
>>> while a new file C will show up in B's former window.
>>
>> Here's a sample workflow. It could be made easier with some custom
>> commands...
>>
>> " Begin with a fresh tab page while in file A
>>
>> :tab split
>>
>> " Split and view a definition.
>>
>> CTRL-W g ]
>>
>> " Now A and B are visible. From file B, jump further forward.
>>
>> :only
>> CTRL-W g ]
>>
>> " Further... (C and D become visible)
>>
>> :only
>> CTRL-W g ]
>>
>> " Now backwards! (B and C are visible again)
>>
>> :only
>> :below split
>> :pop
>>
>> " ...
>> "
>> " Leave the 'Cover Flow' view
>>
>> :tabclose
>>
>
>
> Thanks for your reply. `Ctrl-W g ]` seems to be a good start. I will do
> some homework on vim and try to figure out my own 'cover flow' solution
> (maybe learn to write a shabby plugin script? :P)
>
>
> Thanks!
> zzy
>
As I said, I struggled to write a plugin. Request for comment!
https://github.com/freemandealer/CodeCoverFlow
Thanks
zzy
--
--
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.
For more options, visit https://groups.google.com/d/optout.
Tuesday, September 27, 2016
Re: No such highlight group name: netrwMarkFile
Johann Höchtl wrote:
> Hi,
>
> I am using
> Vim 8.0.7, netrw v156
>
> When I highlight a file in netrw using mf, it is not highlighted, neither on the console, nor in gvim.
>
> If I first mark files and later a target mt , I get the error
>
> Error detected while processing function <SNR>17_NetrwMarkFileTgt[63]..<SNR>17_LocalBrowseRefresh[57]..<SNR>17_Netr
> wRefresh:
> line 28:
> E28: No such highlight group name: netrwMarkFile
> Error detected while processing function <SNR>17_NetrwMarkFileTgt[69]..<SNR>17_NetrwRefresh:
> line 28:
> E28: No such highlight group name: netrwMarkFile
>
> However, a subsequent copy mc succeeds.
>
> It is very cumbersome to work without highlighting of marked files.
>
Hello:
I see the problem; must be a new thing with vim 8. I'll look into it.
Chip Campbell
--
--
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.
For more options, visit https://groups.google.com/d/optout.
> Hi,
>
> I am using
> Vim 8.0.7, netrw v156
>
> When I highlight a file in netrw using mf, it is not highlighted, neither on the console, nor in gvim.
>
> If I first mark files and later a target mt , I get the error
>
> Error detected while processing function <SNR>17_NetrwMarkFileTgt[63]..<SNR>17_LocalBrowseRefresh[57]..<SNR>17_Netr
> wRefresh:
> line 28:
> E28: No such highlight group name: netrwMarkFile
> Error detected while processing function <SNR>17_NetrwMarkFileTgt[69]..<SNR>17_NetrwRefresh:
> line 28:
> E28: No such highlight group name: netrwMarkFile
>
> However, a subsequent copy mc succeeds.
>
> It is very cumbersome to work without highlighting of marked files.
>
Hello:
I see the problem; must be a new thing with vim 8. I'll look into it.
Chip Campbell
--
--
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.
For more options, visit https://groups.google.com/d/optout.
Monday, September 26, 2016
Re: vim stuck on write
On Mon, 26 Sep 2016 15:35:29 -0400
ping song <songpingemail@gmail.com> wrote:
> whenever I change a tcl file and :write
> the vim got stuck...for ever.
> no cpu spike, gnu screen/tmux works fine where vim is running inside.
> no file permission issue - if I set ft=txt and write, there won't be
> any problem...
>
> so I turned on vim debug (-V4).
> it looks I'm stucking at:
>
> vim-misc 1.16.1: Executing external command using system() function:
> sh -c '(/usr/bin/ctags-exuberant --fields=+l --c-kinds=+p
> --c++-kinds=+p --sort=no -f- '\''--language-force=tcl'\''
> '\''/home/ping/Dropbox/lin g-backup/crtc/crtc.abc'\'')
> 1>'\''/tmp/ve6IXR8/15'\''
> 2>'\''/tmp/ve6IXR8/16'\'''
> shell to execute: "(sh -c '(/usr/bin/ctags-exuberant --fields=+l
> --c-kinds=+p --c++-kinds=+p --sort=no -f- '\''--language-force=tcl'\''
> '\''/home/ping/Dropbox/linux-config-backup/crtc/crtc.abc'\'') 1>'\'
> 6IXR8/15'\'' 2>'\''/tmp/ve6IXR8/16'\''') >/tmp/ve6IXR8/17 2>&1"
>
If the cpu is not doing anything, it sounds like one of the
sub-processes is waiting on input.
--
--
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.
For more options, visit https://groups.google.com/d/optout.
ping song <songpingemail@gmail.com> wrote:
> whenever I change a tcl file and :write
> the vim got stuck...for ever.
> no cpu spike, gnu screen/tmux works fine where vim is running inside.
> no file permission issue - if I set ft=txt and write, there won't be
> any problem...
>
> so I turned on vim debug (-V4).
> it looks I'm stucking at:
>
> vim-misc 1.16.1: Executing external command using system() function:
> sh -c '(/usr/bin/ctags-exuberant --fields=+l --c-kinds=+p
> --c++-kinds=+p --sort=no -f- '\''--language-force=tcl'\''
> '\''/home/ping/Dropbox/lin g-backup/crtc/crtc.abc'\'')
> 1>'\''/tmp/ve6IXR8/15'\''
> 2>'\''/tmp/ve6IXR8/16'\'''
> shell to execute: "(sh -c '(/usr/bin/ctags-exuberant --fields=+l
> --c-kinds=+p --c++-kinds=+p --sort=no -f- '\''--language-force=tcl'\''
> '\''/home/ping/Dropbox/linux-config-backup/crtc/crtc.abc'\'') 1>'\'
> 6IXR8/15'\'' 2>'\''/tmp/ve6IXR8/16'\''') >/tmp/ve6IXR8/17 2>&1"
>
If the cpu is not doing anything, it sounds like one of the
sub-processes is waiting on input.
--
--
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.
For more options, visit https://groups.google.com/d/optout.
vim stuck on write
Experts:
I need some help here please...
I have a on-going projects that I'm working on with vim. I never saw this until today...whenever I change a tcl file and :write
the vim got stuck...for ever.
no cpu spike, gnu screen/tmux works fine where vim is running inside.
no file permission issue - if I set ft=txt and write, there won't be any problem...
so I turned on vim debug (-V4).
it looks I'm stucking at:
vim-misc 1.16.1: Executing external command using system() function: sh -c '(/usr/bin/ctags-exuberant --fields=+l --c-kinds=+p --c++-kinds=+p --sort=no -f- '\''--language-force=tcl'\'' '\''/home/ping/Dropbox/lin
g-backup/crtc/crtc.abc'\'') 1>'\''/tmp/ve6IXR8/15'\'' 2>'\''/tmp/ve6IXR8/16'\'''
shell to execute: "(sh -c '(/usr/bin/ctags-exuberant --fields=+l --c-kinds=+p --c++-kinds=+p --sort=no -f- '\''--language-force=tcl'\'' '\''/home/ping/Dropbox/linux-config-backup/crtc/crtc.abc'\'') 1>'\'
6IXR8/15'\'' 2>'\''/tmp/ve6IXR8/16'\''') >/tmp/ve6IXR8/17 2>&1"
so it seems to be related to this vim-misc plugin...but I still doubt it -- I'm not sure I can uninstall it since a lot of plug-ins I'm sure depend on it - autotag seems one.
anyone please shed some light here?
thanks.
regards
ping
--
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.
For more options, visit https://groups.google.com/d/optout.
Re: Strength of builtin blowfish2 encryption?
On 25.09.16 16:24, Stefan Klein wrote:
> Hi,
>
> I wonder how string the builtin encryption of vim really is.
> The manpage states: "cryptmethod zip [ ... ] breakable [ ... ] a 6
> character key in one day (on a Pentium 133 PC)"
> Guess today's computers will use seconds if not microseconds.
>
> But what about blowfish2?
>
> Was this ever reviewed? Are there any tools out there to crack it
> (with weak keys) to get an idea how long it would take with a complex
> key?
We discussed that on this list on 15.09.15, and the last post at:
https://groups.google.com/forum/#!searchin/vim_use/VimCrypt$3A$20A$20small$20framework$20for$20encryption/vim_use/SjP-JQB6Tgo/RM8xhTG-AQAJ
has a bit of a look at it. In short, blowfish2 is probably OK for
encrypting small (wrt 4 GB) files, but switching to twofish would be
prudent.
> I wonder if it's safe to put a blowfish2 crypted password file on a
> cloud drive, how long it would take for it to be cracked if someone
> really tries to.
Decrypting a small file is much harder. Use a strong key. Don't put any
banking passwords in there. As it's not behind a firewall, switch to
twofish for such exposure. ... I wouldn't put it out there.
The simplest way to switch to twofish might be one of:
$ apt-cache search twofish
...
keepassx - Cross Platform Password Manager
mcrypt - Replacement for old unix crypt(1)
Erik
(Who might just invoke mcrypt on vimming such a file, rather than
relying on blowfish2, adequate though it ought to be on small files with
strong keys.)
--
--
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.
For more options, visit https://groups.google.com/d/optout.
> Hi,
>
> I wonder how string the builtin encryption of vim really is.
> The manpage states: "cryptmethod zip [ ... ] breakable [ ... ] a 6
> character key in one day (on a Pentium 133 PC)"
> Guess today's computers will use seconds if not microseconds.
>
> But what about blowfish2?
>
> Was this ever reviewed? Are there any tools out there to crack it
> (with weak keys) to get an idea how long it would take with a complex
> key?
We discussed that on this list on 15.09.15, and the last post at:
https://groups.google.com/forum/#!searchin/vim_use/VimCrypt$3A$20A$20small$20framework$20for$20encryption/vim_use/SjP-JQB6Tgo/RM8xhTG-AQAJ
has a bit of a look at it. In short, blowfish2 is probably OK for
encrypting small (wrt 4 GB) files, but switching to twofish would be
prudent.
> I wonder if it's safe to put a blowfish2 crypted password file on a
> cloud drive, how long it would take for it to be cracked if someone
> really tries to.
Decrypting a small file is much harder. Use a strong key. Don't put any
banking passwords in there. As it's not behind a firewall, switch to
twofish for such exposure. ... I wouldn't put it out there.
The simplest way to switch to twofish might be one of:
$ apt-cache search twofish
...
keepassx - Cross Platform Password Manager
mcrypt - Replacement for old unix crypt(1)
Erik
(Who might just invoke mcrypt on vimming such a file, rather than
relying on blowfish2, adequate though it ought to be on small files with
strong keys.)
--
--
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.
For more options, visit https://groups.google.com/d/optout.
Sunday, September 25, 2016
Status line vs. CursorColumn in diff (or scrollbind?) mode
IMHO this is not a bug, just a quirk, maybe even a feature.
In diff mode (or maybe whenever 'scrollbind' is set?), then in the
windows other that the current one, the CursorColumn highlight doesn't
move, but the status line follows the cursor movement in the current
window, as follows:
%c ("column number" i.e. byte-of-line) is equal to the current
window's %c even if the line in the non-current window is shorter than
that
%V (virtual column number [i.e. screen cell abscissa] if different
from %c) is always 1, thus not displayed when in column 1
%B (character value in hex) is the value of the character at that
column, or zero if beyond the end of the line
Possibly others which are not part of my 'statusline' setting.
As expected, in "ordinary" (non-scrollbound) windows, cursor movement
does not influence other windows' status line contents.
Tested in both GTK3 GUI and console, in Vim 8.0.12 Huge build. Not
tested on empty lines.
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.
For more options, visit https://groups.google.com/d/optout.
In diff mode (or maybe whenever 'scrollbind' is set?), then in the
windows other that the current one, the CursorColumn highlight doesn't
move, but the status line follows the cursor movement in the current
window, as follows:
%c ("column number" i.e. byte-of-line) is equal to the current
window's %c even if the line in the non-current window is shorter than
that
%V (virtual column number [i.e. screen cell abscissa] if different
from %c) is always 1, thus not displayed when in column 1
%B (character value in hex) is the value of the character at that
column, or zero if beyond the end of the line
Possibly others which are not part of my 'statusline' setting.
As expected, in "ordinary" (non-scrollbound) windows, cursor movement
does not influence other windows' status line contents.
Tested in both GTK3 GUI and console, in Vim 8.0.12 Huge build. Not
tested on empty lines.
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.
For more options, visit https://groups.google.com/d/optout.
Re: Strength of builtin blowfish2 encryption?
On 2016-09-25 13:15, Shawn H Corey wrote:
>> > I wonder how string the builtin encryption of vim really is.
>>
>> Encryption really isn't the business of a text editor. Decrypt the
>> cipher-text, feed it to the editor, encrypt when saving, and be
>> sure to delete any temporary/backup files.
>
> It is the business of an editor when it stores temporary files.
> Those too have to be encrypted or it's all wasted effort.
swap/temporary files should be encrypted *or not used*. I believe
one of the GPG plugins I tried disabled a number options such as the
swap file, undo history, and persisting of registers in .viminfo so
it would read the encrypted file in, disable all the settings, pass
it through GPG to decrypt it, allow viewing/editing, then encrypt
upon writing. There's still the possibility of the OS swapping the
memory out to an unencrypted swap space, but that's an OS thing (on
OpenBSD, the swap is encrypted by default; on other OSes, you might
have to jump through some hoops).
-tim
--
--
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.
For more options, visit https://groups.google.com/d/optout.
>> > I wonder how string the builtin encryption of vim really is.
>>
>> Encryption really isn't the business of a text editor. Decrypt the
>> cipher-text, feed it to the editor, encrypt when saving, and be
>> sure to delete any temporary/backup files.
>
> It is the business of an editor when it stores temporary files.
> Those too have to be encrypted or it's all wasted effort.
swap/temporary files should be encrypted *or not used*. I believe
one of the GPG plugins I tried disabled a number options such as the
swap file, undo history, and persisting of registers in .viminfo so
it would read the encrypted file in, disable all the settings, pass
it through GPG to decrypt it, allow viewing/editing, then encrypt
upon writing. There's still the possibility of the OS swapping the
memory out to an unencrypted swap space, but that's an OS thing (on
OpenBSD, the swap is encrypted by default; on other OSes, you might
have to jump through some hoops).
-tim
--
--
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.
For more options, visit https://groups.google.com/d/optout.
Re: Strength of builtin blowfish2 encryption?
On Sun, 25 Sep 2016 12:02:10 -0400
arocker@Vex.Net wrote:
>
> > I wonder how string the builtin encryption of vim really is.
> >
>
> Encryption really isn't the business of a text editor. Decrypt the
> cipher-text, feed it to the editor, encrypt when saving, and be sure
> to delete any temporary/backup files.
>
> Yes. there are windows of vulnerability in there, but I would suggest
> they are less risky than relying on amateur cryptography.
>
It is the business of an editor when it stores temporary files. Those
too have to be encrypted or it's all wasted effort.
--
--
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.
For more options, visit https://groups.google.com/d/optout.
arocker@Vex.Net wrote:
>
> > I wonder how string the builtin encryption of vim really is.
> >
>
> Encryption really isn't the business of a text editor. Decrypt the
> cipher-text, feed it to the editor, encrypt when saving, and be sure
> to delete any temporary/backup files.
>
> Yes. there are windows of vulnerability in there, but I would suggest
> they are less risky than relying on amateur cryptography.
>
It is the business of an editor when it stores temporary files. Those
too have to be encrypted or it's all wasted effort.
--
--
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.
For more options, visit https://groups.google.com/d/optout.
Re: Strength of builtin blowfish2 encryption?
> I wonder how string the builtin encryption of vim really is.
>
Encryption really isn't the business of a text editor. Decrypt the
cipher-text, feed it to the editor, encrypt when saving, and be sure to
delete any temporary/backup files.
Yes. there are windows of vulnerability in there, but I would suggest they
are less risky than relying on amateur cryptography.
--
--
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.
For more options, visit https://groups.google.com/d/optout.
>
Encryption really isn't the business of a text editor. Decrypt the
cipher-text, feed it to the editor, encrypt when saving, and be sure to
delete any temporary/backup files.
Yes. there are windows of vulnerability in there, but I would suggest they
are less risky than relying on amateur cryptography.
--
--
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.
For more options, visit https://groups.google.com/d/optout.
Strength of builtin blowfish2 encryption?
Hi,
I wonder how string the builtin encryption of vim really is.
The manpage states: "cryptmethod zip [ ... ] breakable [ ... ] a 6
character key in one day (on a Pentium 133 PC)"
Guess today's computers will use seconds if not microseconds.
But what about blowfish2?
Was this ever reviewed? Are there any tools out there to crack it
(with weak keys) to get an idea how long it would take with a complex
key?
I wonder if it's safe to put a blowfish2 crypted password file on a
cloud drive, how long it would take for it to be cracked if someone
really tries to.
Thank you,
Stefan
--
--
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.
For more options, visit https://groups.google.com/d/optout.
I wonder how string the builtin encryption of vim really is.
The manpage states: "cryptmethod zip [ ... ] breakable [ ... ] a 6
character key in one day (on a Pentium 133 PC)"
Guess today's computers will use seconds if not microseconds.
But what about blowfish2?
Was this ever reviewed? Are there any tools out there to crack it
(with weak keys) to get an idea how long it would take with a complex
key?
I wonder if it's safe to put a blowfish2 crypted password file on a
cloud drive, how long it would take for it to be cracked if someone
really tries to.
Thank you,
Stefan
--
--
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.
For more options, visit https://groups.google.com/d/optout.
Re: mapping :h to ;
>>
>> Has someone an advice for me?
>>
>> Alle
>
> Thank for your advises. To resume: the function keys F2 till F12 (on my
> keyboard) are available as 'shortcuts'. It is not advisable to use keys
> &c.
Alle deserves compliments for this; reading back the message as
understood. (As is the aviation practice,) That helps both parties,
especially if there is some misunderstanding, which is better caught
early.
--
--
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.
For more options, visit https://groups.google.com/d/optout.
>> Has someone an advice for me?
>>
>> Alle
>
> Thank for your advises. To resume: the function keys F2 till F12 (on my
> keyboard) are available as 'shortcuts'. It is not advisable to use keys
> &c.
Alle deserves compliments for this; reading back the message as
understood. (As is the aviation practice,) That helps both parties,
especially if there is some misunderstanding, which is better caught
early.
--
--
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.
For more options, visit https://groups.google.com/d/optout.
Re: mapping :h to ;
On Sat, Sep 24, 2016 at 10:39 PM, tooth pik <toothpik6@gmail.com> wrote:
> I had the same experience -- I believe we are both suse users -- they did a
> good job of hiding it
Yes, I am on openSUSE.
>
> from the main menu select Settings, then Configure Desktop, Workspace,
> Shortcuts, Global Keyboard Shortcuts,
> then in that KDE Component scroll box scroll to kwin, go down to Maximize
> Window and delete its mapping
Thanks, I think I found the appropriate menuitem in the konsole Settings.
>
> good luck...
>
> On Sat, Sep 24, 2016 at 10:46 AM, Tony Mechelynck
> <antoine.mechelynck@gmail.com> wrote:
>>
>> P.S. I recently noticed that on some terminals, <F11> is used by the
>> terminal itself to toggle between Maximize and Unmaximize and is not
>> passed to the application. [...]
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.
For more options, visit https://groups.google.com/d/optout.
> I had the same experience -- I believe we are both suse users -- they did a
> good job of hiding it
Yes, I am on openSUSE.
>
> from the main menu select Settings, then Configure Desktop, Workspace,
> Shortcuts, Global Keyboard Shortcuts,
> then in that KDE Component scroll box scroll to kwin, go down to Maximize
> Window and delete its mapping
Thanks, I think I found the appropriate menuitem in the konsole Settings.
>
> good luck...
>
> On Sat, Sep 24, 2016 at 10:46 AM, Tony Mechelynck
> <antoine.mechelynck@gmail.com> wrote:
>>
>> P.S. I recently noticed that on some terminals, <F11> is used by the
>> terminal itself to toggle between Maximize and Unmaximize and is not
>> passed to the application. [...]
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.
For more options, visit https://groups.google.com/d/optout.
Saturday, September 24, 2016
Re: Is vim supporting 24 bit colors?
2016-09-24 19:04 GMT+03:00 Tony Mechelynck <antoine.mechelynck@gmail.com>:
> On Sat, Sep 24, 2016 at 5:40 PM, Nikolay Aleksandrovich Pavlov
> <zyx.vim@gmail.com> wrote:
>> 2016-09-24 7:05 GMT+03:00 Tony Mechelynck <antoine.mechelynck@gmail.com>:
>>> On Fri, Sep 23, 2016 at 4:26 AM, KiYugadgeter <zyouhousikaku@gmail.com> wrote:
>>>> Is vim supporting 24 bit colors?
>>>>
>>>> I want to use vim on windows10 bash.
>>>>
>>>> windows 10 bash is supporting 24bit colors on beta version.
>>>>
>>>> Will vim support 24bit colors?
>>>
>>> Vim supports between 2 (2^1) and 16777216 (2^24) colors, depending on
>>> how many _it can tell that_ your terminal supports. This is set by the
>>> termcap variable t_Co or by the equivalent terminfo setting, and these
>>> settings depend in turn on the 'term' setting (q.v.) If $TERM is not
>>> set, and Vim has no way of knowing otherwise, it will set an
>>> OS-dependent 'term' default: for 32- or 64-bit Windows, 'term'
>>> defaults to "win32". To see the number of colours Vim thinks that your
>>> terminal supports, use
>>> :set t_Co?
>>
>> &t_Co will never give you 24-bit value. Also termcap/terminfo do not
>> normally contain information about 24-bit colors support, though tmux
>> developers has selected some custom setting they use to detect 24-bit
>> support. Vim AFAIK does not use it.
>
> You can set t_Co yourself early in the vimrc (before any of the following:
> runtime vimrc_example.vim
> source $VIMRUNTIME/vimrc_example.vim
> " or the same for defaults.vim
> syntax on
> syntax enable
> colorscheme something-or-other
> ) and it will stick. The problem is how to set ctermfg= and ctermbg=
> values for the desired colors, since the correspondence between GUI
> #rrggbb color values and cterm color indices is usually opaque.
>
> I just tried the following in a Huge gui-enabled Vim running in console mode:
> set t_Co=16777216 t_Co?
> and it answered
> t_Co=16777216
> so it _is_ possible to set that high a value. What I don't know is
> which terminals, if any, really support that many colors, nor how to
> use them, and AFAIK no pre-programmed colorscheme uses that many
> colors for ctermfg= ctermbg=
I was false when saying that you can't set &t_Co to such value, but
this does not change the key point: terminals which support 24-bit
colors use different escape sequences for expressing such colors. So
you will not see such a high value in termcap/terminfo.
I also would not be surprised to hear that some software is written in
a way so that it supports only no more then three digits in Co
termcap/terminfo entry.
>>
>>>
>>> For me, 256 colors are good enough, and once I set up my vimrc to make
>>> Vim use (as closely as possible) the same colors in a console and in
>>> the GUI, I can't tell the difference by the naked eye. See
>>> http://vim.wikia.com/wiki/Using_GUI_color_settings_in_a_terminal
>>>
>>> See also ":help term.txt", especially the first two sections.
>
> I stand by the above two paragraphs.
>>>
>>>
>>> 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.
> 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.
For more options, visit https://groups.google.com/d/optout.
> On Sat, Sep 24, 2016 at 5:40 PM, Nikolay Aleksandrovich Pavlov
> <zyx.vim@gmail.com> wrote:
>> 2016-09-24 7:05 GMT+03:00 Tony Mechelynck <antoine.mechelynck@gmail.com>:
>>> On Fri, Sep 23, 2016 at 4:26 AM, KiYugadgeter <zyouhousikaku@gmail.com> wrote:
>>>> Is vim supporting 24 bit colors?
>>>>
>>>> I want to use vim on windows10 bash.
>>>>
>>>> windows 10 bash is supporting 24bit colors on beta version.
>>>>
>>>> Will vim support 24bit colors?
>>>
>>> Vim supports between 2 (2^1) and 16777216 (2^24) colors, depending on
>>> how many _it can tell that_ your terminal supports. This is set by the
>>> termcap variable t_Co or by the equivalent terminfo setting, and these
>>> settings depend in turn on the 'term' setting (q.v.) If $TERM is not
>>> set, and Vim has no way of knowing otherwise, it will set an
>>> OS-dependent 'term' default: for 32- or 64-bit Windows, 'term'
>>> defaults to "win32". To see the number of colours Vim thinks that your
>>> terminal supports, use
>>> :set t_Co?
>>
>> &t_Co will never give you 24-bit value. Also termcap/terminfo do not
>> normally contain information about 24-bit colors support, though tmux
>> developers has selected some custom setting they use to detect 24-bit
>> support. Vim AFAIK does not use it.
>
> You can set t_Co yourself early in the vimrc (before any of the following:
> runtime vimrc_example.vim
> source $VIMRUNTIME/vimrc_example.vim
> " or the same for defaults.vim
> syntax on
> syntax enable
> colorscheme something-or-other
> ) and it will stick. The problem is how to set ctermfg= and ctermbg=
> values for the desired colors, since the correspondence between GUI
> #rrggbb color values and cterm color indices is usually opaque.
>
> I just tried the following in a Huge gui-enabled Vim running in console mode:
> set t_Co=16777216 t_Co?
> and it answered
> t_Co=16777216
> so it _is_ possible to set that high a value. What I don't know is
> which terminals, if any, really support that many colors, nor how to
> use them, and AFAIK no pre-programmed colorscheme uses that many
> colors for ctermfg= ctermbg=
I was false when saying that you can't set &t_Co to such value, but
this does not change the key point: terminals which support 24-bit
colors use different escape sequences for expressing such colors. So
you will not see such a high value in termcap/terminfo.
I also would not be surprised to hear that some software is written in
a way so that it supports only no more then three digits in Co
termcap/terminfo entry.
>>
>>>
>>> For me, 256 colors are good enough, and once I set up my vimrc to make
>>> Vim use (as closely as possible) the same colors in a console and in
>>> the GUI, I can't tell the difference by the naked eye. See
>>> http://vim.wikia.com/wiki/Using_GUI_color_settings_in_a_terminal
>>>
>>> See also ":help term.txt", especially the first two sections.
>
> I stand by the above two paragraphs.
>>>
>>>
>>> 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.
> 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.
For more options, visit https://groups.google.com/d/optout.
Re: Cursor doesn't move to top of screen when issuing a 'zt'
On Saturday, September 24, 2016 at 5:30:53 PM UTC-5, Scott Friedemann wrote:
> Thanks everyone. I've used Vim for 20 years and didn't know about scrolloff...I'm beginning to enjoy it
And that's why it was added to defaults.vim. I'm glad to see it's working as intended!
--
--
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.
For more options, visit https://groups.google.com/d/optout.
> Thanks everyone. I've used Vim for 20 years and didn't know about scrolloff...I'm beginning to enjoy it
And that's why it was added to defaults.vim. I'm glad to see it's working as intended!
--
--
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.
For more options, visit https://groups.google.com/d/optout.
Re: Cursor doesn't move to top of screen when issuing a 'zt'
Thanks everyone. I've used Vim for 20 years and didn't know about scrolloff. Perfect, but now that I've used it for that last week, I'm beginning to enjoy it and may have to leave it for a while. I'll add a comment about it in my vimrc so I don't forget.
--
--
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.
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.
For more options, visit https://groups.google.com/d/optout.
No such highlight group name: netrwMarkFile
Hi,
I am using
Vim 8.0.7, netrw v156
When I highlight a file in netrw using mf, it is not highlighted, neither on the console, nor in gvim.
If I first mark files and later a target mt , I get the error
Error detected while processing function <SNR>17_NetrwMarkFileTgt[63]..<SNR>17_LocalBrowseRefresh[57]..<SNR>17_Netr
wRefresh:
line 28:
E28: No such highlight group name: netrwMarkFile
Error detected while processing function <SNR>17_NetrwMarkFileTgt[69]..<SNR>17_NetrwRefresh:
line 28:
E28: No such highlight group name: netrwMarkFile
However, a subsequent copy mc succeeds.
It is very cumbersome to work without highlighting of marked files.
Help appreciated
--
--
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.
For more options, visit https://groups.google.com/d/optout.
I am using
Vim 8.0.7, netrw v156
When I highlight a file in netrw using mf, it is not highlighted, neither on the console, nor in gvim.
If I first mark files and later a target mt , I get the error
Error detected while processing function <SNR>17_NetrwMarkFileTgt[63]..<SNR>17_LocalBrowseRefresh[57]..<SNR>17_Netr
wRefresh:
line 28:
E28: No such highlight group name: netrwMarkFile
Error detected while processing function <SNR>17_NetrwMarkFileTgt[69]..<SNR>17_NetrwRefresh:
line 28:
E28: No such highlight group name: netrwMarkFile
However, a subsequent copy mc succeeds.
It is very cumbersome to work without highlighting of marked files.
Help appreciated
--
--
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.
For more options, visit https://groups.google.com/d/optout.
Re: Cursor doesn't move to top of screen when issuing a 'zt'
Scott Friedemann wrote:
> After installing v8.0 on two different Windows computers, when I issue
> a 'zt' to move the cursor location to the top of the screen, there are
> always 5 lines above the cursor position. I imagine this is a setting,
> but cannot find. This happens with a number of cursor movements at the
> top and bottom of the screen. As this is new behavior for me, I am
> starting to get used to it and even see the advantage, but I would
> like to be able to control it.
>
> Can someone tell me the setting that controls this?
Vim 8 will set scrolloff to 5 in defailts.vim if you don't have your own
vimrc.
--
Not too long ago, compress was something you did to garbage...
/// 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.
For more options, visit https://groups.google.com/d/optout.
> After installing v8.0 on two different Windows computers, when I issue
> a 'zt' to move the cursor location to the top of the screen, there are
> always 5 lines above the cursor position. I imagine this is a setting,
> but cannot find. This happens with a number of cursor movements at the
> top and bottom of the screen. As this is new behavior for me, I am
> starting to get used to it and even see the advantage, but I would
> like to be able to control it.
>
> Can someone tell me the setting that controls this?
Vim 8 will set scrolloff to 5 in defailts.vim if you don't have your own
vimrc.
--
Not too long ago, compress was something you did to garbage...
/// 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.
For more options, visit https://groups.google.com/d/optout.
Re: mapping :h to ;
I had the same experience -- I believe we are both suse users -- they did a good job of hiding it
from the main menu select Settings, then Configure Desktop, Workspace, Shortcuts, Global Keyboard Shortcuts,On Sat, Sep 24, 2016 at 10:46 AM, Tony Mechelynck <antoine.mechelynck@gmail.com> wrote:
P.S. I recently noticed that on some terminals, <F11> is used by the
terminal itself to toggle between Maximize and Unmaximize and is not
passed to the application. This means that I go on using my <F11> and
<S-F11> mappings in gvim to go to the next window up or down, but in
Console Vim I must fall back to the defaults Ctrl-W w and Ctrl-W W, or
else click the statusline of the desired window (it's too late for me
to relocate these mappings, practically all my F and Shift-F keys are
taken).
Similarly, depending on the terminal, Alt+something may or may not be
recognizable. When in doubt, put Vim in Insert mode and hit Ctrl-V
followed by the key in question. If nothing gets inserted, Vim did not
receive the key or key combo. If something gets inserted, it might
still be undistinguishable from the same key without Alt: repeat the
procedure (Ctrl-V + the key without Alt) and check (by putting the
cursor on each character and hitting ga if necessary) that both
strings are different.
Best regadrs,
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 .
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.
For more options, visit https://groups.google.com/d/optout.
Re: Cursor doesn't move to top of screen when issuing a 'zt'
On 2016-09-24 08:40, Scott Friedemann wrote:
> After installing v8.0 on two different Windows computers, when I
> issue a 'zt' to move the cursor location to the top of the screen,
> there are always 5 lines above the cursor position. I imagine this
> is a setting, but cannot find. This happens with a number of cursor
> movements at the top and bottom of the screen. As this is new
> behavior for me, I am starting to get used to it and even see the
> advantage, but I would like to be able to control it.
>
> Can someone tell me the setting that controls this?
This sounds suspiciously like the 'scrolloff' setting has been
set to 5. (re)setting it back to 0 should get you the standard
behavior.
-tim
--
--
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.
For more options, visit https://groups.google.com/d/optout.
> After installing v8.0 on two different Windows computers, when I
> issue a 'zt' to move the cursor location to the top of the screen,
> there are always 5 lines above the cursor position. I imagine this
> is a setting, but cannot find. This happens with a number of cursor
> movements at the top and bottom of the screen. As this is new
> behavior for me, I am starting to get used to it and even see the
> advantage, but I would like to be able to control it.
>
> Can someone tell me the setting that controls this?
This sounds suspiciously like the 'scrolloff' setting has been
set to 5. (re)setting it back to 0 should get you the standard
behavior.
-tim
--
--
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.
For more options, visit https://groups.google.com/d/optout.
Re: Cursor doesn't move to top of screen when issuing a 'zt'
See the settings for scrolloff, which controls the minimal number of screen lines to keep above and below the cursor.
On Sat, Sep 24, 2016 at 11:40 AM, Scott Friedemann <randomsf@gmail.com> wrote:
After installing v8.0 on two different Windows computers, when I issue a 'zt' to move the cursor location to the top of the screen, there are always 5 lines above the cursor position. I imagine this is a setting, but cannot find. This happens with a number of cursor movements at the top and bottom of the screen. As this is new behavior for me, I am starting to get used to it and even see the advantage, but I would like to be able to control it.
Can someone tell me the setting that controls this?
--
--
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 .
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.
For more options, visit https://groups.google.com/d/optout.
Re: Is vim supporting 24 bit colors?
On Sat, Sep 24, 2016 at 5:40 PM, Nikolay Aleksandrovich Pavlov
<zyx.vim@gmail.com> wrote:
> 2016-09-24 7:05 GMT+03:00 Tony Mechelynck <antoine.mechelynck@gmail.com>:
>> On Fri, Sep 23, 2016 at 4:26 AM, KiYugadgeter <zyouhousikaku@gmail.com> wrote:
>>> Is vim supporting 24 bit colors?
>>>
>>> I want to use vim on windows10 bash.
>>>
>>> windows 10 bash is supporting 24bit colors on beta version.
>>>
>>> Will vim support 24bit colors?
>>
>> Vim supports between 2 (2^1) and 16777216 (2^24) colors, depending on
>> how many _it can tell that_ your terminal supports. This is set by the
>> termcap variable t_Co or by the equivalent terminfo setting, and these
>> settings depend in turn on the 'term' setting (q.v.) If $TERM is not
>> set, and Vim has no way of knowing otherwise, it will set an
>> OS-dependent 'term' default: for 32- or 64-bit Windows, 'term'
>> defaults to "win32". To see the number of colours Vim thinks that your
>> terminal supports, use
>> :set t_Co?
>
> &t_Co will never give you 24-bit value. Also termcap/terminfo do not
> normally contain information about 24-bit colors support, though tmux
> developers has selected some custom setting they use to detect 24-bit
> support. Vim AFAIK does not use it.
You can set t_Co yourself early in the vimrc (before any of the following:
runtime vimrc_example.vim
source $VIMRUNTIME/vimrc_example.vim
" or the same for defaults.vim
syntax on
syntax enable
colorscheme something-or-other
) and it will stick. The problem is how to set ctermfg= and ctermbg=
values for the desired colors, since the correspondence between GUI
#rrggbb color values and cterm color indices is usually opaque.
I just tried the following in a Huge gui-enabled Vim running in console mode:
set t_Co=16777216 t_Co?
and it answered
t_Co=16777216
so it _is_ possible to set that high a value. What I don't know is
which terminals, if any, really support that many colors, nor how to
use them, and AFAIK no pre-programmed colorscheme uses that many
colors for ctermfg= ctermbg=
>
>>
>> For me, 256 colors are good enough, and once I set up my vimrc to make
>> Vim use (as closely as possible) the same colors in a console and in
>> the GUI, I can't tell the difference by the naked eye. See
>> http://vim.wikia.com/wiki/Using_GUI_color_settings_in_a_terminal
>>
>> See also ":help term.txt", especially the first two sections.
I stand by the above two paragraphs.
>>
>>
>> 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.
For more options, visit https://groups.google.com/d/optout.
<zyx.vim@gmail.com> wrote:
> 2016-09-24 7:05 GMT+03:00 Tony Mechelynck <antoine.mechelynck@gmail.com>:
>> On Fri, Sep 23, 2016 at 4:26 AM, KiYugadgeter <zyouhousikaku@gmail.com> wrote:
>>> Is vim supporting 24 bit colors?
>>>
>>> I want to use vim on windows10 bash.
>>>
>>> windows 10 bash is supporting 24bit colors on beta version.
>>>
>>> Will vim support 24bit colors?
>>
>> Vim supports between 2 (2^1) and 16777216 (2^24) colors, depending on
>> how many _it can tell that_ your terminal supports. This is set by the
>> termcap variable t_Co or by the equivalent terminfo setting, and these
>> settings depend in turn on the 'term' setting (q.v.) If $TERM is not
>> set, and Vim has no way of knowing otherwise, it will set an
>> OS-dependent 'term' default: for 32- or 64-bit Windows, 'term'
>> defaults to "win32". To see the number of colours Vim thinks that your
>> terminal supports, use
>> :set t_Co?
>
> &t_Co will never give you 24-bit value. Also termcap/terminfo do not
> normally contain information about 24-bit colors support, though tmux
> developers has selected some custom setting they use to detect 24-bit
> support. Vim AFAIK does not use it.
You can set t_Co yourself early in the vimrc (before any of the following:
runtime vimrc_example.vim
source $VIMRUNTIME/vimrc_example.vim
" or the same for defaults.vim
syntax on
syntax enable
colorscheme something-or-other
) and it will stick. The problem is how to set ctermfg= and ctermbg=
values for the desired colors, since the correspondence between GUI
#rrggbb color values and cterm color indices is usually opaque.
I just tried the following in a Huge gui-enabled Vim running in console mode:
set t_Co=16777216 t_Co?
and it answered
t_Co=16777216
so it _is_ possible to set that high a value. What I don't know is
which terminals, if any, really support that many colors, nor how to
use them, and AFAIK no pre-programmed colorscheme uses that many
colors for ctermfg= ctermbg=
>
>>
>> For me, 256 colors are good enough, and once I set up my vimrc to make
>> Vim use (as closely as possible) the same colors in a console and in
>> the GUI, I can't tell the difference by the naked eye. See
>> http://vim.wikia.com/wiki/Using_GUI_color_settings_in_a_terminal
>>
>> See also ":help term.txt", especially the first two sections.
I stand by the above two paragraphs.
>>
>>
>> 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.
For more options, visit https://groups.google.com/d/optout.
Re: mapping :h to ;
P.S. I recently noticed that on some terminals, <F11> is used by the
terminal itself to toggle between Maximize and Unmaximize and is not
passed to the application. This means that I go on using my <F11> and
<S-F11> mappings in gvim to go to the next window up or down, but in
Console Vim I must fall back to the defaults Ctrl-W w and Ctrl-W W, or
else click the statusline of the desired window (it's too late for me
to relocate these mappings, practically all my F and Shift-F keys are
taken).
Similarly, depending on the terminal, Alt+something may or may not be
recognizable. When in doubt, put Vim in Insert mode and hit Ctrl-V
followed by the key in question. If nothing gets inserted, Vim did not
receive the key or key combo. If something gets inserted, it might
still be undistinguishable from the same key without Alt: repeat the
procedure (Ctrl-V + the key without Alt) and check (by putting the
cursor on each character and hitting ga if necessary) that both
strings are different.
Best regadrs,
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.
For more options, visit https://groups.google.com/d/optout.
terminal itself to toggle between Maximize and Unmaximize and is not
passed to the application. This means that I go on using my <F11> and
<S-F11> mappings in gvim to go to the next window up or down, but in
Console Vim I must fall back to the defaults Ctrl-W w and Ctrl-W W, or
else click the statusline of the desired window (it's too late for me
to relocate these mappings, practically all my F and Shift-F keys are
taken).
Similarly, depending on the terminal, Alt+something may or may not be
recognizable. When in doubt, put Vim in Insert mode and hit Ctrl-V
followed by the key in question. If nothing gets inserted, Vim did not
receive the key or key combo. If something gets inserted, it might
still be undistinguishable from the same key without Alt: repeat the
procedure (Ctrl-V + the key without Alt) and check (by putting the
cursor on each character and hitting ga if necessary) that both
strings are different.
Best regadrs,
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.
For more options, visit https://groups.google.com/d/optout.
Cursor doesn't move to top of screen when issuing a 'zt'
After installing v8.0 on two different Windows computers, when I issue a 'zt' to move the cursor location to the top of the screen, there are always 5 lines above the cursor position. I imagine this is a setting, but cannot find. This happens with a number of cursor movements at the top and bottom of the screen. As this is new behavior for me, I am starting to get used to it and even see the advantage, but I would like to be able to control it.
Can someone tell me the setting that controls this?
--
--
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.
For more options, visit https://groups.google.com/d/optout.
Can someone tell me the setting that controls this?
--
--
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.
For more options, visit https://groups.google.com/d/optout.
Re: Is vim supporting 24 bit colors?
2016-09-24 7:05 GMT+03:00 Tony Mechelynck <antoine.mechelynck@gmail.com>:
> On Fri, Sep 23, 2016 at 4:26 AM, KiYugadgeter <zyouhousikaku@gmail.com> wrote:
>> Is vim supporting 24 bit colors?
>>
>> I want to use vim on windows10 bash.
>>
>> windows 10 bash is supporting 24bit colors on beta version.
>>
>> Will vim support 24bit colors?
>
> Vim supports between 2 (2^1) and 16777216 (2^24) colors, depending on
> how many _it can tell that_ your terminal supports. This is set by the
> termcap variable t_Co or by the equivalent terminfo setting, and these
> settings depend in turn on the 'term' setting (q.v.) If $TERM is not
> set, and Vim has no way of knowing otherwise, it will set an
> OS-dependent 'term' default: for 32- or 64-bit Windows, 'term'
> defaults to "win32". To see the number of colours Vim thinks that your
> terminal supports, use
> :set t_Co?
&t_Co will never give you 24-bit value. Also termcap/terminfo do not
normally contain information about 24-bit colors support, though tmux
developers has selected some custom setting they use to detect 24-bit
support. Vim AFAIK does not use it.
>
> For me, 256 colors are good enough, and once I set up my vimrc to make
> Vim use (as closely as possible) the same colors in a console and in
> the GUI, I can't tell the difference by the naked eye. See
> http://vim.wikia.com/wiki/Using_GUI_color_settings_in_a_terminal
>
> See also ":help term.txt", especially the first two sections.
>
>
> 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.
> 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.
For more options, visit https://groups.google.com/d/optout.
> On Fri, Sep 23, 2016 at 4:26 AM, KiYugadgeter <zyouhousikaku@gmail.com> wrote:
>> Is vim supporting 24 bit colors?
>>
>> I want to use vim on windows10 bash.
>>
>> windows 10 bash is supporting 24bit colors on beta version.
>>
>> Will vim support 24bit colors?
>
> Vim supports between 2 (2^1) and 16777216 (2^24) colors, depending on
> how many _it can tell that_ your terminal supports. This is set by the
> termcap variable t_Co or by the equivalent terminfo setting, and these
> settings depend in turn on the 'term' setting (q.v.) If $TERM is not
> set, and Vim has no way of knowing otherwise, it will set an
> OS-dependent 'term' default: for 32- or 64-bit Windows, 'term'
> defaults to "win32". To see the number of colours Vim thinks that your
> terminal supports, use
> :set t_Co?
&t_Co will never give you 24-bit value. Also termcap/terminfo do not
normally contain information about 24-bit colors support, though tmux
developers has selected some custom setting they use to detect 24-bit
support. Vim AFAIK does not use it.
>
> For me, 256 colors are good enough, and once I set up my vimrc to make
> Vim use (as closely as possible) the same colors in a console and in
> the GUI, I can't tell the difference by the naked eye. See
> http://vim.wikia.com/wiki/Using_GUI_color_settings_in_a_terminal
>
> See also ":help term.txt", especially the first two sections.
>
>
> 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.
> 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.
For more options, visit https://groups.google.com/d/optout.
Re: mapping :h to ;
On Saturday, 24 September 2016 11:40:01 UTC+2, in...@odyschrift.nl wrote:
> I am a novice in gVim. I often need the help function. <shift>:h<space>. I understand I can map this combination of 4 keystrokes to a single key.
> Is ; a good choice?
>
> The website <http://vimcasts.org/blog/2013/02/habit-breaking-habit-making/ attracted my attention, thanks to a recent post in this maillist. I understand ; is useful to repeat a character search with t,T,f,F for my period as novice.
>
> I think the best decision is to use ; for the time being, but according to the article j and k are also could alternatives. What about h and l?
>
> Has someone an advice for me?
>
> Alle
Thank for your advises. To resume: the function keys F2 till F12 (on my keyboard) are available as 'shortcuts'. It is not advisable to use keys which have already a function in the normal mode of Vim, because then I will loose possible functionality. Perhaps uppercase Q.
For my special question I can change the function of <F1>, because I want to visit the helpfile over particular subjects, mostly, and not open it generally.
When the time is there for more than 11 'shortcuts', I can think about which functionality I will offer for my 'shortcuts'. I understand there are many strategies to move the cursor. I will develop my own strategy and will pick keys dedicated to the alternative strategies. They will be not useful for me.
In the meantime, I will follow discussions over motion strategies in this mailinglist.
Again, thanks for the reactions on my novice-question.
Alle
--
--
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.
For more options, visit https://groups.google.com/d/optout.
> I am a novice in gVim. I often need the help function. <shift>:h<space>. I understand I can map this combination of 4 keystrokes to a single key.
> Is ; a good choice?
>
> The website <http://vimcasts.org/blog/2013/02/habit-breaking-habit-making/ attracted my attention, thanks to a recent post in this maillist. I understand ; is useful to repeat a character search with t,T,f,F for my period as novice.
>
> I think the best decision is to use ; for the time being, but according to the article j and k are also could alternatives. What about h and l?
>
> Has someone an advice for me?
>
> Alle
Thank for your advises. To resume: the function keys F2 till F12 (on my keyboard) are available as 'shortcuts'. It is not advisable to use keys which have already a function in the normal mode of Vim, because then I will loose possible functionality. Perhaps uppercase Q.
For my special question I can change the function of <F1>, because I want to visit the helpfile over particular subjects, mostly, and not open it generally.
When the time is there for more than 11 'shortcuts', I can think about which functionality I will offer for my 'shortcuts'. I understand there are many strategies to move the cursor. I will develop my own strategy and will pick keys dedicated to the alternative strategies. They will be not useful for me.
In the meantime, I will follow discussions over motion strategies in this mailinglist.
Again, thanks for the reactions on my novice-question.
Alle
--
--
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.
For more options, visit https://groups.google.com/d/optout.
Re: mapping :h to ;
On 2016-09-24 11:55, Tony Mechelynck wrote:
> - In most cases, it is safe to use the F and Shift-F "function" keys
> with the exception of <F1> (Help) and sometimes of <F10> (Menu)
> - If you have non-ASCII printing characters on your keyboard, you
> can use them too. For instance, my Belgian keyboard (shown at
> http://users.skynet.be/antoine.mechelynck/other/keybbe.htm )
> includes é § è ç à ù £ µ ² and ³ plus dead-key circumflex,
> dead-key-diaeresis-or-umlaut, and quite a number of special AltGr
> combinations.
To add to Tony's good suggestions, the alt+{key} pairings are usually
available too. It's an extra (half-)key press in my experience but
most terminals reliably send them.
Also, "Q" (also the <shift> there being a (half-)keypress) is one
which, while it technically is used by vim, is one that is almost
never used. Except perhaps in VimGolf.
Having vimmed for over 15 years, I tend to use Q and the F{1-9} keys
for such mappings so as to not overwrite useful functionality.
-tim
--
--
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.
For more options, visit https://groups.google.com/d/optout.
> - In most cases, it is safe to use the F and Shift-F "function" keys
> with the exception of <F1> (Help) and sometimes of <F10> (Menu)
> - If you have non-ASCII printing characters on your keyboard, you
> can use them too. For instance, my Belgian keyboard (shown at
> http://users.skynet.be/antoine.mechelynck/other/keybbe.htm )
> includes é § è ç à ù £ µ ² and ³ plus dead-key circumflex,
> dead-key-diaeresis-or-umlaut, and quite a number of special AltGr
> combinations.
To add to Tony's good suggestions, the alt+{key} pairings are usually
available too. It's an extra (half-)key press in my experience but
most terminals reliably send them.
Also, "Q" (also the <shift> there being a (half-)keypress) is one
which, while it technically is used by vim, is one that is almost
never used. Except perhaps in VimGolf.
Having vimmed for over 15 years, I tend to use Q and the F{1-9} keys
for such mappings so as to not overwrite useful functionality.
-tim
--
--
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.
For more options, visit https://groups.google.com/d/optout.
Re: mapping :h to ;
On Fri, 23 Sep 2016 23:02:04 -0700 (PDT)
info@odyschrift.nl wrote:
> I am a novice in gVim. I often need the help function.
> <shift>:h<space>. I understand I can map this combination of 4
> keystrokes to a single key. Is ; a good choice?
No, ";" is used to repeat "f", "F", "t", or "T" search. See :help ;
A better choice is <F1> since it is help on many other apps.
:nnoremap <F1> :help<space>
The default mapping for <F1> is :help<CR> which brings up the
general help file, help.txt
--
--
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.
For more options, visit https://groups.google.com/d/optout.
info@odyschrift.nl wrote:
> I am a novice in gVim. I often need the help function.
> <shift>:h<space>. I understand I can map this combination of 4
> keystrokes to a single key. Is ; a good choice?
No, ";" is used to repeat "f", "F", "t", or "T" search. See :help ;
A better choice is <F1> since it is help on many other apps.
:nnoremap <F1> :help<space>
The default mapping for <F1> is :help<CR> which brings up the
general help file, help.txt
--
--
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.
For more options, visit https://groups.google.com/d/optout.
Re: mapping :h to ;
On Sat, Sep 24, 2016 at 8:02 AM, <info@odyschrift.nl> wrote:
> I am a novice in gVim. I often need the help function. <shift>:h<space>. I understand I can map this combination of 4 keystrokes to a single key.
> Is ; a good choice?
>
> The website <http://vimcasts.org/blog/2013/02/habit-breaking-habit-making/ attracted my attention, thanks to a recent post in this maillist. I understand ; is useful to repeat a character search with t,T,f,F for my period as novice.
>
> I think the best decision is to use ; for the time being, but according to the article j and k are also could alternatives. What about h and l?
>
> Has someone an advice for me?
>
> Alle
Which keys to use as the {lhs} of a mapping depends on your keyboard
layout and on which keys are already mapped. I recommend to use keys
which don't already mean something to Vim, but which it still can
receive from the keyboard driver or the window manager, and that is
not always obvious. Here are a few hints:
- In most cases, it is safe to use the F and Shift-F "function" keys
with the exception of <F1> (Help) and sometimes of <F10> (Menu)
- If you have non-ASCII printing characters on your keyboard, you can
use them too. For instance, my Belgian keyboard (shown at
http://users.skynet.be/antoine.mechelynck/other/keybbe.htm ) includes
é § è ç à ù £ µ ² and ³ plus dead-key circumflex,
dead-key-diaeresis-or-umlaut, and quite a number of special AltGr
combinations.
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.
For more options, visit https://groups.google.com/d/optout.
> I am a novice in gVim. I often need the help function. <shift>:h<space>. I understand I can map this combination of 4 keystrokes to a single key.
> Is ; a good choice?
>
> The website <http://vimcasts.org/blog/2013/02/habit-breaking-habit-making/ attracted my attention, thanks to a recent post in this maillist. I understand ; is useful to repeat a character search with t,T,f,F for my period as novice.
>
> I think the best decision is to use ; for the time being, but according to the article j and k are also could alternatives. What about h and l?
>
> Has someone an advice for me?
>
> Alle
Which keys to use as the {lhs} of a mapping depends on your keyboard
layout and on which keys are already mapped. I recommend to use keys
which don't already mean something to Vim, but which it still can
receive from the keyboard driver or the window manager, and that is
not always obvious. Here are a few hints:
- In most cases, it is safe to use the F and Shift-F "function" keys
with the exception of <F1> (Help) and sometimes of <F10> (Menu)
- If you have non-ASCII printing characters on your keyboard, you can
use them too. For instance, my Belgian keyboard (shown at
http://users.skynet.be/antoine.mechelynck/other/keybbe.htm ) includes
é § è ç à ù £ µ ² and ³ plus dead-key circumflex,
dead-key-diaeresis-or-umlaut, and quite a number of special AltGr
combinations.
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.
For more options, visit https://groups.google.com/d/optout.
Friday, September 23, 2016
mapping :h to ;
I am a novice in gVim. I often need the help function. <shift>:h<space>. I understand I can map this combination of 4 keystrokes to a single key.
Is ; a good choice?
The website <http://vimcasts.org/blog/2013/02/habit-breaking-habit-making/ attracted my attention, thanks to a recent post in this maillist. I understand ; is useful to repeat a character search with t,T,f,F for my period as novice.
I think the best decision is to use ; for the time being, but according to the article j and k are also could alternatives. What about h and l?
Has someone an advice for me?
Alle
--
--
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.
For more options, visit https://groups.google.com/d/optout.
Is ; a good choice?
The website <http://vimcasts.org/blog/2013/02/habit-breaking-habit-making/ attracted my attention, thanks to a recent post in this maillist. I understand ; is useful to repeat a character search with t,T,f,F for my period as novice.
I think the best decision is to use ; for the time being, but according to the article j and k are also could alternatives. What about h and l?
Has someone an advice for me?
Alle
--
--
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.
For more options, visit https://groups.google.com/d/optout.
Subscribe to:
Posts (Atom)