Luc,
Thanks. I updated it and it is working. I will test and will let you know.
Thanks again.
On Friday, August 26, 2016 at 9:08:19 AM UTC-5, Amit Christian wrote:
> Luc,
>
> Thank you. I installed the plugin. But I can't get it to work.
>
> I have attached the error. I have followed the direction and got all the plugins (as shown below).
>
> git clone git@github.com:LucHermitte/lh-vim-lib.git
> git clone git@github.com:LucHermitte/lh-tags.git
> git clone git@github.com:LucHermitte/lh-dev.git
> git clone git@github.com:LucHermitte/lh-brackets.git
> git clone git@github.com:LucHermitte/searchInRuntime.git
> git clone git@github.com:LucHermitte/mu-template.git
>
> Thanks.
> On Thursday, August 25, 2016 at 6:22:06 AM UTC-5, Luc Hermitte wrote:
> > Hi,
> >
> > > I am looking into that. I am beginner/intermediate level of Vim user.
> > > And I find it really hard to add my own custom snippet in the
> > > mu-template. Can you give me some ideas of how to add simple
> > > snippets.
> > >
> > > For example
> > > -----------
> > >
> > > I would like to add the following for the trigger `openr`.
> > >
> > > OPENR, unit, filename, /GET_LUN
> > >
> > > cursor here
> > >
> > > CLOSE, unit
> > > FREE_LUN, unit
> >
> > Indeed, I see I shall add a "how do i create a new snippet/template?" section in the help.
> >
> > I don't know the filetype your snippet is for, let's say it's "foobar".
> >
> > Create a "template/foobar" directory under the vimfiles/ directory in your $HOME (%HOMEDRIVE%%HOMEPATH% in windows).
> >
> > In your $HOME/vimfiles/template/foobar, create a file named openr.template, it should get filed with default mu-template boilerplate settings.
> >
> > Then, add what you want in your template file. If you keep the default
> >
> > VimL: let s:marker_open = '<+'
> > VimL: let s:marker_close = '+>'
> >
> > Your can define placeholders with "<++>", or "<+placeholdername+>". It's even possible to accept parameters that can be injected from other snippets, or programmatically. (see :h s:Params()).
> >
> > So, I guess, your template would look like:
> >
> > VimL: let s:marker_open = '<+'
> > VimL: let s:marker_close = '+>'
> > OPENR, <+unit+>, <+filename+>, /GET_LUN
> >
> > <+cursor here+>
> >
> > CLOSE, <+unit+>
> > FREE_LUN, <+unit+>
> >
> >
> >
> > NB: I've simplified the explanation regarding the exact directory where you could put your new template files. see :h MuT-paths-override
> >
> > HTH,
> >
> > --
> > Luc Hermitte
--
--
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, August 29, 2016
Sunday, August 28, 2016
Re: How to reference characters within visually selected text within a function?
On Sunday, August 28, 2016 at 10:51:48 PM UTC, jf...@worcester.edu wrote:
> Hi,
>
> I have a question. I am trying to create a function that uses visually selected text.
So basically what I'm trying to do is create a very simple context menu with copy, cut and paste options. (See code below)
function ContextMenu() range
let choice = confirm("Context Menu", "copy\ncut\npaste")
if choice == 1
<selected_text>yank
elseif choice == 2
<selected_text>delete
elseif choice == 3
<selected_text>put
endif
endfunction
But as you can see from all my <selected_text> pseudo code, I don't know how to access the selected text from within the function.
--
--
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 have a question. I am trying to create a function that uses visually selected text.
So basically what I'm trying to do is create a very simple context menu with copy, cut and paste options. (See code below)
function ContextMenu() range
let choice = confirm("Context Menu", "copy\ncut\npaste")
if choice == 1
<selected_text>yank
elseif choice == 2
<selected_text>delete
elseif choice == 3
<selected_text>put
endif
endfunction
But as you can see from all my <selected_text> pseudo code, I don't know how to access the selected text from within the function.
--
--
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 reference characters within visually selected text within a function?
On 2016-08-28 15:33, jfeal@worcester.edu wrote:
> I have a question. I am trying to create a function that uses
> visually selected text. For example:
>
> Let's say I have
>
> 12345
>
> And I highlight the characters
>
> 234
>
> How would I access the selected text '234' within a vim function?
>
> Or another example, let's say I have
>
> 12345
> abcde
>
> And I highlight (using visual block) the characters
>
> 234
> bcd
>
> How would I access the selected text within a vim function?
There are a couple things you can do depending on what you intend to
do with the highlighted content.
- you can yank it to a register (e.g. the "z" register) and then
operate on that register
:vnoremap Q "zy:echo substitute(@z, '[c3]', 'X', 'g')<cr>
- you can use it in a substitution using the \%V token:
:%s/\%V[c3]/X/g
- you can use the mode(), line(), winline(), col(), virtcol(),
screencol(), and/or wincol() functions, passing the '< and '> marks
to the *line() and *col() functions for the beginning/ending of the
block. That will give you the offsets in the various lines,
allowing you to use the getline() function to pull those lines.
Note there are some thorny edge-cases if using mutli-byte
characters.
With a little more detail on what you're trying to do, there might be
other ideas that the list can concoct. :-)
-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 have a question. I am trying to create a function that uses
> visually selected text. For example:
>
> Let's say I have
>
> 12345
>
> And I highlight the characters
>
> 234
>
> How would I access the selected text '234' within a vim function?
>
> Or another example, let's say I have
>
> 12345
> abcde
>
> And I highlight (using visual block) the characters
>
> 234
> bcd
>
> How would I access the selected text within a vim function?
There are a couple things you can do depending on what you intend to
do with the highlighted content.
- you can yank it to a register (e.g. the "z" register) and then
operate on that register
:vnoremap Q "zy:echo substitute(@z, '[c3]', 'X', 'g')<cr>
- you can use it in a substitution using the \%V token:
:%s/\%V[c3]/X/g
- you can use the mode(), line(), winline(), col(), virtcol(),
screencol(), and/or wincol() functions, passing the '< and '> marks
to the *line() and *col() functions for the beginning/ending of the
block. That will give you the offsets in the various lines,
allowing you to use the getline() function to pull those lines.
Note there are some thorny edge-cases if using mutli-byte
characters.
With a little more detail on what you're trying to do, there might be
other ideas that the list can concoct. :-)
-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.
How to reference characters within visually selected text within a function?
Hi,
I have a question. I am trying to create a function that uses visually selected text. For example:
Let's say I have
12345
And I highlight the characters
234
How would I access the selected text '234' within a vim function?
Or another example, let's say I have
12345
abcde
And I highlight (using visual block) the characters
234
bcd
How would I access the selected text within a vim function?
Sincerely,
Jon
P.S. I just recently subscribed.
--
--
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 have a question. I am trying to create a function that uses visually selected text. For example:
Let's say I have
12345
And I highlight the characters
234
How would I access the selected text '234' within a vim function?
Or another example, let's say I have
12345
abcde
And I highlight (using visual block) the characters
234
bcd
How would I access the selected text within a vim function?
Sincerely,
Jon
P.S. I just recently subscribed.
--
--
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 7.4x ready for beta testing
Hello Vim users,
Announcing: Vim (Vi IMproved) version 7.4x BETA
This is the first BETA release for Vim 8
Please check that the distribution is OK. I haven't done one for a long
time. Report anything that isn't right. That includes a crash but also
a typo in the documentation or a missing file.
Once you have installed Vim 7.4x BETA you can find details about the
changes since Vim 7.4 with:
:help version8
Note that the reported version is 7.4.2287.
Gratitude
---------
If you like Vim, please consider helping poor children in the south of
Uganda: http://iccf-holland.org
Where to get it
---------------
The best way to obtain the latest Vim is using Git. Summary:
git clone https://github.com/vim/vim.git
More information here: http://www.vim.org/git.php
For MS-Windows most of you will want the self-installing executable:
ftp://ftp.vim.org/pub/vim/unstable/pc/gvim74x.exe
Information about which files to download for what system (don't use the
links, they are still for Vim 7.4):
http://www.vim.org/download.php
A list of mirror sites can be found here:
http://www.vim.org/mirrors.php
The files available for download:
UNIX:
sources + runtime files, bzip2 compressed:
ftp://ftp.vim.org/pub/vim/unstable/unix/vim-7.4x.tar.bz2
VARIOUS:
help files converted to HTML:
ftp://ftp.vim.org/pub/vim/unstable/doc/vim74xhtml.zip
MS-WINDOWS one-size-fits-all:
Self-installing, includes all runtime files, loads libraries dynamically:
ftp://ftp.vim.org/pub/vim/unstable/pc/gvim74x.exe
MS-WINDOWS separate files:
Runtime files:
ftp://ftp.vim.org/pub/vim/unstable/pc/vim74xrt.zip
GUI binary for Windows 95/98/NT/2000/XP/7:
ftp://ftp.vim.org/pub/vim/unstable/pc/gvim74x.zip
GUI binary with OLE support:
ftp://ftp.vim.org/pub/vim/unstable/pc/gvim74xole.zip
Console version for Windows NT/2000/XP/7:
ftp://ftp.vim.org/pub/vim/unstable/pc/vim74xw32.zip
Sources for PC (with CR-LF):
ftp://ftp.vim.org/pub/vim/unstable/pc/vim74xsrc.zip
For debugging:
ftp://ftp.vim.org/pub/vim/unstable/pc/gvim74x.pdb
ftp://ftp.vim.org/pub/vim/unstable/pc/gvim74xole.pdb
ftp://ftp.vim.org/pub/vim/unstable/pc/vim74xw32.pdb
Omitted in this version are:
- The 16-bit DOS, OS/2 and Amiga versions, these are obsolete.
- The 32-bit console version for MS-DOS/Windows 95/98
- The 16 bit MS-Windows version
Mailing lists
-------------
For user questions you can turn to the Vim mailing list. There are a
lot of tips, scripts and solutions. You can ask your Vim questions, but
only if you subscribe. See http://www.vim.org/maillist.php#vim
If you want to help Vim development, discuss new features or get the
latest patches, subscribe to the vim-dev mailing list. See
http://www.vim.org/maillist.php#vim-dev
Subject specific lists:
Macintosh issues: http://www.vim.org/maillist.php#vim-mac
Before you ask a question you should search the archives, someone may
already have given the answer.
Reporting bugs
--------------
Send them to <vim-dev@vim.org>. Please describe the problem precisely.
All the time spent on answering mail is subtracted from the time that is
spent on improving Vim! Always give a reproducible example and try to
find out which settings or other things influence the appearance of the
bug. Try starting without your own vimrc file: "vim -u NONE". Try
different machines if possible. See ":help bugs" in Vim.
Alternatively, create an issue at github and/or a pull request.
Please try to write a test that reproduces the problem and will pass
once it is fixed. See https://github.com/vim/vim
Happy Vimming!
--
Q: What kind of stuff do you do?
A: I collect hobbies.
/// 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.
Announcing: Vim (Vi IMproved) version 7.4x BETA
This is the first BETA release for Vim 8
Please check that the distribution is OK. I haven't done one for a long
time. Report anything that isn't right. That includes a crash but also
a typo in the documentation or a missing file.
Once you have installed Vim 7.4x BETA you can find details about the
changes since Vim 7.4 with:
:help version8
Note that the reported version is 7.4.2287.
Gratitude
---------
If you like Vim, please consider helping poor children in the south of
Uganda: http://iccf-holland.org
Where to get it
---------------
The best way to obtain the latest Vim is using Git. Summary:
git clone https://github.com/vim/vim.git
More information here: http://www.vim.org/git.php
For MS-Windows most of you will want the self-installing executable:
ftp://ftp.vim.org/pub/vim/unstable/pc/gvim74x.exe
Information about which files to download for what system (don't use the
links, they are still for Vim 7.4):
http://www.vim.org/download.php
A list of mirror sites can be found here:
http://www.vim.org/mirrors.php
The files available for download:
UNIX:
sources + runtime files, bzip2 compressed:
ftp://ftp.vim.org/pub/vim/unstable/unix/vim-7.4x.tar.bz2
VARIOUS:
help files converted to HTML:
ftp://ftp.vim.org/pub/vim/unstable/doc/vim74xhtml.zip
MS-WINDOWS one-size-fits-all:
Self-installing, includes all runtime files, loads libraries dynamically:
ftp://ftp.vim.org/pub/vim/unstable/pc/gvim74x.exe
MS-WINDOWS separate files:
Runtime files:
ftp://ftp.vim.org/pub/vim/unstable/pc/vim74xrt.zip
GUI binary for Windows 95/98/NT/2000/XP/7:
ftp://ftp.vim.org/pub/vim/unstable/pc/gvim74x.zip
GUI binary with OLE support:
ftp://ftp.vim.org/pub/vim/unstable/pc/gvim74xole.zip
Console version for Windows NT/2000/XP/7:
ftp://ftp.vim.org/pub/vim/unstable/pc/vim74xw32.zip
Sources for PC (with CR-LF):
ftp://ftp.vim.org/pub/vim/unstable/pc/vim74xsrc.zip
For debugging:
ftp://ftp.vim.org/pub/vim/unstable/pc/gvim74x.pdb
ftp://ftp.vim.org/pub/vim/unstable/pc/gvim74xole.pdb
ftp://ftp.vim.org/pub/vim/unstable/pc/vim74xw32.pdb
Omitted in this version are:
- The 16-bit DOS, OS/2 and Amiga versions, these are obsolete.
- The 32-bit console version for MS-DOS/Windows 95/98
- The 16 bit MS-Windows version
Mailing lists
-------------
For user questions you can turn to the Vim mailing list. There are a
lot of tips, scripts and solutions. You can ask your Vim questions, but
only if you subscribe. See http://www.vim.org/maillist.php#vim
If you want to help Vim development, discuss new features or get the
latest patches, subscribe to the vim-dev mailing list. See
http://www.vim.org/maillist.php#vim-dev
Subject specific lists:
Macintosh issues: http://www.vim.org/maillist.php#vim-mac
Before you ask a question you should search the archives, someone may
already have given the answer.
Reporting bugs
--------------
Send them to <vim-dev@vim.org>. Please describe the problem precisely.
All the time spent on answering mail is subtracted from the time that is
spent on improving Vim! Always give a reproducible example and try to
find out which settings or other things influence the appearance of the
bug. Try starting without your own vimrc file: "vim -u NONE". Try
different machines if possible. See ":help bugs" in Vim.
Alternatively, create an issue at github and/or a pull request.
Please try to write a test that reproduces the problem and will pass
once it is fixed. See https://github.com/vim/vim
Happy Vimming!
--
Q: What kind of stuff do you do?
A: I collect hobbies.
/// 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.
same filename completion across different ways of opening files
In an active gvim window, let us say I do
:e file1.txt
:sp file2.txt
:sf file3.txt
:vert sf file4.txt
:tabe file5.txt
:tabf file6.txt
As you can see, I am using different ways (:edit, :split, :splitfind
etc.,) to open up different files. Now if I do "up arrow" on any of
these type of commands, I want vim to cycle through all the files as
opposed to simple completion. For example, if I do
:sf <UP>
I want the output to be :sf file6.txt instead of :sf file3.txt. A
subsequent <UP> will result in :sf file5.txt etc.,
Ideally I would be able to specify what commands are to be grouped
this way. But it is not a big deal if the feature exists in a
non-configurable way. Is this possible? If not, can you please
consider adding it to vim?
thanks
raju
--
Kamaraju S Kusumanchi | http://raju.shoutwiki.com/wiki/Blog
--
--
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 file1.txt
:sp file2.txt
:sf file3.txt
:vert sf file4.txt
:tabe file5.txt
:tabf file6.txt
As you can see, I am using different ways (:edit, :split, :splitfind
etc.,) to open up different files. Now if I do "up arrow" on any of
these type of commands, I want vim to cycle through all the files as
opposed to simple completion. For example, if I do
:sf <UP>
I want the output to be :sf file6.txt instead of :sf file3.txt. A
subsequent <UP> will result in :sf file5.txt etc.,
Ideally I would be able to specify what commands are to be grouped
this way. But it is not a big deal if the feature exists in a
non-configurable way. Is this possible? If not, can you please
consider adding it to vim?
thanks
raju
--
Kamaraju S Kusumanchi | http://raju.shoutwiki.com/wiki/Blog
--
--
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: managing dotfiles and plugins on remote server
On Saturday, August 27, 2016 at 3:41:31 PM UTC-4, mantas.simkunas wrote:
> > Well I modified and simplified my dotfiles in github.
> > https://github.com/Luis-Henriquez-Perez/dotfiles
> >
> > It still doesn't work on the remote server but it works on my local computer.
> > I'm thinking maybe it's has something to do with the remote server.
>
> I would suggest you to try adding your vim plugins as submodules in your repository. This way you can simply clone your repository recursively and git will handle downloading your plugins for you automatically. That's how I manage my own dotfiles, here's a link for reference: https://github.com/msimkunas/dotfiles
>
> To add a submodule, type the following from the root folder of your repository: git submodule add <repo url> <destination directory>
>
> To clone your repository (including submoules): git clone --recursive <repo_url> <destination directory> (note the --recursive flag)
After using submodules I received the same error messages. At this point though I think it's probably the server. Regardless, thanks mantas.simkunas and Christian for your helpful suggestions!
--
--
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.
> > Well I modified and simplified my dotfiles in github.
> > https://github.com/Luis-Henriquez-Perez/dotfiles
> >
> > It still doesn't work on the remote server but it works on my local computer.
> > I'm thinking maybe it's has something to do with the remote server.
>
> I would suggest you to try adding your vim plugins as submodules in your repository. This way you can simply clone your repository recursively and git will handle downloading your plugins for you automatically. That's how I manage my own dotfiles, here's a link for reference: https://github.com/msimkunas/dotfiles
>
> To add a submodule, type the following from the root folder of your repository: git submodule add <repo url> <destination directory>
>
> To clone your repository (including submoules): git clone --recursive <repo_url> <destination directory> (note the --recursive flag)
After using submodules I received the same error messages. At this point though I think it's probably the server. Regardless, thanks mantas.simkunas and Christian for your helpful suggestions!
--
--
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, August 27, 2016
opinion: 'set showmatch'?
I'm in the process of relooking at my .vimrc, and I remember years ago
coming across this recommendation to do 'set sm', to help reduce
errors when typing brackets. IIRC, this was really helpful back then,
because there was no other way to see the matching LP when typing an
RP without 'set sm'.
But now playing with my settings, it appears that somewhere along the
way, vim added "highlight match" to its behaviour, and now without
'set sm', I can see the matching LP when typing an RP. So I'm just
wondering: what do folks thinking about 'set sm'?
On another note, how do I tweak the colour (both foreground, and
background) of the highlight?
thanks,
-jf
--
He who settles on the idea of the intelligent man as a static entity
only shows himself to be a fool.
--
--
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.
coming across this recommendation to do 'set sm', to help reduce
errors when typing brackets. IIRC, this was really helpful back then,
because there was no other way to see the matching LP when typing an
RP without 'set sm'.
But now playing with my settings, it appears that somewhere along the
way, vim added "highlight match" to its behaviour, and now without
'set sm', I can see the matching LP when typing an RP. So I'm just
wondering: what do folks thinking about 'set sm'?
On another note, how do I tweak the colour (both foreground, and
background) of the highlight?
thanks,
-jf
--
He who settles on the idea of the intelligent man as a static entity
only shows himself to be a fool.
--
--
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: P in Vim for windows won't put before a cursor...
Another thought: it is true that if the clipboard contains whole lines, the lines go before (P) or after (p) the line the cursor is on. Are you sure that's not what you saw?
On Sat, Aug 27, 2016 at 12:52 PM, Kevin O'Gorman <kogorman@gmail.com> wrote:
I've been using vi and vim on Unix, Linux and Windows since the mid '80s and never saw that behavior. I'm pretty sure you won't get it. I'd be horrified if you could, because they should all behave the same so that folks only have to learn how to use it once total, not once per architecture.Do you have a link to such a tutorial?--On Fri, Aug 26, 2016 at 8:15 PM, Don Cichot <opagagnamstajl@gmail.com> wrote:I'm really frustrated a and confused...
Everywhere writes that how a "big P
or p puts a yanked content before
cursor..." BUT I've seen some Mac
Vim tutorials and there when you
Put yanked content it was placed
before space that is before a word
and in windows that is inside a
word for a little p an JUST before
word with a big P...
My question is... how to make a
windows Vim behave more likely as
a Mac version of Vim...
And esspecialy, how to make "P" in
windows behave as a "P" in a Mac
version?
--
--
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 .
Kevin O'Gorman#define QUESTION ((bb) || (!bb)) /* Shakespeare */
Please consider the environment before printing this email.
--
Kevin O'Gorman
#define QUESTION ((bb) || (!bb)) /* Shakespeare */ | Please consider the environment before printing this email. |
--
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: P in Vim for windows won't put before a cursor...
I've been using vi and vim on Unix, Linux and Windows since the mid '80s and never saw that behavior. I'm pretty sure you won't get it. I'd be horrified if you could, because they should all behave the same so that folks only have to learn how to use it once total, not once per architecture.
Do you have a link to such a tutorial?On Fri, Aug 26, 2016 at 8:15 PM, Don Cichot <opagagnamstajl@gmail.com> wrote:
I'm really frustrated a and confused...
Everywhere writes that how a "big P
or p puts a yanked content before
cursor..." BUT I've seen some Mac
Vim tutorials and there when you
Put yanked content it was placed
before space that is before a word
and in windows that is inside a
word for a little p an JUST before
word with a big P...
My question is... how to make a
windows Vim behave more likely as
a Mac version of Vim...
And esspecialy, how to make "P" in
windows behave as a "P" in a Mac
version?
--
--
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 .
--
Kevin O'Gorman
#define QUESTION ((bb) || (!bb)) /* Shakespeare */ | Please consider the environment before printing this email. |
--
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: P in Vim for windows won't put before a cursor...
On Saturday, August 27, 2016 at 2:41:31 PM UTC-5, Don Cichot wrote:
> I'm really frustrated a and confused...
> Everywhere writes that how a "big P
> or p puts a yanked content before
> cursor..." BUT I've seen some Mac
> Vim tutorials and there when you
> Put yanked content it was placed
> before space that is before a word
> and in windows that is inside a
> word for a little p an JUST before
> word with a big P...
>
> My question is... how to make a
> windows Vim behave more likely as
> a Mac version of Vim...
>
> And esspecialy, how to make "P" in
> windows behave as a "P" in a Mac
> version?
Can you give an example? For me it works exactly as expected in Windows, and has for years.
With text "abc 123", if I put the cursor on the '1' and press P, I will paste just before the 1. If I press 'p' instead, I will paste just after the 1.
Is this what you expect? If not, what do you expect and why? If so, what actually happens?
--
--
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'm really frustrated a and confused...
> Everywhere writes that how a "big P
> or p puts a yanked content before
> cursor..." BUT I've seen some Mac
> Vim tutorials and there when you
> Put yanked content it was placed
> before space that is before a word
> and in windows that is inside a
> word for a little p an JUST before
> word with a big P...
>
> My question is... how to make a
> windows Vim behave more likely as
> a Mac version of Vim...
>
> And esspecialy, how to make "P" in
> windows behave as a "P" in a Mac
> version?
Can you give an example? For me it works exactly as expected in Windows, and has for years.
With text "abc 123", if I put the cursor on the '1' and press P, I will paste just before the 1. If I press 'p' instead, I will paste just after the 1.
Is this what you expect? If not, what do you expect and why? If so, what actually happens?
--
--
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: managing dotfiles and plugins on remote server
> Well I modified and simplified my dotfiles in github.
> https://github.com/Luis-Henriquez-Perez/dotfiles
>
> It still doesn't work on the remote server but it works on my local computer.
> I'm thinking maybe it's has something to do with the remote server.
I would suggest you to try adding your vim plugins as submodules in your repository. This way you can simply clone your repository recursively and git will handle downloading your plugins for you automatically. That's how I manage my own dotfiles, here's a link for reference: https://github.com/msimkunas/dotfiles
To add a submodule, type the following from the root folder of your repository: git submodule add <repo url> <destination directory>
To clone your repository (including submoules): git clone --recursive <repo_url> <destination directory> (note the --recursive flag)
--
--
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.
> https://github.com/Luis-Henriquez-Perez/dotfiles
>
> It still doesn't work on the remote server but it works on my local computer.
> I'm thinking maybe it's has something to do with the remote server.
I would suggest you to try adding your vim plugins as submodules in your repository. This way you can simply clone your repository recursively and git will handle downloading your plugins for you automatically. That's how I manage my own dotfiles, here's a link for reference: https://github.com/msimkunas/dotfiles
To add a submodule, type the following from the root folder of your repository: git submodule add <repo url> <destination directory>
To clone your repository (including submoules): git clone --recursive <repo_url> <destination directory> (note the --recursive flag)
--
--
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, August 26, 2016
P in Vim for windows won't put before a cursor...
I'm really frustrated a and confused...
Everywhere writes that how a "big P
or p puts a yanked content before
cursor..." BUT I've seen some Mac
Vim tutorials and there when you
Put yanked content it was placed
before space that is before a word
and in windows that is inside a
word for a little p an JUST before
word with a big P...
My question is... how to make a
windows Vim behave more likely as
a Mac version of Vim...
And esspecialy, how to make "P" in
windows behave as a "P" in a Mac
version?
--
--
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.
Everywhere writes that how a "big P
or p puts a yanked content before
cursor..." BUT I've seen some Mac
Vim tutorials and there when you
Put yanked content it was placed
before space that is before a word
and in windows that is inside a
word for a little p an JUST before
word with a big P...
My question is... how to make a
windows Vim behave more likely as
a Mac version of Vim...
And esspecialy, how to make "P" in
windows behave as a "P" in a Mac
version?
--
--
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: managing dotfiles and plugins on remote server
On Thursday, August 25, 2016 at 12:56:14 PM UTC-4, Luis Henriquez-Perez wrote:
> On Thursday, August 25, 2016 at 10:59:02 AM UTC-4, Christian Brabandt wrote:
> > Hi Luis!
> >
> > On Do, 25 Aug 2016, Luis Henriquez-Perez wrote:
> >
> > > I'm setting up my dotfiles on github (https://github.com/Luis-Henriquez-Perez/dotfiles.git) so that i can clone them on any unix-based remote server with internet. http://blog.smalleycreative.com/tutorials/using-git-and-github-to-manage-your-dotfiles/
> > >
> > > I use vim-plug. When I cloned my files on a server I and started vim, vim-plug was not working. I would get error messages saying "Plug" is not a vim command. I thought maybe I'd need to use this command that's on the vim-plug github page:
> > >
> > > curl -fLo ~/.vim/autoload/plug.vim --create-dirs \
> > > https://raw.githubusercontent.com/junegunn/vim-plug/master/plug.vim
> > >
> > > but "curl" doesn't work on the remote server. Does anyone have an idea of how to get the plugins set up on a remote server?
> >
> > If curl isn't available, wget should also do it. It won't however create
> > the directories.
> > Also since you already cloned vim-plug, you should be able to simply
> > copy the file to ~/.vim/autoload/plugin.vim manually.
> >
> >
> > Best,
> > Christian
> > --
> > Menschen, die immer daran denken, was andere von ihnen halten, wären
> > sehr überrascht, wenn sie wüßten, wie wenig die anderen über sie
> > nachdenken.
> > -- Bertrand A. W. Russell
> Hi!
>
> I cloned the vim.plug file into ~/.vim/autoload/plugin.vim but I still keep getting things like:
>
> line 24:
> E492: Not an editor command: Plug 'tpope/vim-fugitive' " git manager
> line 25:
> E492: Not an editor command: Plug 'sirver/ultisnips' " snippet manager
> line 26:
> E492: Not an editor command: Plug 'sheerun/vim-polyglot' " language package
>
> I though this meant I just need to run :PlugInstall in vim, but when I do that vim says:
>
> E492: Not an editor command: PlugInstall.
>
> This all happens when I'm cloning my dotfiles into a remote server. However when I try cloning on my local computer everything works fine.
>
> Why isn't vim-plug being read by vim in the remote server?
Well I modified and simplified my dotfiles in github.
https://github.com/Luis-Henriquez-Perez/dotfiles
It still doesn't work on the remote server but it works on my local computer.
I'm thinking maybe it's has something to do with the remote server.
--
--
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 Thursday, August 25, 2016 at 10:59:02 AM UTC-4, Christian Brabandt wrote:
> > Hi Luis!
> >
> > On Do, 25 Aug 2016, Luis Henriquez-Perez wrote:
> >
> > > I'm setting up my dotfiles on github (https://github.com/Luis-Henriquez-Perez/dotfiles.git) so that i can clone them on any unix-based remote server with internet. http://blog.smalleycreative.com/tutorials/using-git-and-github-to-manage-your-dotfiles/
> > >
> > > I use vim-plug. When I cloned my files on a server I and started vim, vim-plug was not working. I would get error messages saying "Plug" is not a vim command. I thought maybe I'd need to use this command that's on the vim-plug github page:
> > >
> > > curl -fLo ~/.vim/autoload/plug.vim --create-dirs \
> > > https://raw.githubusercontent.com/junegunn/vim-plug/master/plug.vim
> > >
> > > but "curl" doesn't work on the remote server. Does anyone have an idea of how to get the plugins set up on a remote server?
> >
> > If curl isn't available, wget should also do it. It won't however create
> > the directories.
> > Also since you already cloned vim-plug, you should be able to simply
> > copy the file to ~/.vim/autoload/plugin.vim manually.
> >
> >
> > Best,
> > Christian
> > --
> > Menschen, die immer daran denken, was andere von ihnen halten, wären
> > sehr überrascht, wenn sie wüßten, wie wenig die anderen über sie
> > nachdenken.
> > -- Bertrand A. W. Russell
> Hi!
>
> I cloned the vim.plug file into ~/.vim/autoload/plugin.vim but I still keep getting things like:
>
> line 24:
> E492: Not an editor command: Plug 'tpope/vim-fugitive' " git manager
> line 25:
> E492: Not an editor command: Plug 'sirver/ultisnips' " snippet manager
> line 26:
> E492: Not an editor command: Plug 'sheerun/vim-polyglot' " language package
>
> I though this meant I just need to run :PlugInstall in vim, but when I do that vim says:
>
> E492: Not an editor command: PlugInstall.
>
> This all happens when I'm cloning my dotfiles into a remote server. However when I try cloning on my local computer everything works fine.
>
> Why isn't vim-plug being read by vim in the remote server?
Well I modified and simplified my dotfiles in github.
https://github.com/Luis-Henriquez-Perez/dotfiles
It still doesn't work on the remote server but it works on my local computer.
I'm thinking maybe it's has something to do with the remote server.
--
--
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: Create Autocompletion snippets for Custom Code
Thank you. I installed the plugin. But I can't get it to work.
I have attached the error. I have followed the direction and got all the plugins (as shown below).
git clone git@github.com:LucHermitte/lh-vim-lib.git
git clone git@github.com:LucHermitte/lh-tags.git
git clone git@github.com:LucHermitte/lh-dev.git
git clone git@github.com:LucHermitte/lh-brackets.git
git clone git@github.com:LucHermitte/searchInRuntime.git
git clone git@github.com:LucHermitte/mu-template.git
Thanks.
On Thursday, August 25, 2016 at 6:22:06 AM UTC-5, Luc Hermitte wrote:
> Hi,
>
> > I am looking into that. I am beginner/intermediate level of Vim user.
> > And I find it really hard to add my own custom snippet in the
> > mu-template. Can you give me some ideas of how to add simple
> > snippets.
> >
> > For example
> > -----------
> >
> > I would like to add the following for the trigger `openr`.
> >
> > OPENR, unit, filename, /GET_LUN
> >
> > cursor here
> >
> > CLOSE, unit
> > FREE_LUN, unit
>
> Indeed, I see I shall add a "how do i create a new snippet/template?" section in the help.
>
> I don't know the filetype your snippet is for, let's say it's "foobar".
>
> Create a "template/foobar" directory under the vimfiles/ directory in your $HOME (%HOMEDRIVE%%HOMEPATH% in windows).
>
> In your $HOME/vimfiles/template/foobar, create a file named openr.template, it should get filed with default mu-template boilerplate settings.
>
> Then, add what you want in your template file. If you keep the default
>
> VimL: let s:marker_open = '<+'
> VimL: let s:marker_close = '+>'
>
> Your can define placeholders with "<++>", or "<+placeholdername+>". It's even possible to accept parameters that can be injected from other snippets, or programmatically. (see :h s:Params()).
>
> So, I guess, your template would look like:
>
> VimL: let s:marker_open = '<+'
> VimL: let s:marker_close = '+>'
> OPENR, <+unit+>, <+filename+>, /GET_LUN
>
> <+cursor here+>
>
> CLOSE, <+unit+>
> FREE_LUN, <+unit+>
>
>
>
> NB: I've simplified the explanation regarding the exact directory where you could put your new template files. see :h MuT-paths-override
>
> HTH,
>
> --
> Luc Hermitte
--
--
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, August 25, 2016
Re: managing dotfiles and plugins on remote server
On Thursday, August 25, 2016 at 10:59:02 AM UTC-4, Christian Brabandt wrote:
> Hi Luis!
>
> On Do, 25 Aug 2016, Luis Henriquez-Perez wrote:
>
> > I'm setting up my dotfiles on github (https://github.com/Luis-Henriquez-Perez/dotfiles.git) so that i can clone them on any unix-based remote server with internet. http://blog.smalleycreative.com/tutorials/using-git-and-github-to-manage-your-dotfiles/
> >
> > I use vim-plug. When I cloned my files on a server I and started vim, vim-plug was not working. I would get error messages saying "Plug" is not a vim command. I thought maybe I'd need to use this command that's on the vim-plug github page:
> >
> > curl -fLo ~/.vim/autoload/plug.vim --create-dirs \
> > https://raw.githubusercontent.com/junegunn/vim-plug/master/plug.vim
> >
> > but "curl" doesn't work on the remote server. Does anyone have an idea of how to get the plugins set up on a remote server?
>
> If curl isn't available, wget should also do it. It won't however create
> the directories.
> Also since you already cloned vim-plug, you should be able to simply
> copy the file to ~/.vim/autoload/plugin.vim manually.
>
>
> Best,
> Christian
> --
> Menschen, die immer daran denken, was andere von ihnen halten, wären
> sehr überrascht, wenn sie wüßten, wie wenig die anderen über sie
> nachdenken.
> -- Bertrand A. W. Russell
Hi!
I cloned the vim.plug file into ~/.vim/autoload/plugin.vim but I still keep getting things like:
line 24:
E492: Not an editor command: Plug 'tpope/vim-fugitive' " git manager
line 25:
E492: Not an editor command: Plug 'sirver/ultisnips' " snippet manager
line 26:
E492: Not an editor command: Plug 'sheerun/vim-polyglot' " language package
I though this meant I just need to run :PlugInstall in vim, but when I do that vim says:
E492: Not an editor command: PlugInstall.
This all happens when I'm cloning my dotfiles into a remote server. However when I try cloning on my local computer everything works fine.
Why isn't vim-plug being read by vim in the remote server?
--
--
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 Luis!
>
> On Do, 25 Aug 2016, Luis Henriquez-Perez wrote:
>
> > I'm setting up my dotfiles on github (https://github.com/Luis-Henriquez-Perez/dotfiles.git) so that i can clone them on any unix-based remote server with internet. http://blog.smalleycreative.com/tutorials/using-git-and-github-to-manage-your-dotfiles/
> >
> > I use vim-plug. When I cloned my files on a server I and started vim, vim-plug was not working. I would get error messages saying "Plug" is not a vim command. I thought maybe I'd need to use this command that's on the vim-plug github page:
> >
> > curl -fLo ~/.vim/autoload/plug.vim --create-dirs \
> > https://raw.githubusercontent.com/junegunn/vim-plug/master/plug.vim
> >
> > but "curl" doesn't work on the remote server. Does anyone have an idea of how to get the plugins set up on a remote server?
>
> If curl isn't available, wget should also do it. It won't however create
> the directories.
> Also since you already cloned vim-plug, you should be able to simply
> copy the file to ~/.vim/autoload/plugin.vim manually.
>
>
> Best,
> Christian
> --
> Menschen, die immer daran denken, was andere von ihnen halten, wären
> sehr überrascht, wenn sie wüßten, wie wenig die anderen über sie
> nachdenken.
> -- Bertrand A. W. Russell
Hi!
I cloned the vim.plug file into ~/.vim/autoload/plugin.vim but I still keep getting things like:
line 24:
E492: Not an editor command: Plug 'tpope/vim-fugitive' " git manager
line 25:
E492: Not an editor command: Plug 'sirver/ultisnips' " snippet manager
line 26:
E492: Not an editor command: Plug 'sheerun/vim-polyglot' " language package
I though this meant I just need to run :PlugInstall in vim, but when I do that vim says:
E492: Not an editor command: PlugInstall.
This all happens when I'm cloning my dotfiles into a remote server. However when I try cloning on my local computer everything works fine.
Why isn't vim-plug being read by vim in the remote server?
--
--
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: managing dotfiles and plugins on remote server
Hi Luis!
On Do, 25 Aug 2016, Luis Henriquez-Perez wrote:
> I'm setting up my dotfiles on github (https://github.com/Luis-Henriquez-Perez/dotfiles.git) so that i can clone them on any unix-based remote server with internet. http://blog.smalleycreative.com/tutorials/using-git-and-github-to-manage-your-dotfiles/
>
> I use vim-plug. When I cloned my files on a server I and started vim, vim-plug was not working. I would get error messages saying "Plug" is not a vim command. I thought maybe I'd need to use this command that's on the vim-plug github page:
>
> curl -fLo ~/.vim/autoload/plug.vim --create-dirs \
> https://raw.githubusercontent.com/junegunn/vim-plug/master/plug.vim
>
> but "curl" doesn't work on the remote server. Does anyone have an idea of how to get the plugins set up on a remote server?
If curl isn't available, wget should also do it. It won't however create
the directories.
Also since you already cloned vim-plug, you should be able to simply
copy the file to ~/.vim/autoload/plugin.vim manually.
Best,
Christian
--
Menschen, die immer daran denken, was andere von ihnen halten, wären
sehr überrascht, wenn sie wüßten, wie wenig die anderen über sie
nachdenken.
-- Bertrand A. W. Russell
--
--
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 Do, 25 Aug 2016, Luis Henriquez-Perez wrote:
> I'm setting up my dotfiles on github (https://github.com/Luis-Henriquez-Perez/dotfiles.git) so that i can clone them on any unix-based remote server with internet. http://blog.smalleycreative.com/tutorials/using-git-and-github-to-manage-your-dotfiles/
>
> I use vim-plug. When I cloned my files on a server I and started vim, vim-plug was not working. I would get error messages saying "Plug" is not a vim command. I thought maybe I'd need to use this command that's on the vim-plug github page:
>
> curl -fLo ~/.vim/autoload/plug.vim --create-dirs \
> https://raw.githubusercontent.com/junegunn/vim-plug/master/plug.vim
>
> but "curl" doesn't work on the remote server. Does anyone have an idea of how to get the plugins set up on a remote server?
If curl isn't available, wget should also do it. It won't however create
the directories.
Also since you already cloned vim-plug, you should be able to simply
copy the file to ~/.vim/autoload/plugin.vim manually.
Best,
Christian
--
Menschen, die immer daran denken, was andere von ihnen halten, wären
sehr überrascht, wenn sie wüßten, wie wenig die anderen über sie
nachdenken.
-- Bertrand A. W. Russell
--
--
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: Annoying "smart" indentation
On Friday, August 19, 2016 at 3:45:16 PM UTC-5, otajuun wrote:
> As per the documentation, I tried adding "filetype indent off" at the end, to no effect. I can turn off that annoying "feature" on a per-file basis by doing:
>
> :set indentexpr=
>
> But I have to do it for every single file I open, which is beyond annoying.
>
That's weird. The "filetype indent off" at the end of your .vimrc should have worked.
When you have a file open which has the unwanted auto-indenting, what is the output of ":verbose set indentexpr?"?
This should tell you which script set the option. If it's not an indent script, that's the problem. If it IS an indent script, then I'm not sure why it's being sourced, since you have turned off filetype indent.
--
--
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.
> As per the documentation, I tried adding "filetype indent off" at the end, to no effect. I can turn off that annoying "feature" on a per-file basis by doing:
>
> :set indentexpr=
>
> But I have to do it for every single file I open, which is beyond annoying.
>
That's weird. The "filetype indent off" at the end of your .vimrc should have worked.
When you have a file open which has the unwanted auto-indenting, what is the output of ":verbose set indentexpr?"?
This should tell you which script set the option. If it's not an indent script, that's the problem. If it IS an indent script, then I'm not sure why it's being sourced, since you have turned off filetype indent.
--
--
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 there way to show search matches in a separate window similar to Acrobat?
On Thursday, August 25, 2016 at 9:13:48 AM UTC-5, Ben Fritz wrote:
> Put the following in ~/.vim/ftplugin/qf.vim:
>
> """ begin """
> function! QfHlMatch()
> if exists('w:quickfix_title') && w:quickfix_title =~ 'vimgrep'
> if exists('b:QF_HL_id')
> call matchdelete(b:QF_HL_id)
> endif
> let pat = substitute(w:quickfix_title, '\v.*vimgrep\s+(.)(%(%(\1)@!.|\\@<=\1)+)\1.*', '\2', '')
> let b:QF_HL_id = matchadd('IncSearch', pat)
> endif
> endfun
>
Oops, b:QF_HL_id should be w:QF_HL_id throughout.
--
--
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.
> Put the following in ~/.vim/ftplugin/qf.vim:
>
> """ begin """
> function! QfHlMatch()
> if exists('w:quickfix_title') && w:quickfix_title =~ 'vimgrep'
> if exists('b:QF_HL_id')
> call matchdelete(b:QF_HL_id)
> endif
> let pat = substitute(w:quickfix_title, '\v.*vimgrep\s+(.)(%(%(\1)@!.|\\@<=\1)+)\1.*', '\2', '')
> let b:QF_HL_id = matchadd('IncSearch', pat)
> endif
> endfun
>
Oops, b:QF_HL_id should be w:QF_HL_id throughout.
--
--
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 there way to show search matches in a separate window similar to Acrobat?
On Friday, August 19, 2016 at 8:43:12 PM UTC-5, Peng Yu wrote:
> On Fri, Aug 19, 2016 at 6:19 PM, Erik Falor <ewfalor@gmail.com> wrote:
> > On Fri, Aug 19, 2016 at 05:35:48PM -0500, Peng Yu wrote:
> >> Hi, The attached image shows what is available in Acrobat, where all
> >> the search results will show in one window with search keyword
> >> highlighted. This can be convenient as one can easily see the search
> >> results across all the document and can jump to the hit easily by
> >> clicking.
> >>
> >> Is there something similar in vim?
> >
> > You may try
> >
> > :vimgrep /pattern/ % | copen
> >
> > or
> >
> > :lvimgrep /pattern/ % | lopen
> >
> > The '%' refers to the current file. You may use * and ** to refer to
> > many files at once (recursively).
>
> Thanks. Is there a way to simultaneously highlight all the matches in
> the newly opened window?
>
>
Sorry for the drive-by post, but I threw this together because you reminded me I've wanted the same thing.
Put the following in ~/.vim/ftplugin/qf.vim:
""" begin """
function! QfHlMatch()
if exists('w:quickfix_title') && w:quickfix_title =~ 'vimgrep'
if exists('b:QF_HL_id')
call matchdelete(b:QF_HL_id)
endif
let pat = substitute(w:quickfix_title, '\v.*vimgrep\s+(.)(%(%(\1)@!.|\\@<=\1)+)\1.*', '\2', '')
let b:QF_HL_id = matchadd('IncSearch', pat)
endif
endfun
augroup QF_HL
au! * <buffer>
au WinEnter <buffer> call QfHlMatch()
augroup END
call QfHlMatch()
""" end """
It uses the quickfix window title to extract the pattern used for the search. There may be a better way to get that.
If you need help understanding what's going on in that regex, consult the :help for:
/\%(
/\@<=
/\@!
etc.
The purpose of the regex is to strip out everything before the vimgrep pattern, delimited by an arbitrary character, keep up to the first non-escaped delimiter character, and strip out everything after. I've noticed it may do weird things if you use certain weird delimiters in certain cases but it mostly seems to work. There may be a better way.
I used IncSearch rather than Search because the current line in the quickfix list is already highlighted with Search. If you have different highlighting defined for each of those you'll be able to see the match even on the current line.
Matches update whenever you enter the quickfix list window. You could use CursorHold or similar if you want it to update automatically without going to the window.
--
--
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, Aug 19, 2016 at 6:19 PM, Erik Falor <ewfalor@gmail.com> wrote:
> > On Fri, Aug 19, 2016 at 05:35:48PM -0500, Peng Yu wrote:
> >> Hi, The attached image shows what is available in Acrobat, where all
> >> the search results will show in one window with search keyword
> >> highlighted. This can be convenient as one can easily see the search
> >> results across all the document and can jump to the hit easily by
> >> clicking.
> >>
> >> Is there something similar in vim?
> >
> > You may try
> >
> > :vimgrep /pattern/ % | copen
> >
> > or
> >
> > :lvimgrep /pattern/ % | lopen
> >
> > The '%' refers to the current file. You may use * and ** to refer to
> > many files at once (recursively).
>
> Thanks. Is there a way to simultaneously highlight all the matches in
> the newly opened window?
>
>
Sorry for the drive-by post, but I threw this together because you reminded me I've wanted the same thing.
Put the following in ~/.vim/ftplugin/qf.vim:
""" begin """
function! QfHlMatch()
if exists('w:quickfix_title') && w:quickfix_title =~ 'vimgrep'
if exists('b:QF_HL_id')
call matchdelete(b:QF_HL_id)
endif
let pat = substitute(w:quickfix_title, '\v.*vimgrep\s+(.)(%(%(\1)@!.|\\@<=\1)+)\1.*', '\2', '')
let b:QF_HL_id = matchadd('IncSearch', pat)
endif
endfun
augroup QF_HL
au! * <buffer>
au WinEnter <buffer> call QfHlMatch()
augroup END
call QfHlMatch()
""" end """
It uses the quickfix window title to extract the pattern used for the search. There may be a better way to get that.
If you need help understanding what's going on in that regex, consult the :help for:
/\%(
/\@<=
/\@!
etc.
The purpose of the regex is to strip out everything before the vimgrep pattern, delimited by an arbitrary character, keep up to the first non-escaped delimiter character, and strip out everything after. I've noticed it may do weird things if you use certain weird delimiters in certain cases but it mostly seems to work. There may be a better way.
I used IncSearch rather than Search because the current line in the quickfix list is already highlighted with Search. If you have different highlighting defined for each of those you'll be able to see the match even on the current line.
Matches update whenever you enter the quickfix list window. You could use CursorHold or similar if you want it to update automatically without going to the window.
--
--
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.
managing dotfiles and plugins on remote server
I'm setting up my dotfiles on github (https://github.com/Luis-Henriquez-Perez/dotfiles.git) so that i can clone them on any unix-based remote server with internet. http://blog.smalleycreative.com/tutorials/using-git-and-github-to-manage-your-dotfiles/
I use vim-plug. When I cloned my files on a server I and started vim, vim-plug was not working. I would get error messages saying "Plug" is not a vim command. I thought maybe I'd need to use this command that's on the vim-plug github page:
curl -fLo ~/.vim/autoload/plug.vim --create-dirs \
https://raw.githubusercontent.com/junegunn/vim-plug/master/plug.vim
but "curl" doesn't work on the remote server. Does anyone have an idea of how to get the plugins set up on a remote server?
--
--
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 use vim-plug. When I cloned my files on a server I and started vim, vim-plug was not working. I would get error messages saying "Plug" is not a vim command. I thought maybe I'd need to use this command that's on the vim-plug github page:
curl -fLo ~/.vim/autoload/plug.vim --create-dirs \
https://raw.githubusercontent.com/junegunn/vim-plug/master/plug.vim
but "curl" doesn't work on the remote server. Does anyone have an idea of how to get the plugins set up on a remote server?
--
--
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: Create Autocompletion snippets for Custom Code
Hi,
> I am looking into that. I am beginner/intermediate level of Vim user.
> And I find it really hard to add my own custom snippet in the
> mu-template. Can you give me some ideas of how to add simple
> snippets.
>
> For example
> -----------
>
> I would like to add the following for the trigger `openr`.
>
> OPENR, unit, filename, /GET_LUN
>
> cursor here
>
> CLOSE, unit
> FREE_LUN, unit
Indeed, I see I shall add a "how do i create a new snippet/template?" section in the help.
I don't know the filetype your snippet is for, let's say it's "foobar".
Create a "template/foobar" directory under the vimfiles/ directory in your $HOME (%HOMEDRIVE%%HOMEPATH% in windows).
In your $HOME/vimfiles/template/foobar, create a file named openr.template, it should get filed with default mu-template boilerplate settings.
Then, add what you want in your template file. If you keep the default
VimL: let s:marker_open = '<+'
VimL: let s:marker_close = '+>'
Your can define placeholders with "<++>", or "<+placeholdername+>". It's even possible to accept parameters that can be injected from other snippets, or programmatically. (see :h s:Params()).
So, I guess, your template would look like:
VimL: let s:marker_open = '<+'
VimL: let s:marker_close = '+>'
OPENR, <+unit+>, <+filename+>, /GET_LUN
<+cursor here+>
CLOSE, <+unit+>
FREE_LUN, <+unit+>
NB: I've simplified the explanation regarding the exact directory where you could put your new template files. see :h MuT-paths-override
HTH,
--
Luc Hermitte
--
--
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 looking into that. I am beginner/intermediate level of Vim user.
> And I find it really hard to add my own custom snippet in the
> mu-template. Can you give me some ideas of how to add simple
> snippets.
>
> For example
> -----------
>
> I would like to add the following for the trigger `openr`.
>
> OPENR, unit, filename, /GET_LUN
>
> cursor here
>
> CLOSE, unit
> FREE_LUN, unit
Indeed, I see I shall add a "how do i create a new snippet/template?" section in the help.
I don't know the filetype your snippet is for, let's say it's "foobar".
Create a "template/foobar" directory under the vimfiles/ directory in your $HOME (%HOMEDRIVE%%HOMEPATH% in windows).
In your $HOME/vimfiles/template/foobar, create a file named openr.template, it should get filed with default mu-template boilerplate settings.
Then, add what you want in your template file. If you keep the default
VimL: let s:marker_open = '<+'
VimL: let s:marker_close = '+>'
Your can define placeholders with "<++>", or "<+placeholdername+>". It's even possible to accept parameters that can be injected from other snippets, or programmatically. (see :h s:Params()).
So, I guess, your template would look like:
VimL: let s:marker_open = '<+'
VimL: let s:marker_close = '+>'
OPENR, <+unit+>, <+filename+>, /GET_LUN
<+cursor here+>
CLOSE, <+unit+>
FREE_LUN, <+unit+>
NB: I've simplified the explanation regarding the exact directory where you could put your new template files. see :h MuT-paths-override
HTH,
--
Luc Hermitte
--
--
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, August 24, 2016
Re: how to make the dot command repeat the command in the plugin ?
在 2016年8月24日星期三 UTC+8上午5:34:33，Enno写道：
> Using the plugin repeat.vim at https://github.com/tpope/vim-repeat, if, for example,
>
> nnoremap <leader>cc :Comment<cr>
>
> then
>
> :<c-u>Comment!<CR>:silent! call repeat#set("<leader>cc", 1)<CR>
>
> makes . repeat :Comment<cr>.
tnx it worked
--
--
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.
> Using the plugin repeat.vim at https://github.com/tpope/vim-repeat, if, for example,
>
> nnoremap <leader>cc :Comment<cr>
>
> then
>
> :<c-u>Comment!<CR>:silent! call repeat#set("<leader>cc", 1)<CR>
>
> makes . repeat :Comment<cr>.
tnx it worked
--
--
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: Create Autocompletion snippets for Custom Code
Thanks Luc.
I am looking into that. I am beginner/intermediate level of Vim user. And I find it really hard to add my own custom snippet in the mu-template. Can you give me some ideas of how to add simple snippets.
For example
-----------
I would like to add the following for the trigger `openr`.
OPENR, unit, filename, /GET_LUN
cursor here
CLOSE, unit
FREE_LUN, unit
On Tuesday, August 23, 2016 at 4:51:11 PM UTC-5, Luc Hermitte wrote:
> Hi
>
> > Is it possible to create your own autocompletion snippets using Vim
> > functionalities or plugin? I have several custom code that I would
> > like to create snippet for. I am using GVim on Windows. Most of
> > existing autocomplete plugins like NeoComplete or YouCompleteMe etc
> > do not work well on Windows. I am looking for something Vim native
> > to do this.
>
> There exist several template expander plugins that work on Window. mu-template is one of them. It's indeed 100% native (i.e. written only in viml).
> -> https://github.com/LucHermitte/mu-template
>
> If you want a smart completion, its internal completion function is available in lh-vim-lib
> https://github.com/LucHermitte/lh-vim-lib/blob/master/autoload/lh/icomplete.vim#L136
> (it has been inspired from YCM equivalent feature ; see http://vi.stackexchange.com/questions/5820/dynamic-completion regarding its birth)
>
> You'll find examples of use within mu-template code base and in the accompanying documentation.
>
> HTH,
>
> --
> Luc Hermitte
--
--
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 looking into that. I am beginner/intermediate level of Vim user. And I find it really hard to add my own custom snippet in the mu-template. Can you give me some ideas of how to add simple snippets.
For example
-----------
I would like to add the following for the trigger `openr`.
OPENR, unit, filename, /GET_LUN
cursor here
CLOSE, unit
FREE_LUN, unit
On Tuesday, August 23, 2016 at 4:51:11 PM UTC-5, Luc Hermitte wrote:
> Hi
>
> > Is it possible to create your own autocompletion snippets using Vim
> > functionalities or plugin? I have several custom code that I would
> > like to create snippet for. I am using GVim on Windows. Most of
> > existing autocomplete plugins like NeoComplete or YouCompleteMe etc
> > do not work well on Windows. I am looking for something Vim native
> > to do this.
>
> There exist several template expander plugins that work on Window. mu-template is one of them. It's indeed 100% native (i.e. written only in viml).
> -> https://github.com/LucHermitte/mu-template
>
> If you want a smart completion, its internal completion function is available in lh-vim-lib
> https://github.com/LucHermitte/lh-vim-lib/blob/master/autoload/lh/icomplete.vim#L136
> (it has been inspired from YCM equivalent feature ; see http://vi.stackexchange.com/questions/5820/dynamic-completion regarding its birth)
>
> You'll find examples of use within mu-template code base and in the accompanying documentation.
>
> HTH,
>
> --
> Luc Hermitte
--
--
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, August 23, 2016
Re: Create Autocompletion snippets for Custom Code
Hi
> Is it possible to create your own autocompletion snippets using Vim
> functionalities or plugin? I have several custom code that I would
> like to create snippet for. I am using GVim on Windows. Most of
> existing autocomplete plugins like NeoComplete or YouCompleteMe etc
> do not work well on Windows. I am looking for something Vim native
> to do this.
There exist several template expander plugins that work on Window. mu-template is one of them. It's indeed 100% native (i.e. written only in viml).
-> https://github.com/LucHermitte/mu-template
If you want a smart completion, its internal completion function is available in lh-vim-lib
https://github.com/LucHermitte/lh-vim-lib/blob/master/autoload/lh/icomplete.vim#L136
(it has been inspired from YCM equivalent feature ; see http://vi.stackexchange.com/questions/5820/dynamic-completion regarding its birth)
You'll find examples of use within mu-template code base and in the accompanying documentation.
HTH,
--
Luc Hermitte
--
--
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 it possible to create your own autocompletion snippets using Vim
> functionalities or plugin? I have several custom code that I would
> like to create snippet for. I am using GVim on Windows. Most of
> existing autocomplete plugins like NeoComplete or YouCompleteMe etc
> do not work well on Windows. I am looking for something Vim native
> to do this.
There exist several template expander plugins that work on Window. mu-template is one of them. It's indeed 100% native (i.e. written only in viml).
-> https://github.com/LucHermitte/mu-template
If you want a smart completion, its internal completion function is available in lh-vim-lib
https://github.com/LucHermitte/lh-vim-lib/blob/master/autoload/lh/icomplete.vim#L136
(it has been inspired from YCM equivalent feature ; see http://vi.stackexchange.com/questions/5820/dynamic-completion regarding its birth)
You'll find examples of use within mu-template code base and in the accompanying documentation.
HTH,
--
Luc Hermitte
--
--
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 make the dot command repeat the command in the plugin ?
Using the plugin repeat.vim at https://github.com/tpope/vim-repeat, if, for example,
nnoremap <leader>cc :Comment<cr>
then
:<c-u>Comment!<CR>:silent! call repeat#set("<leader>cc", 1)<CR>
makes . repeat :Comment<cr>.
--
--
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.
nnoremap <leader>cc :Comment<cr>
then
:<c-u>Comment!<CR>:silent! call repeat#set("<leader>cc", 1)<CR>
makes . repeat :Comment<cr>.
--
--
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.
French documentation gone AWOL
According to http://www.vim.org/translations.php the French
translation of the Vim help is "complete". Alas, AFAICT, the site
vim.dindinx.net where it used to be has gone missing.
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.
translation of the Vim help is "complete". Alas, AFAICT, the site
vim.dindinx.net where it used to be has gone missing.
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: Create Autocompletion snippets for Custom Code
> Is it possible to have completion triggers snippet with
> multiple lines?
You're asking if a completion suggestion can be multiple
lines/have new-lines in them? I'm not the definitive
source on this, but I don't think so. I tried all line
breaking methods I could think of and none of them worked.
Unfortunately for you, I think it's designed as line by
line kind of a thing, sorry.
Regards,
~Tumbler
--
--
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.
> multiple lines?
You're asking if a completion suggestion can be multiple
lines/have new-lines in them? I'm not the definitive
source on this, but I don't think so. I tried all line
breaking methods I could think of and none of them worked.
Unfortunately for you, I think it's designed as line by
line kind of a thing, sorry.
Regards,
~Tumbler
--
--
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: Create Autocompletion snippets for Custom Code
On Tuesday, August 23, 2016 at 11:45:30 AM UTC-5, Tumbler Terrall wrote:
> On Tuesday, August 23, 2016 at 11:38:19 AM UTC-5, Amit Christian wrote:
> > Is it possible to create your own autocompletion snippets using Vim functionalities or plugin? I have several custom code that I would like to create snippet for. I am using GVim on Windows. Most of existing autocomplete plugins like NeoComplete or YouCompleteMe etc do not work well on Windows. I am looking for something Vim native to do this.
> >
> > Any help, suggestions are appreciated.
> >
> > Thanks.
>
> Yes it is! Have a look at `:h complete` and `:h compl-functions`. They should get you pointed in the right direction. :)
Thanks Tumbler.
I started working on it. The Help had a example that I could work with.
inoremap <F5> <C-R>=ListMonths()<CR>
func! ListMonths()
call complete(col('.'),
['January
New line', 'February', 'March',
\ 'April', 'May', 'June', 'July', 'August', 'September',
\ 'October', 'November', 'December'])
return ''
endfunc
Is it possible to have completion triggers snippet with multiple lines? For example,
F5 > January will put
First Month.
January.
Something like that. Is it possible?
--
--
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 Tuesday, August 23, 2016 at 11:38:19 AM UTC-5, Amit Christian wrote:
> > Is it possible to create your own autocompletion snippets using Vim functionalities or plugin? I have several custom code that I would like to create snippet for. I am using GVim on Windows. Most of existing autocomplete plugins like NeoComplete or YouCompleteMe etc do not work well on Windows. I am looking for something Vim native to do this.
> >
> > Any help, suggestions are appreciated.
> >
> > Thanks.
>
> Yes it is! Have a look at `:h complete` and `:h compl-functions`. They should get you pointed in the right direction. :)
Thanks Tumbler.
I started working on it. The Help had a example that I could work with.
inoremap <F5> <C-R>=ListMonths()<CR>
func! ListMonths()
call complete(col('.'),
['January
New line', 'February', 'March',
\ 'April', 'May', 'June', 'July', 'August', 'September',
\ 'October', 'November', 'December'])
return ''
endfunc
Is it possible to have completion triggers snippet with multiple lines? For example,
F5 > January will put
First Month.
January.
Something like that. Is it possible?
--
--
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 8 pre-announcement
> Bram:
>
> > Work on Vim 8.0 is coming close to an end. I hope version 8.0 can be
> > released in about two weeks.
> >
> > This is a last chance to modify new features in a way that is not
> > backwards compatible. Once 8.0 is out we can't make changes that would
> > break plugins.
> >
>
>
> Visual C++ 6 can play a sound when build stop.
>
> so Can I have a command ':bell' to ring the bell to notify myself that my async-build job has finished and I should check the quickfix output now while I am focusing on editing or navigating source.
afplay or other command line utilities could be used to play a .wav file in the desktop gvim, but there is no way to make a voice in a terminal vim.
--
--
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.
>
> > Work on Vim 8.0 is coming close to an end. I hope version 8.0 can be
> > released in about two weeks.
> >
> > This is a last chance to modify new features in a way that is not
> > backwards compatible. Once 8.0 is out we can't make changes that would
> > break plugins.
> >
>
>
> Visual C++ 6 can play a sound when build stop.
>
> so Can I have a command ':bell' to ring the bell to notify myself that my async-build job has finished and I should check the quickfix output now while I am focusing on editing or navigating source.
afplay or other command line utilities could be used to play a .wav file in the desktop gvim, but there is no way to make a voice in a terminal vim.
--
--
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 8 pre-announcement
Bram:
> Work on Vim 8.0 is coming close to an end. I hope version 8.0 can be
> released in about two weeks.
>
> This is a last chance to modify new features in a way that is not
> backwards compatible. Once 8.0 is out we can't make changes that would
> break plugins.
>
Visual C++ 6 can play a sound when build stop.
so Can I have a command ':bell' to ring the bell to notify myself that my async-build job has finished and I should check the quickfix output now while I am focusing on editing or navigating source.
--
--
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.
> Work on Vim 8.0 is coming close to an end. I hope version 8.0 can be
> released in about two weeks.
>
> This is a last chance to modify new features in a way that is not
> backwards compatible. Once 8.0 is out we can't make changes that would
> break plugins.
>
Visual C++ 6 can play a sound when build stop.
so Can I have a command ':bell' to ring the bell to notify myself that my async-build job has finished and I should check the quickfix output now while I am focusing on editing or navigating source.
--
--
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: Create Autocompletion snippets for Custom Code
On Tuesday, August 23, 2016 at 11:38:19 AM UTC-5, Amit Christian wrote:
> Is it possible to create your own autocompletion snippets using Vim functionalities or plugin? I have several custom code that I would like to create snippet for. I am using GVim on Windows. Most of existing autocomplete plugins like NeoComplete or YouCompleteMe etc do not work well on Windows. I am looking for something Vim native to do this.
>
> Any help, suggestions are appreciated.
>
> Thanks.
Yes it is! Have a look at `:h complete` and `:h compl-functions`. They should get you pointed in the right direction. :)
--
--
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 it possible to create your own autocompletion snippets using Vim functionalities or plugin? I have several custom code that I would like to create snippet for. I am using GVim on Windows. Most of existing autocomplete plugins like NeoComplete or YouCompleteMe etc do not work well on Windows. I am looking for something Vim native to do this.
>
> Any help, suggestions are appreciated.
>
> Thanks.
Yes it is! Have a look at `:h complete` and `:h compl-functions`. They should get you pointed in the right direction. :)
--
--
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.
Create Autocompletion snippets for Custom Code
Is it possible to create your own autocompletion snippets using Vim functionalities or plugin? I have several custom code that I would like to create snippet for. I am using GVim on Windows. Most of existing autocomplete plugins like NeoComplete or YouCompleteMe etc do not work well on Windows. I am looking for something Vim native to do this.
Any help, suggestions are appreciated.
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.
Any help, suggestions are appreciated.
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.
Re: Change color of no line
On Tuesday, August 23, 2016 at 2:19:03 PM UTC+2, Christian Brabandt wrote:
> On Di, 23 Aug 2016, Ni Va wrote:
>
> > VIM - Vi IMproved 7.4 (2013 Aug 10, compiled Jun 5 2016 12:02:25)
> > MS-Windows 64-bit GUI version with OLE support
> > Included patches: 1-1901
>
> It's not in there:
> #v+
> ~/vim$ git log -v v7.4.2213 -1
> commit 58b853460add42098ab08017df9e030fb14fd34b
> Author: Bram Moolenaar <Bram@vim.org>
> Date: Sun Aug 14 19:54:54 2016 +0200
>
> patch 7.4.2213
> Problem: Cannot highlight the "~" lines at the end of a window differentl
> Solution: Add the EndOfBuffer highlighting. (Marco Hinz, James McCoy)
> #v-
>
>
>
> Best,
> Christian
> --
> Wendet sich der Pastor während der kirchlichen Trauung
> verärgert an den Bräutigam: "Junger Mann, ich bin es
> gewohnt, daß man auf meine Frage mit einem klaren "Ja"
> antwortet und nicht mit einem "Meinetwegen!"
Ok thanks I upgrade my version. Thank you very much Christian !
--
--
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 Di, 23 Aug 2016, Ni Va wrote:
>
> > VIM - Vi IMproved 7.4 (2013 Aug 10, compiled Jun 5 2016 12:02:25)
> > MS-Windows 64-bit GUI version with OLE support
> > Included patches: 1-1901
>
> It's not in there:
> #v+
> ~/vim$ git log -v v7.4.2213 -1
> commit 58b853460add42098ab08017df9e030fb14fd34b
> Author: Bram Moolenaar <Bram@vim.org>
> Date: Sun Aug 14 19:54:54 2016 +0200
>
> patch 7.4.2213
> Problem: Cannot highlight the "~" lines at the end of a window differentl
> Solution: Add the EndOfBuffer highlighting. (Marco Hinz, James McCoy)
> #v-
>
>
>
> Best,
> Christian
> --
> Wendet sich der Pastor während der kirchlichen Trauung
> verärgert an den Bräutigam: "Junger Mann, ich bin es
> gewohnt, daß man auf meine Frage mit einem klaren "Ja"
> antwortet und nicht mit einem "Meinetwegen!"
Ok thanks I upgrade my version. Thank you very much Christian !
--
--
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: Change color of no line
On Di, 23 Aug 2016, Ni Va wrote:
> VIM - Vi IMproved 7.4 (2013 Aug 10, compiled Jun 5 2016 12:02:25)
> MS-Windows 64-bit GUI version with OLE support
> Included patches: 1-1901
It's not in there:
#v+
~/vim$ git log -v v7.4.2213 -1
commit 58b853460add42098ab08017df9e030fb14fd34b
Author: Bram Moolenaar <Bram@vim.org>
Date: Sun Aug 14 19:54:54 2016 +0200
patch 7.4.2213
Problem: Cannot highlight the "~" lines at the end of a window differentl
Solution: Add the EndOfBuffer highlighting. (Marco Hinz, James McCoy)
#v-
Best,
Christian
--
Wendet sich der Pastor während der kirchlichen Trauung
verärgert an den Bräutigam: "Junger Mann, ich bin es
gewohnt, daß man auf meine Frage mit einem klaren "Ja"
antwortet und nicht mit einem "Meinetwegen!"
--
--
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 - Vi IMproved 7.4 (2013 Aug 10, compiled Jun 5 2016 12:02:25)
> MS-Windows 64-bit GUI version with OLE support
> Included patches: 1-1901
It's not in there:
#v+
~/vim$ git log -v v7.4.2213 -1
commit 58b853460add42098ab08017df9e030fb14fd34b
Author: Bram Moolenaar <Bram@vim.org>
Date: Sun Aug 14 19:54:54 2016 +0200
patch 7.4.2213
Problem: Cannot highlight the "~" lines at the end of a window differentl
Solution: Add the EndOfBuffer highlighting. (Marco Hinz, James McCoy)
#v-
Best,
Christian
--
Wendet sich der Pastor während der kirchlichen Trauung
verärgert an den Bräutigam: "Junger Mann, ich bin es
gewohnt, daß man auf meine Frage mit einem klaren "Ja"
antwortet und nicht mit einem "Meinetwegen!"
--
--
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: Change color of no line
On Tuesday, August 23, 2016 at 11:47:45 AM UTC+2, Christian Brabandt wrote:
> Am 2016-08-23 11:32, schrieb Ni Va:
> > On Tuesday, August 23, 2016 at 11:22:25 AM UTC+2, Christian Brabandt
> > wrote:
> >> Am 2016-08-23 10:32, schrieb Ni Va:
> >> > I would like to change the bg color of "no line" and of buffer.
> >> >
> >> > _________________________________
> >> > line0
> >> > line1
> >> > .
> >> > .
> >> > lineN
> >> > ~ <<< this ONE
> >> > _________________________________
> >> >
> >> > I don't succeed to find the match name pattern.
> >> >
> >>
> >> recent Vim builds include the EndOfBuffer highlighting group.
> >> You can use that to change the highlighting.
> >
> > Seems to fail :
>
> Well, check your Vim version then.
>
> Best,
> Christian
VIM - Vi IMproved 7.4 (2013 Aug 10, compiled Jun 5 2016 12:02:25)
MS-Windows 64-bit GUI version with OLE support
Included patches: 1-1901
--
--
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 2016-08-23 11:32, schrieb Ni Va:
> > On Tuesday, August 23, 2016 at 11:22:25 AM UTC+2, Christian Brabandt
> > wrote:
> >> Am 2016-08-23 10:32, schrieb Ni Va:
> >> > I would like to change the bg color of "no line" and of buffer.
> >> >
> >> > _________________________________
> >> > line0
> >> > line1
> >> > .
> >> > .
> >> > lineN
> >> > ~ <<< this ONE
> >> > _________________________________
> >> >
> >> > I don't succeed to find the match name pattern.
> >> >
> >>
> >> recent Vim builds include the EndOfBuffer highlighting group.
> >> You can use that to change the highlighting.
> >
> > Seems to fail :
>
> Well, check your Vim version then.
>
> Best,
> Christian
VIM - Vi IMproved 7.4 (2013 Aug 10, compiled Jun 5 2016 12:02:25)
MS-Windows 64-bit GUI version with OLE support
Included patches: 1-1901
--
--
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: Change color of no line
On Tuesday, August 23, 2016 at 11:47:45 AM UTC+2, Christian Brabandt wrote:
> Am 2016-08-23 11:32, schrieb Ni Va:
> > On Tuesday, August 23, 2016 at 11:22:25 AM UTC+2, Christian Brabandt
> > wrote:
> >> Am 2016-08-23 10:32, schrieb Ni Va:
> >> > I would like to change the bg color of "no line" and of buffer.
> >> >
> >> > _________________________________
> >> > line0
> >> > line1
> >> > .
> >> > .
> >> > lineN
> >> > ~ <<< this ONE
> >> > _________________________________
> >> >
> >> > I don't succeed to find the match name pattern.
> >> >
> >>
> >> recent Vim builds include the EndOfBuffer highlighting group.
> >> You can use that to change the highlighting.
> >
> > Seems to fail :
>
> Well, check your Vim version then.
>
> Best,
> Christian
IM - Vi IMproved 7.4 (2013 Aug 10, compiled Jun 5 2016 12:02:25)
MS-Windows 64-bit GUI version with OLE support
--
--
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 2016-08-23 11:32, schrieb Ni Va:
> > On Tuesday, August 23, 2016 at 11:22:25 AM UTC+2, Christian Brabandt
> > wrote:
> >> Am 2016-08-23 10:32, schrieb Ni Va:
> >> > I would like to change the bg color of "no line" and of buffer.
> >> >
> >> > _________________________________
> >> > line0
> >> > line1
> >> > .
> >> > .
> >> > lineN
> >> > ~ <<< this ONE
> >> > _________________________________
> >> >
> >> > I don't succeed to find the match name pattern.
> >> >
> >>
> >> recent Vim builds include the EndOfBuffer highlighting group.
> >> You can use that to change the highlighting.
> >
> > Seems to fail :
>
> Well, check your Vim version then.
>
> Best,
> Christian
IM - Vi IMproved 7.4 (2013 Aug 10, compiled Jun 5 2016 12:02:25)
MS-Windows 64-bit GUI version with OLE support
--
--
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: Change color of no line
Am 2016-08-23 11:32, schrieb Ni Va:
> On Tuesday, August 23, 2016 at 11:22:25 AM UTC+2, Christian Brabandt
> wrote:
>> Am 2016-08-23 10:32, schrieb Ni Va:
>> > I would like to change the bg color of "no line" and of buffer.
>> >
>> > _________________________________
>> > line0
>> > line1
>> > .
>> > .
>> > lineN
>> > ~ <<< this ONE
>> > _________________________________
>> >
>> > I don't succeed to find the match name pattern.
>> >
>>
>> recent Vim builds include the EndOfBuffer highlighting group.
>> You can use that to change the highlighting.
>
> Seems to fail :
Well, check your Vim version then.
Best,
Christian
--
--
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 Tuesday, August 23, 2016 at 11:22:25 AM UTC+2, Christian Brabandt
> wrote:
>> Am 2016-08-23 10:32, schrieb Ni Va:
>> > I would like to change the bg color of "no line" and of buffer.
>> >
>> > _________________________________
>> > line0
>> > line1
>> > .
>> > .
>> > lineN
>> > ~ <<< this ONE
>> > _________________________________
>> >
>> > I don't succeed to find the match name pattern.
>> >
>>
>> recent Vim builds include the EndOfBuffer highlighting group.
>> You can use that to change the highlighting.
>
> Seems to fail :
Well, check your Vim version then.
Best,
Christian
--
--
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: Change color of no line
On Tuesday, August 23, 2016 at 11:22:25 AM UTC+2, Christian Brabandt wrote:
> Hi,
>
>
> Am 2016-08-23 10:32, schrieb Ni Va:
> > I would like to change the bg color of "no line" and of buffer.
> >
> > _________________________________
> > line0
> > line1
> > .
> > .
> > lineN
> > ~ <<< this ONE
> > _________________________________
> >
> > I don't succeed to find the match name pattern.
> >
> > Thank you
>
> recent Vim builds include the EndOfBuffer highlighting group.
> You can use that to change the highlighting.
>
> Best,
> Christian
--
--
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,
>
>
> Am 2016-08-23 10:32, schrieb Ni Va:
> > I would like to change the bg color of "no line" and of buffer.
> >
> > _________________________________
> > line0
> > line1
> > .
> > .
> > lineN
> > ~ <<< this ONE
> > _________________________________
> >
> > I don't succeed to find the match name pattern.
> >
> > Thank you
>
> recent Vim builds include the EndOfBuffer highlighting group.
> You can use that to change the highlighting.
>
> Best,
> Christian
--
--
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: Change color of no line
On Tuesday, August 23, 2016 at 11:22:25 AM UTC+2, Christian Brabandt wrote:
> Hi,
>
>
> Am 2016-08-23 10:32, schrieb Ni Va:
> > I would like to change the bg color of "no line" and of buffer.
> >
> > _________________________________
> > line0
> > line1
> > .
> > .
> > lineN
> > ~ <<< this ONE
> > _________________________________
> >
> > I don't succeed to find the match name pattern.
> >
> > Thank you
>
> recent Vim builds include the EndOfBuffer highlighting group.
> You can use that to change the highlighting.
>
> Best,
> Christian
Seems to fail :
" Vim color file -- with 256 colour support!
"
" Author: Anthony Carapetis <anthony.carapetis@gmail.com>
" Contributors: Lucas Tadeu <lucastadeuteixeira@gmail.com>
"
" Note: Based on github's syntax highlighting theme
" Used Brian Mock's darkspectrum as a starting point/template
" Thanks to Ryan Heath for an easy list of some of the colours:
" http://rpheath.com/posts/356-github-theme-for-syntax-gem
set background=light
if version > 580
hi clear
if exists("syntax_on")
syntax reset
endif
endif
let colors_name = "github"
" {{{ General colors
hi Normal ctermfg=0 ctermbg=255 guifg=#222222 guibg=#bbbbbb
hi EndOfBuffer ctermfg=0 ctermbg=255 guifg=#222222 guibg=#bbbbbb
hi Cursor ctermfg=239 ctermbg=15 guifg=#aaaaaa guibg=#dddddd
--
--
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,
>
>
> Am 2016-08-23 10:32, schrieb Ni Va:
> > I would like to change the bg color of "no line" and of buffer.
> >
> > _________________________________
> > line0
> > line1
> > .
> > .
> > lineN
> > ~ <<< this ONE
> > _________________________________
> >
> > I don't succeed to find the match name pattern.
> >
> > Thank you
>
> recent Vim builds include the EndOfBuffer highlighting group.
> You can use that to change the highlighting.
>
> Best,
> Christian
Seems to fail :
" Vim color file -- with 256 colour support!
"
" Author: Anthony Carapetis <anthony.carapetis@gmail.com>
" Contributors: Lucas Tadeu <lucastadeuteixeira@gmail.com>
"
" Note: Based on github's syntax highlighting theme
" Used Brian Mock's darkspectrum as a starting point/template
" Thanks to Ryan Heath for an easy list of some of the colours:
" http://rpheath.com/posts/356-github-theme-for-syntax-gem
set background=light
if version > 580
hi clear
if exists("syntax_on")
syntax reset
endif
endif
let colors_name = "github"
" {{{ General colors
hi Normal ctermfg=0 ctermbg=255 guifg=#222222 guibg=#bbbbbb
hi EndOfBuffer ctermfg=0 ctermbg=255 guifg=#222222 guibg=#bbbbbb
hi Cursor ctermfg=239 ctermbg=15 guifg=#aaaaaa guibg=#dddddd
--
--
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: Change color of no line
Hi,
Am 2016-08-23 10:32, schrieb Ni Va:
> I would like to change the bg color of "no line" and of buffer.
>
> _________________________________
> line0
> line1
> .
> .
> lineN
> ~ <<< this ONE
> _________________________________
>
> I don't succeed to find the match name pattern.
>
> Thank you
recent Vim builds include the EndOfBuffer highlighting group.
You can use that to change the highlighting.
Best,
Christian
--
--
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 2016-08-23 10:32, schrieb Ni Va:
> I would like to change the bg color of "no line" and of buffer.
>
> _________________________________
> line0
> line1
> .
> .
> lineN
> ~ <<< this ONE
> _________________________________
>
> I don't succeed to find the match name pattern.
>
> Thank you
recent Vim builds include the EndOfBuffer highlighting group.
You can use that to change the highlighting.
Best,
Christian
--
--
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.
Change color of no line
Hi,
I would like to change the bg color of "no line" and of buffer.
_________________________________
line0
line1
.
.
lineN
~ <<< this ONE
_________________________________
I don't succeed to find the match name pattern.
Thank you
--
--
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 would like to change the bg color of "no line" and of buffer.
_________________________________
line0
line1
.
.
lineN
~ <<< this ONE
_________________________________
I don't succeed to find the match name pattern.
Thank you
--
--
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, August 21, 2016
Re: Changing the defaults with Vim 8
Hi Michael,
2016-8-21(Sun) 21:58:54 UTC+9 Michael Henry:
> On 08/20/2016 01:22 PM, Bram Moolenaar wrote:
> > Hirohito Higashi wrote:
> >> `set ttimeoutlen=0` will solve the above.
> >>
> >> I have invested in above setting more than a year, but the
> >> trouble does not happen even once.
> >
> > Zero only works when you are directly using a terminal. When
> > using a remote shell it might not work properly. But one
> > second is indeed too much.
> >
> > I have it set to 200, this still has some lag. I think 100
> > would work for just about everyone.
>
> I ran for a long time without trouble using 50 milliseconds.
> But even this eventually proved too long once I began using
> Alt-letter mappings in console Vim. The key sequence for Alt-j
> is <Esc>j. I would frequently press <Esc> to exit insert mode
> followed quickly by the j key, and Vim would misinterpret the
> sequence as Alt-j (which would then invoke my insert-mode
> mapping for Alt-j). I found experimentally that I could set
> ttimeoutlen to 5 to avoid most instances of this kind of
> incorrect key interpretation. This value has never proved to be
> too small in my use. I've never noticed a case of Vim timing
> out in the middle of a valid multi-key sequence and splitting it
> incorrectly into multiple keypresses, even when using Vim across
> an SSH connection; however, these connections were typically
> done over a local Ethernet, so on a slower network it's possible
> that such splitting could occur (such that Alt-j might be split
> erroneously into <Esc> followed by j). I consider this an
> unlikely case, since the multi-key sequence will probably be
> written to the network as a unit and carried in a single network
> packet, regardless of the speed of the network; still, until we
> start using uniquely decodable key sequences so we don't have to
> rely on timeouts, there will always be some risk of incorrect
> key interpretation.
>
> I think 100ms is better than 200ms as a default. I wouldn't
> suggest a default as low as 5ms due to the possible risk of
> misinterpreting multi-byte key sequences, even though I've never
> personally noticed such a failure. Users like myself who
> require shorter values can always override the default. I'll
> also note that I've seen 100ms used elsewhere, such as in Tim
> Pope's "Sensible Defaults" plugin:
> https://github.com/tpope/vim-sensible/blob/master/plugin/sensible.vim#L28
Thanks for the reply.
`set ttimeoutlen=100` is already included at patch 7.4.2232.
https://github.com/vim/vim/commit/e07e797db0c5ef1aafc650d8bb0d39fb052cf1e1
I think "100" is enough as the default.
I might be okay with a smaller value, I think that it would be changed in the individual.
--
Best regards,
Hirohito Higashi (a.k.a. h_east)
--
--
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.
2016-8-21(Sun) 21:58:54 UTC+9 Michael Henry:
> On 08/20/2016 01:22 PM, Bram Moolenaar wrote:
> > Hirohito Higashi wrote:
> >> `set ttimeoutlen=0` will solve the above.
> >>
> >> I have invested in above setting more than a year, but the
> >> trouble does not happen even once.
> >
> > Zero only works when you are directly using a terminal. When
> > using a remote shell it might not work properly. But one
> > second is indeed too much.
> >
> > I have it set to 200, this still has some lag. I think 100
> > would work for just about everyone.
>
> I ran for a long time without trouble using 50 milliseconds.
> But even this eventually proved too long once I began using
> Alt-letter mappings in console Vim. The key sequence for Alt-j
> is <Esc>j. I would frequently press <Esc> to exit insert mode
> followed quickly by the j key, and Vim would misinterpret the
> sequence as Alt-j (which would then invoke my insert-mode
> mapping for Alt-j). I found experimentally that I could set
> ttimeoutlen to 5 to avoid most instances of this kind of
> incorrect key interpretation. This value has never proved to be
> too small in my use. I've never noticed a case of Vim timing
> out in the middle of a valid multi-key sequence and splitting it
> incorrectly into multiple keypresses, even when using Vim across
> an SSH connection; however, these connections were typically
> done over a local Ethernet, so on a slower network it's possible
> that such splitting could occur (such that Alt-j might be split
> erroneously into <Esc> followed by j). I consider this an
> unlikely case, since the multi-key sequence will probably be
> written to the network as a unit and carried in a single network
> packet, regardless of the speed of the network; still, until we
> start using uniquely decodable key sequences so we don't have to
> rely on timeouts, there will always be some risk of incorrect
> key interpretation.
>
> I think 100ms is better than 200ms as a default. I wouldn't
> suggest a default as low as 5ms due to the possible risk of
> misinterpreting multi-byte key sequences, even though I've never
> personally noticed such a failure. Users like myself who
> require shorter values can always override the default. I'll
> also note that I've seen 100ms used elsewhere, such as in Tim
> Pope's "Sensible Defaults" plugin:
> https://github.com/tpope/vim-sensible/blob/master/plugin/sensible.vim#L28
Thanks for the reply.
`set ttimeoutlen=100` is already included at patch 7.4.2232.
https://github.com/vim/vim/commit/e07e797db0c5ef1aafc650d8bb0d39fb052cf1e1
I think "100" is enough as the default.
I might be okay with a smaller value, I think that it would be changed in the individual.
--
Best regards,
Hirohito Higashi (a.k.a. h_east)
--
--
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: Changing the defaults with Vim 8
On 08/20/2016 01:22 PM, Bram Moolenaar wrote:
> Hirohito Higashi wrote:
>> `set ttimeoutlen=0` will solve the above.
>>
>> I have invested in above setting more than a year, but the
>> trouble does not happen even once.
>
> Zero only works when you are directly using a terminal. When
> using a remote shell it might not work properly. But one
> second is indeed too much.
>
> I have it set to 200, this still has some lag. I think 100
> would work for just about everyone.
I ran for a long time without trouble using 50 milliseconds.
But even this eventually proved too long once I began using
Alt-letter mappings in console Vim. The key sequence for Alt-j
is <Esc>j. I would frequently press <Esc> to exit insert mode
followed quickly by the j key, and Vim would misinterpret the
sequence as Alt-j (which would then invoke my insert-mode
mapping for Alt-j). I found experimentally that I could set
ttimeoutlen to 5 to avoid most instances of this kind of
incorrect key interpretation. This value has never proved to be
too small in my use. I've never noticed a case of Vim timing
out in the middle of a valid multi-key sequence and splitting it
incorrectly into multiple keypresses, even when using Vim across
an SSH connection; however, these connections were typically
done over a local Ethernet, so on a slower network it's possible
that such splitting could occur (such that Alt-j might be split
erroneously into <Esc> followed by j). I consider this an
unlikely case, since the multi-key sequence will probably be
written to the network as a unit and carried in a single network
packet, regardless of the speed of the network; still, until we
start using uniquely decodable key sequences so we don't have to
rely on timeouts, there will always be some risk of incorrect
key interpretation.
I think 100ms is better than 200ms as a default. I wouldn't
suggest a default as low as 5ms due to the possible risk of
misinterpreting multi-byte key sequences, even though I've never
personally noticed such a failure. Users like myself who
require shorter values can always override the default. I'll
also note that I've seen 100ms used elsewhere, such as in Tim
Pope's "Sensible Defaults" plugin:
https://github.com/tpope/vim-sensible/blob/master/plugin/sensible.vim#L28
Michael Henry
--
--
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.
> Hirohito Higashi wrote:
>> `set ttimeoutlen=0` will solve the above.
>>
>> I have invested in above setting more than a year, but the
>> trouble does not happen even once.
>
> Zero only works when you are directly using a terminal. When
> using a remote shell it might not work properly. But one
> second is indeed too much.
>
> I have it set to 200, this still has some lag. I think 100
> would work for just about everyone.
I ran for a long time without trouble using 50 milliseconds.
But even this eventually proved too long once I began using
Alt-letter mappings in console Vim. The key sequence for Alt-j
is <Esc>j. I would frequently press <Esc> to exit insert mode
followed quickly by the j key, and Vim would misinterpret the
sequence as Alt-j (which would then invoke my insert-mode
mapping for Alt-j). I found experimentally that I could set
ttimeoutlen to 5 to avoid most instances of this kind of
incorrect key interpretation. This value has never proved to be
too small in my use. I've never noticed a case of Vim timing
out in the middle of a valid multi-key sequence and splitting it
incorrectly into multiple keypresses, even when using Vim across
an SSH connection; however, these connections were typically
done over a local Ethernet, so on a slower network it's possible
that such splitting could occur (such that Alt-j might be split
erroneously into <Esc> followed by j). I consider this an
unlikely case, since the multi-key sequence will probably be
written to the network as a unit and carried in a single network
packet, regardless of the speed of the network; still, until we
start using uniquely decodable key sequences so we don't have to
rely on timeouts, there will always be some risk of incorrect
key interpretation.
I think 100ms is better than 200ms as a default. I wouldn't
suggest a default as low as 5ms due to the possible risk of
misinterpreting multi-byte key sequences, even though I've never
personally noticed such a failure. Users like myself who
require shorter values can always override the default. I'll
also note that I've seen 100ms used elsewhere, such as in Tim
Pope's "Sensible Defaults" plugin:
https://github.com/tpope/vim-sensible/blob/master/plugin/sensible.vim#L28
Michael Henry
--
--
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.