On Sunday, August 31, 2014 5:42:24 AM UTC-7, Andrei Olsen wrote:
> On Sunday, August 31, 2014 12:37:36 AM UTC+2, Bob Hyam wrote:
> > On Saturday, August 30, 2014 3:33:21 PM UTC-7, Bob Hyam wrote:
> > > On Sa> >
> > > > > Sorry about that, Debian wheezy amd64. No errors seem to occur, it just remains the same version I started with. Does anyone know if this building creates a log file I could go through ? The screen updates pretty quickly so I can't say for sure there are no errors.
> > > > >
> > > > > Thanks for answering, Bob H
> > > >
> > > > I run the latest 429 on Debian Wheezy as I write.
> > > >
> > > > Maybe you have several versions on your system. Did you try:
> > > > which -a vim
> > > >
> > > > Also, did you try to run your locally compiled file, that is in /usr/src/vim/src/ ?
> > > >
> > > > What "hg summary" says?
> > >
> > > alpha:/usr/src/vim>root#hg summary
> > > Not trusting file /usr/src/vim/.hg/hgrc from untrusted user bobh, group users
> > > Not trusting file /usr/src/vim/.hg/hgrc from untrusted user bobh, group users
> > > parent: 6142:4c08173b8b95 tip
> > > Add files missing from 7.4.408.
> > > branch: default
> > > commit: 1 modified, 2 unknown
> > > update: (current)
> > >
> > > BobH
> >
> > Sorry forgot to in include .hg/hgrc file -
> >
> > [paths]
> > default = https://vim.googlecode.com/hg/
> >
> > BH
>
> I suspect "hg pull" fails because .hgrc is owned by the different user other than the one that is running Mercurial.
>
> You can change the ownership or see this:
> http://mercurial.selenic.com/wiki/Trust
Andrei - I appreciate your help, the info you gave me led me to do some experimenting. What I found was that I did not have $HOME/.hgrc file, so I created one ! It now seems to be OK. I am a bit confused, I didn't erase this file and as I said in the original post I've been using the same procedure for years.
Thanks again Bob.
--
--
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 31, 2014
Re: Can't get vim-go bundle to work
> I've installed the vim-go bundle on my Ubuntu 14.04 system. I'm using pathogen
> to manage my plugins.
>
> I ran a git clone to pull the program into my .vim/bundle directory.
>
> Unfortunately, for some reason, the vim-go environment doesn't seem to
> work. For example, when I run :help godocs it comes back with "Sorry, no help
> for godocs". Or, for example, when I put the cursor under a go
> keyword and type :godocs, I get: E492: Not an editor command godocs
Well - then read pathogen docs. It tells you how to run helptags
automatically (or switch to a plugin manager which does this
automatically in a sane way (on install/update) such as
vim-addon-mangaer)
> When I first ran .vim, it started downloading a number of things that
> were necessary for it to work. However, at this point, none of the
> listed vim-go commands actually does anything, only giving "Not an
> editor command: godoc"
You're missing basic understanding of Vim commands:
vim provided commands are lower case only
plugin provided commands are always starting with upper case.
Vim of course does not ship with :godoc command AFAIK for obvious
reasons. Thus reread documentation, open the plugin/* files and look for
command which defines a plugin provided Vim command or such.
Also ensure plugin and filetype is enabled in your .vimrc
Eg see here http://vim-wiki.mawercer.de/wiki/topic/vimrc.html
(This wiki also contains some hints about how to debug/troubleshoot
VimL)
Marc Weber
--
--
You received this message from the "vim_use" maillist.
Do not top-post! Type your reply below the text you are replying to.
For more information, visit http://www.vim.org/maillist.php
---
You received this message because you are subscribed to the Google Groups "vim_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
> to manage my plugins.
>
> I ran a git clone to pull the program into my .vim/bundle directory.
>
> Unfortunately, for some reason, the vim-go environment doesn't seem to
> work. For example, when I run :help godocs it comes back with "Sorry, no help
> for godocs". Or, for example, when I put the cursor under a go
> keyword and type :godocs, I get: E492: Not an editor command godocs
Well - then read pathogen docs. It tells you how to run helptags
automatically (or switch to a plugin manager which does this
automatically in a sane way (on install/update) such as
vim-addon-mangaer)
> When I first ran .vim, it started downloading a number of things that
> were necessary for it to work. However, at this point, none of the
> listed vim-go commands actually does anything, only giving "Not an
> editor command: godoc"
You're missing basic understanding of Vim commands:
vim provided commands are lower case only
plugin provided commands are always starting with upper case.
Vim of course does not ship with :godoc command AFAIK for obvious
reasons. Thus reread documentation, open the plugin/* files and look for
command which defines a plugin provided Vim command or such.
Also ensure plugin and filetype is enabled in your .vimrc
Eg see here http://vim-wiki.mawercer.de/wiki/topic/vimrc.html
(This wiki also contains some hints about how to debug/troubleshoot
VimL)
Marc Weber
--
--
You received this message from the "vim_use" maillist.
Do not top-post! Type your reply below the text you are replying to.
For more information, visit http://www.vim.org/maillist.php
---
You received this message because you are subscribed to the Google Groups "vim_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Can't get vim-go bundle to work
Hi all,
I've installed the vim-go bundle on my Ubuntu 14.04 system. I'm using pathogen
to manage my plugins.
I ran a git clone to pull the program into my .vim/bundle directory.
Unfortunately, for some reason, the vim-go environment doesn't seem to
work. For example, when I run :help godocs it comes back with "Sorry, no help
for godocs". Or, for example, when I put the cursor under a go keyword and type :godocs, I get: E492: Not an editor command godocs
my ~/.vim/bundle directory looks like this:
mysystem:~/.vim/bundle> ls
nerdtree vim-go
When I first ran .vim, it started downloading a number of things that were necessary for it to work. However, at this point, none of the listed vim-go commands actually does anything, only giving "Not an editor command: godoc"
(to pick a specific example).
Running :scriptnames shows the following vim-go objects
37: ~/.vim/bundle/vim-go/plugin/goinstall.vim
...
50: ~/.vim/bundle/vim-go/ftplugin/go.vim
51: ~/.vim/bundle/vim-go/compiler/go.vim
52: ~/.vim/bundle/vim-go/ftplugin/go/fmt.vim
53: ~/.vim/bundle/vim-go/ftplugin/go/godef.vim
54: ~/.vim/bundle/vim-go/ftplugin/go/godoc.vim
55: ~/.vim/bundle/vim-go/ftplugin/go/goerrcheck.vim
56: ~/.vim/bundle/vim-go/ftplugin/go/gooracle.vim
57: ~/.vim/bundle/vim-go/ftplugin/go/goplay.vim
58: ~/.vim/bundle/vim-go/ftplugin/go/gosnippet.vim
59: ~/.vim/bundle/vim-go/ftplugin/go/gotagbar.vim
60: ~/.vim/bundle/vim-go/ftplugin/go/gotools.vim
61: ~/.vim/bundle/vim-go/ftplugin/go/import.vim
62: ~/.vim/bundle/vim-go/ftplugin/go/lint.vim
63: ~/.vim/bundle/vim-go/indent/go.vim
Anybody know what's going on or what I'm missing?
Thanks,
Braun Brelin
--
--
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've installed the vim-go bundle on my Ubuntu 14.04 system. I'm using pathogen
to manage my plugins.
I ran a git clone to pull the program into my .vim/bundle directory.
Unfortunately, for some reason, the vim-go environment doesn't seem to
work. For example, when I run :help godocs it comes back with "Sorry, no help
for godocs". Or, for example, when I put the cursor under a go keyword and type :godocs, I get: E492: Not an editor command godocs
my ~/.vim/bundle directory looks like this:
mysystem:~/.vim/bundle> ls
nerdtree vim-go
When I first ran .vim, it started downloading a number of things that were necessary for it to work. However, at this point, none of the listed vim-go commands actually does anything, only giving "Not an editor command: godoc"
(to pick a specific example).
Running :scriptnames shows the following vim-go objects
37: ~/.vim/bundle/vim-go/plugin/goinstall.vim
...
50: ~/.vim/bundle/vim-go/ftplugin/go.vim
51: ~/.vim/bundle/vim-go/compiler/go.vim
52: ~/.vim/bundle/vim-go/ftplugin/go/fmt.vim
53: ~/.vim/bundle/vim-go/ftplugin/go/godef.vim
54: ~/.vim/bundle/vim-go/ftplugin/go/godoc.vim
55: ~/.vim/bundle/vim-go/ftplugin/go/goerrcheck.vim
56: ~/.vim/bundle/vim-go/ftplugin/go/gooracle.vim
57: ~/.vim/bundle/vim-go/ftplugin/go/goplay.vim
58: ~/.vim/bundle/vim-go/ftplugin/go/gosnippet.vim
59: ~/.vim/bundle/vim-go/ftplugin/go/gotagbar.vim
60: ~/.vim/bundle/vim-go/ftplugin/go/gotools.vim
61: ~/.vim/bundle/vim-go/ftplugin/go/import.vim
62: ~/.vim/bundle/vim-go/ftplugin/go/lint.vim
63: ~/.vim/bundle/vim-go/indent/go.vim
Anybody know what's going on or what I'm missing?
Thanks,
Braun Brelin
--
--
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: Downloading Plugins
On Sunday, August 31, 2014 6:20:40 AM UTC-7, Robert Cressman wrote:
> On Saturday, August 30, 2014 11:24:04 PM UTC-7, Vanilla Ice wrote:
> > You have to have 'git' in the path. You'll have to follow these steps with accuracy:
> >
> > https://github.com/gmarik/Vundle.vim/wiki/Vundle-for-Windows
>
> I'll give it a read and try later today!
> Thanks!
> Bob
I re-read the article as suggested by Vanilla Ice and found a simple error in the "rtp" line. Vindle now works and all is good!! I will now go back to learning move about using Vim (which seems to be an amazing program!) Thanks to all!!
--
--
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 Saturday, August 30, 2014 11:24:04 PM UTC-7, Vanilla Ice wrote:
> > You have to have 'git' in the path. You'll have to follow these steps with accuracy:
> >
> > https://github.com/gmarik/Vundle.vim/wiki/Vundle-for-Windows
>
> I'll give it a read and try later today!
> Thanks!
> Bob
I re-read the article as suggested by Vanilla Ice and found a simple error in the "rtp" line. Vindle now works and all is good!! I will now go back to learning move about using Vim (which seems to be an amazing program!) Thanks to all!!
--
--
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: Downloading Plugins
On Saturday, August 30, 2014 11:24:04 PM UTC-7, Vanilla Ice wrote:
> You have to have 'git' in the path. You'll have to follow these steps with accuracy:
>
> https://github.com/gmarik/Vundle.vim/wiki/Vundle-for-Windows
I'll give it a read and try later today!
Thanks!
Bob
--
--
You received this message from the "vim_use" maillist.
Do not top-post! Type your reply below the text you are replying to.
For more information, visit http://www.vim.org/maillist.php
---
You received this message because you are subscribed to the Google Groups "vim_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
> You have to have 'git' in the path. You'll have to follow these steps with accuracy:
>
> https://github.com/gmarik/Vundle.vim/wiki/Vundle-for-Windows
I'll give it a read and try later today!
Thanks!
Bob
--
--
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: Unable to update Vim past ver 7.4.408
On Sunday, August 31, 2014 12:37:36 AM UTC+2, Bob Hyam wrote:
> On Saturday, August 30, 2014 3:33:21 PM UTC-7, Bob Hyam wrote:
> > On Sa> >
> > > > Sorry about that, Debian wheezy amd64. No errors seem to occur, it just remains the same version I started with. Does anyone know if this building creates a log file I could go through ? The screen updates pretty quickly so I can't say for sure there are no errors.
> > > >
> > > > Thanks for answering, Bob H
> > >
> > > I run the latest 429 on Debian Wheezy as I write.
> > >
> > > Maybe you have several versions on your system. Did you try:
> > > which -a vim
> > >
> > > Also, did you try to run your locally compiled file, that is in /usr/src/vim/src/ ?
> > >
> > > What "hg summary" says?
> >
> > alpha:/usr/src/vim>root#hg summary
> > Not trusting file /usr/src/vim/.hg/hgrc from untrusted user bobh, group users
> > Not trusting file /usr/src/vim/.hg/hgrc from untrusted user bobh, group users
> > parent: 6142:4c08173b8b95 tip
> > Add files missing from 7.4.408.
> > branch: default
> > commit: 1 modified, 2 unknown
> > update: (current)
> >
> > BobH
>
> Sorry forgot to in include .hg/hgrc file -
>
> [paths]
> default = https://vim.googlecode.com/hg/
>
> BH
I suspect "hg pull" fails because .hgrc is owned by the different user other than the one that is running Mercurial.
You can change the ownership or see this:
http://mercurial.selenic.com/wiki/Trust
--
--
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 Saturday, August 30, 2014 3:33:21 PM UTC-7, Bob Hyam wrote:
> > On Sa> >
> > > > Sorry about that, Debian wheezy amd64. No errors seem to occur, it just remains the same version I started with. Does anyone know if this building creates a log file I could go through ? The screen updates pretty quickly so I can't say for sure there are no errors.
> > > >
> > > > Thanks for answering, Bob H
> > >
> > > I run the latest 429 on Debian Wheezy as I write.
> > >
> > > Maybe you have several versions on your system. Did you try:
> > > which -a vim
> > >
> > > Also, did you try to run your locally compiled file, that is in /usr/src/vim/src/ ?
> > >
> > > What "hg summary" says?
> >
> > alpha:/usr/src/vim>root#hg summary
> > Not trusting file /usr/src/vim/.hg/hgrc from untrusted user bobh, group users
> > Not trusting file /usr/src/vim/.hg/hgrc from untrusted user bobh, group users
> > parent: 6142:4c08173b8b95 tip
> > Add files missing from 7.4.408.
> > branch: default
> > commit: 1 modified, 2 unknown
> > update: (current)
> >
> > BobH
>
> Sorry forgot to in include .hg/hgrc file -
>
> [paths]
> default = https://vim.googlecode.com/hg/
>
> BH
I suspect "hg pull" fails because .hgrc is owned by the different user other than the one that is running Mercurial.
You can change the ownership or see this:
http://mercurial.selenic.com/wiki/Trust
--
--
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: Unable to update Vim past ver 7.4.408
On Sunday, August 31, 2014 12:33:21 AM UTC+2, Bob Hyam wrote:
> On Sa> >
> > > Sorry about that, Debian wheezy amd64. No errors seem to occur, it just remains the same version I started with. Does anyone know if this building creates a log file I could go through ? The screen updates pretty quickly so I can't say for sure there are no errors.
> > >
> > > Thanks for answering, Bob H
> >
> > I run the latest 429 on Debian Wheezy as I write.
> >
> > Maybe you have several versions on your system. Did you try:
> > which -a vim
> >
> > Also, did you try to run your locally compiled file, that is in /usr/src/vim/src/ ?
> >
> > What "hg summary" says?
>
> alpha:/usr/src/vim>root#hg summary
> Not trusting file /usr/src/vim/.hg/hgrc from untrusted user bobh, group users
> Not trusting file /usr/src/vim/.hg/hgrc from untrusted user bobh, group users
> parent: 6142:4c08173b8b95 tip
> Add files missing from 7.4.408.
> branch: default
> commit: 1 modified, 2 unknown
> update: (current)
>
> BobH
Update field says you have the latest revision checked out and tip is rev 6142, which is not the latest, so "hg pull" must have failed somehow.
Run command manually and look for error messages.
--
--
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 Sa> >
> > > Sorry about that, Debian wheezy amd64. No errors seem to occur, it just remains the same version I started with. Does anyone know if this building creates a log file I could go through ? The screen updates pretty quickly so I can't say for sure there are no errors.
> > >
> > > Thanks for answering, Bob H
> >
> > I run the latest 429 on Debian Wheezy as I write.
> >
> > Maybe you have several versions on your system. Did you try:
> > which -a vim
> >
> > Also, did you try to run your locally compiled file, that is in /usr/src/vim/src/ ?
> >
> > What "hg summary" says?
>
> alpha:/usr/src/vim>root#hg summary
> Not trusting file /usr/src/vim/.hg/hgrc from untrusted user bobh, group users
> Not trusting file /usr/src/vim/.hg/hgrc from untrusted user bobh, group users
> parent: 6142:4c08173b8b95 tip
> Add files missing from 7.4.408.
> branch: default
> commit: 1 modified, 2 unknown
> update: (current)
>
> BobH
Update field says you have the latest revision checked out and tip is rev 6142, which is not the latest, so "hg pull" must have failed somehow.
Run command manually and look for error messages.
--
--
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: set backupdir=~/.vim/backup//
On Sunday, August 31, 2014 6:24:06 AM UTC+12, Kaleb Hornsby wrote:
> In my vimrc, I have setup backupdir to be `set backupdir=~/.cache/vim/backup//,/var/tmp//,/tmp//`. The double slash does not seem to be working for 'backupdir', but it does work for 'undodir' and 'directory'.
>
> Instead of seeing a file like `%home%user%foo%bar.txt~` in my ~/.cache/vim/backup directory, I am seeing simply bar.txt~. This can lead to conflicts.
>
> Is this a vim bug or oversight, or have I configured something incorrectly?
I think this is something like an accepted oversight, because you can use an autocommand to rename the backup file how you like. I use such to timestamp the backup file names, a sort of poor man's versioning system. (I keep resolving to change to a proper system like git or hg, where every save is committed to a repository, but have not got round to it.)
Maybe (tested minimally, er, once):
function! StampBackup()
let bup = globpath(&backupdir, expand('%:t') . &bex)
if bup != ""
let modified = substitute(bup, '/[^/]*$', '', '') . '/' .
\ substitute(expand('%:p'), "/", "%", 'g')
if rename(bup, modified)
echoerr "failed rename of backup " . bup . " to " . modified
endif
endif
endfunction
augroup StampBackup
au! BufWritePost,FileWritePost * call StampBackup()
augroup END
Regards, John Little
--
--
You received this message from the "vim_use" maillist.
Do not top-post! Type your reply below the text you are replying to.
For more information, visit http://www.vim.org/maillist.php
---
You received this message because you are subscribed to the Google Groups "vim_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
> In my vimrc, I have setup backupdir to be `set backupdir=~/.cache/vim/backup//,/var/tmp//,/tmp//`. The double slash does not seem to be working for 'backupdir', but it does work for 'undodir' and 'directory'.
>
> Instead of seeing a file like `%home%user%foo%bar.txt~` in my ~/.cache/vim/backup directory, I am seeing simply bar.txt~. This can lead to conflicts.
>
> Is this a vim bug or oversight, or have I configured something incorrectly?
I think this is something like an accepted oversight, because you can use an autocommand to rename the backup file how you like. I use such to timestamp the backup file names, a sort of poor man's versioning system. (I keep resolving to change to a proper system like git or hg, where every save is committed to a repository, but have not got round to it.)
Maybe (tested minimally, er, once):
function! StampBackup()
let bup = globpath(&backupdir, expand('%:t') . &bex)
if bup != ""
let modified = substitute(bup, '/[^/]*$', '', '') . '/' .
\ substitute(expand('%:p'), "/", "%", 'g')
if rename(bup, modified)
echoerr "failed rename of backup " . bup . " to " . modified
endif
endif
endfunction
augroup StampBackup
au! BufWritePost,FileWritePost * call StampBackup()
augroup END
Regards, John Little
--
--
You received this message from the "vim_use" maillist.
Do not top-post! Type your reply below the text you are replying to.
For more information, visit http://www.vim.org/maillist.php
---
You received this message because you are subscribed to the Google Groups "vim_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Saturday, August 30, 2014
Re: Downloading Plugins
You have to have 'git' in the path. You'll have to follow these steps with accuracy:
https://github.com/gmarik/Vundle.vim/wiki/Vundle-for-Windows
--
--
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/gmarik/Vundle.vim/wiki/Vundle-for-Windows
--
--
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: Downloading Plugins
To all those who have answered my original message, THANK YOU!!
I have been constantly reading and working with Vim, Git Bash, an several downloaded manuals. Things are starting to become clearer. I have given up for the time being on downloading any plugins, other than Vundle. I have learned how to "clone" them from github. I also followed a Youtube video on installation of Vundle.
Vundle loaded where I think it should go (~/Vim/vim74/vimfiles/bundle. I put the necessary coding in my _vimrc. When I entered the command :PluginInstall on the command line, I get 2 errors (E116 & E684). Checking the log, I get the following info:
[2014-08-30 20:21:43]
[2014-08-30 20:21:43] Plugin gmarik/vundle.vim
[2014-08-30 20:21:43] $ git clone --recursive "https://github.com/gmarik/vundle.vim.git" "C:\Users\Robert A. Cressman\.vim\bundle\vundle.vim"
[2014-08-30 20:21:43] > 'git' is not recognized as an internal or external command,
[2014-08-30 20:21:43] > operable program or batch file.
[2014-08-30 20:21:43] >
[2014-08-30 20:21:44]
[2014-08-30 20:21:44] Helptags:
[2014-08-30 20:21:44] Helptags: 0 plugins processed
Appreciate any ideas, or comments!
Bob
p.s. I've been to several sites for assistance,and you guys are the only ones kind enough to answer! 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.
I have been constantly reading and working with Vim, Git Bash, an several downloaded manuals. Things are starting to become clearer. I have given up for the time being on downloading any plugins, other than Vundle. I have learned how to "clone" them from github. I also followed a Youtube video on installation of Vundle.
Vundle loaded where I think it should go (~/Vim/vim74/vimfiles/bundle. I put the necessary coding in my _vimrc. When I entered the command :PluginInstall on the command line, I get 2 errors (E116 & E684). Checking the log, I get the following info:
[2014-08-30 20:21:43]
[2014-08-30 20:21:43] Plugin gmarik/vundle.vim
[2014-08-30 20:21:43] $ git clone --recursive "https://github.com/gmarik/vundle.vim.git" "C:\Users\Robert A. Cressman\.vim\bundle\vundle.vim"
[2014-08-30 20:21:43] > 'git' is not recognized as an internal or external command,
[2014-08-30 20:21:43] > operable program or batch file.
[2014-08-30 20:21:43] >
[2014-08-30 20:21:44]
[2014-08-30 20:21:44] Helptags:
[2014-08-30 20:21:44] Helptags: 0 plugins processed
Appreciate any ideas, or comments!
Bob
p.s. I've been to several sites for assistance,and you guys are the only ones kind enough to answer! 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: Unable to update Vim past ver 7.4.408
On Saturday, August 30, 2014 5:37:36 PM UTC-5, Bob Hyam wrote:
> > >
> > > What "hg summary" says?
> >
> > alpha:/usr/src/vim>root#hg summary
> > Not trusting file /usr/src/vim/.hg/hgrc from untrusted user bobh, group users
> > Not trusting file /usr/src/vim/.hg/hgrc from untrusted user bobh, group users
> > parent: 6142:4c08173b8b95 tip
> > Add files missing from 7.4.408.
> > branch: default
> > commit: 1 modified, 2 unknown
> > update: (current)
> >
> > BobH
>
> Sorry forgot to in include .hg/hgrc file -
>
> [paths]
> default = https://vim.googlecode.com/hg/
>
> BH
So it looks like you're having some sort of problem with hg. What is the output of "hg pull", and then "hg update", when you run them manually?
--
--
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.
> > >
> > > What "hg summary" says?
> >
> > alpha:/usr/src/vim>root#hg summary
> > Not trusting file /usr/src/vim/.hg/hgrc from untrusted user bobh, group users
> > Not trusting file /usr/src/vim/.hg/hgrc from untrusted user bobh, group users
> > parent: 6142:4c08173b8b95 tip
> > Add files missing from 7.4.408.
> > branch: default
> > commit: 1 modified, 2 unknown
> > update: (current)
> >
> > BobH
>
> Sorry forgot to in include .hg/hgrc file -
>
> [paths]
> default = https://vim.googlecode.com/hg/
>
> BH
So it looks like you're having some sort of problem with hg. What is the output of "hg pull", and then "hg update", when you run them manually?
--
--
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: Unable to update Vim past ver 7.4.408
On Saturday, August 30, 2014 3:33:21 PM UTC-7, Bob Hyam wrote:
> On Sa> >
> > > Sorry about that, Debian wheezy amd64. No errors seem to occur, it just remains the same version I started with. Does anyone know if this building creates a log file I could go through ? The screen updates pretty quickly so I can't say for sure there are no errors.
> > >
> > > Thanks for answering, Bob H
> >
> > I run the latest 429 on Debian Wheezy as I write.
> >
> > Maybe you have several versions on your system. Did you try:
> > which -a vim
> >
> > Also, did you try to run your locally compiled file, that is in /usr/src/vim/src/ ?
> >
> > What "hg summary" says?
>
> alpha:/usr/src/vim>root#hg summary
> Not trusting file /usr/src/vim/.hg/hgrc from untrusted user bobh, group users
> Not trusting file /usr/src/vim/.hg/hgrc from untrusted user bobh, group users
> parent: 6142:4c08173b8b95 tip
> Add files missing from 7.4.408.
> branch: default
> commit: 1 modified, 2 unknown
> update: (current)
>
> BobH
Sorry forgot to in include .hg/hgrc file -
[paths]
default = https://vim.googlecode.com/hg/
BH
--
--
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 Sa> >
> > > Sorry about that, Debian wheezy amd64. No errors seem to occur, it just remains the same version I started with. Does anyone know if this building creates a log file I could go through ? The screen updates pretty quickly so I can't say for sure there are no errors.
> > >
> > > Thanks for answering, Bob H
> >
> > I run the latest 429 on Debian Wheezy as I write.
> >
> > Maybe you have several versions on your system. Did you try:
> > which -a vim
> >
> > Also, did you try to run your locally compiled file, that is in /usr/src/vim/src/ ?
> >
> > What "hg summary" says?
>
> alpha:/usr/src/vim>root#hg summary
> Not trusting file /usr/src/vim/.hg/hgrc from untrusted user bobh, group users
> Not trusting file /usr/src/vim/.hg/hgrc from untrusted user bobh, group users
> parent: 6142:4c08173b8b95 tip
> Add files missing from 7.4.408.
> branch: default
> commit: 1 modified, 2 unknown
> update: (current)
>
> BobH
Sorry forgot to in include .hg/hgrc file -
[paths]
default = https://vim.googlecode.com/hg/
BH
--
--
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: Unable to update Vim past ver 7.4.408
On Sa> >
> > Sorry about that, Debian wheezy amd64. No errors seem to occur, it just remains the same version I started with. Does anyone know if this building creates a log file I could go through ? The screen updates pretty quickly so I can't say for sure there are no errors.
> >
> > Thanks for answering, Bob H
>
> I run the latest 429 on Debian Wheezy as I write.
>
> Maybe you have several versions on your system. Did you try:
> which -a vim
>
> Also, did you try to run your locally compiled file, that is in /usr/src/vim/src/ ?
>
> What "hg summary" says?
alpha:/usr/src/vim>root#hg summary
Not trusting file /usr/src/vim/.hg/hgrc from untrusted user bobh, group users
Not trusting file /usr/src/vim/.hg/hgrc from untrusted user bobh, group users
parent: 6142:4c08173b8b95 tip
Add files missing from 7.4.408.
branch: default
commit: 1 modified, 2 unknown
update: (current)
BobH
--
--
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.
> > Sorry about that, Debian wheezy amd64. No errors seem to occur, it just remains the same version I started with. Does anyone know if this building creates a log file I could go through ? The screen updates pretty quickly so I can't say for sure there are no errors.
> >
> > Thanks for answering, Bob H
>
> I run the latest 429 on Debian Wheezy as I write.
>
> Maybe you have several versions on your system. Did you try:
> which -a vim
>
> Also, did you try to run your locally compiled file, that is in /usr/src/vim/src/ ?
>
> What "hg summary" says?
alpha:/usr/src/vim>root#hg summary
Not trusting file /usr/src/vim/.hg/hgrc from untrusted user bobh, group users
Not trusting file /usr/src/vim/.hg/hgrc from untrusted user bobh, group users
parent: 6142:4c08173b8b95 tip
Add files missing from 7.4.408.
branch: default
commit: 1 modified, 2 unknown
update: (current)
BobH
--
--
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: an update for the romanian spell checker
sâmbătă, 30 august 2014, 19:10:59 UTC+3, Bram Moolenaar a scris:
> Vanilla Ice wrote:
>
>
>
> > > > miercuri, 13 august 2014, 15:51:25 UTC+3, Bram Moolenaar a scris:
>
> > > > > Vanilla Ice wrote:
>
> > > > >
>
> > > > >> <snip>
>
> > > > >
>
> > > > > Thanks for figuring this out. Can you please send me the .dic and .aff
>
> > > > >
>
> > > > > files you used to generate this .spl file? Or better: the URL of the
>
> > > > >
>
> > > > > files to be downloaded and a diff on top of that.
>
> > > > >
>
> > > >
>
> > > > By all means. I hope that there aren't other mistakes (I loaded a
>
> > > > text-formatted translation of "Caves of Steel" by Asimov and it
>
> > > > looked ok). In any case, it should be better than the old one,
>
> > > > which is quite unusable for correct fonts/new grammar rules.
>
> > > >
>
> > > > 1. The URL is: http://sourceforge.net/projects/rospell/files/Romanian%20dictionaries/dict-3.3.10/ro_RO.3.3.10.zip
>
> > > >
>
> > > > and
>
> > > > 2. The diff file is attached to this post.
>
> > >
>
> > > I tried using that zip file with the diff, but I get lots of errors.
>
> > >
>
> > > The first one is easy to fix: Comment-out the KEY line.
>
> > >
>
> > > I get lots of "Trailing text" errors.
>
> > > I get a few "Duplicate character in MAP" errors.
>
> > >
>
> > > For the cp1250 encoded file I get lots of "Conversion failure" errors.
>
> > >
>
> > > Did you not see these errors or did you just ignore them?
>
> >
>
> > The "trailing text" errors (a lot of them!) are caused by the fact
>
> > that the authors of the spell files didn't put a comment start after
>
> > the 5th element. From what i've seen in the vim spell.c source, the
>
> > error messages are actually warnings, i.e. they don't affect the
>
> > parsing.
>
>
>
> I think these are grammar annotations. The problem is that they could
>
> be mistakes. I think we need to add a flag that tells the parser that
>
> the fifth item is to be ignored. We could edit the file and put the
>
> changes in the diff, but that means the diff gets outdated very quickly.
Indeed. Perhaps the 'mkspell' code should be as rigorous/relaxed as the parsing program which the authors of the spell files use day by day when testing their creation (hunspell?).
> > I don't know what the effect of the "Duplicate character in MAP" error
>
> > is, but i've seen no invalid spell behaviour with the new .spl.
>
> >
>
> > Also, i just generated the ro.cp1250.spl file in gvim/Windows using
>
> >
>
> > :set encoding=cp1250
>
> > :mkspell ro ro_RO in the right folder, and had no other errors than the above ones (no "Conversion failure" errors)
>
>
>
> I'm doing this on Ubuntu. The locale handling is a bit complicated and
>
> iconv is quite strict. I hope someone can make it work on Ubuntu
>
> without errors. The errors might be harmless, but they will cause other
>
> errors to go unnoticed.
I did a bit of reading, and - one of the issues is the fact that the "right" diacritics in Romanian are *not* in the cp1250 standard. But the wrong ones (cedilla form) were used nonetheless with Windows versions up to including XP. The right format is ș,ț (no cedilla). Also the new Romanian writing rules have changed the usage of î inside words with â. The right diacritics, i read, are in the ISO8859-16 (Latin10) standard. Ideally, for spelling there should be some standard to allow both forms and adapt to the user's preferences ... So, one language, two set of rules.
But, on my ArchLinux machine, i can't get Vim to save/convert the ro_RO.aff from utf-8 to iso8859-16 without errors, or to set encoding to this format and run mkspell without conversion errors.
Regards
--
--
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.
> Vanilla Ice wrote:
>
>
>
> > > > miercuri, 13 august 2014, 15:51:25 UTC+3, Bram Moolenaar a scris:
>
> > > > > Vanilla Ice wrote:
>
> > > > >
>
> > > > >> <snip>
>
> > > > >
>
> > > > > Thanks for figuring this out. Can you please send me the .dic and .aff
>
> > > > >
>
> > > > > files you used to generate this .spl file? Or better: the URL of the
>
> > > > >
>
> > > > > files to be downloaded and a diff on top of that.
>
> > > > >
>
> > > >
>
> > > > By all means. I hope that there aren't other mistakes (I loaded a
>
> > > > text-formatted translation of "Caves of Steel" by Asimov and it
>
> > > > looked ok). In any case, it should be better than the old one,
>
> > > > which is quite unusable for correct fonts/new grammar rules.
>
> > > >
>
> > > > 1. The URL is: http://sourceforge.net/projects/rospell/files/Romanian%20dictionaries/dict-3.3.10/ro_RO.3.3.10.zip
>
> > > >
>
> > > > and
>
> > > > 2. The diff file is attached to this post.
>
> > >
>
> > > I tried using that zip file with the diff, but I get lots of errors.
>
> > >
>
> > > The first one is easy to fix: Comment-out the KEY line.
>
> > >
>
> > > I get lots of "Trailing text" errors.
>
> > > I get a few "Duplicate character in MAP" errors.
>
> > >
>
> > > For the cp1250 encoded file I get lots of "Conversion failure" errors.
>
> > >
>
> > > Did you not see these errors or did you just ignore them?
>
> >
>
> > The "trailing text" errors (a lot of them!) are caused by the fact
>
> > that the authors of the spell files didn't put a comment start after
>
> > the 5th element. From what i've seen in the vim spell.c source, the
>
> > error messages are actually warnings, i.e. they don't affect the
>
> > parsing.
>
>
>
> I think these are grammar annotations. The problem is that they could
>
> be mistakes. I think we need to add a flag that tells the parser that
>
> the fifth item is to be ignored. We could edit the file and put the
>
> changes in the diff, but that means the diff gets outdated very quickly.
Indeed. Perhaps the 'mkspell' code should be as rigorous/relaxed as the parsing program which the authors of the spell files use day by day when testing their creation (hunspell?).
> > I don't know what the effect of the "Duplicate character in MAP" error
>
> > is, but i've seen no invalid spell behaviour with the new .spl.
>
> >
>
> > Also, i just generated the ro.cp1250.spl file in gvim/Windows using
>
> >
>
> > :set encoding=cp1250
>
> > :mkspell ro ro_RO in the right folder, and had no other errors than the above ones (no "Conversion failure" errors)
>
>
>
> I'm doing this on Ubuntu. The locale handling is a bit complicated and
>
> iconv is quite strict. I hope someone can make it work on Ubuntu
>
> without errors. The errors might be harmless, but they will cause other
>
> errors to go unnoticed.
I did a bit of reading, and - one of the issues is the fact that the "right" diacritics in Romanian are *not* in the cp1250 standard. But the wrong ones (cedilla form) were used nonetheless with Windows versions up to including XP. The right format is ș,ț (no cedilla). Also the new Romanian writing rules have changed the usage of î inside words with â. The right diacritics, i read, are in the ISO8859-16 (Latin10) standard. Ideally, for spelling there should be some standard to allow both forms and adapt to the user's preferences ... So, one language, two set of rules.
But, on my ArchLinux machine, i can't get Vim to save/convert the ro_RO.aff from utf-8 to iso8859-16 without errors, or to set encoding to this format and run mkspell without conversion errors.
Regards
--
--
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.
set backupdir=~/.vim/backup//
In my vimrc, I have setup backupdir to be `set backupdir=~/.cache/vim/backup//,/var/tmp//,/tmp//`. The double slash does not seem to be working for 'backupdir', but it does work for 'undodir' and 'directory'.
Instead of seeing a file like `%home%user%foo%bar.txt~` in my ~/.cache/vim/backup directory, I am seeing simply bar.txt~. This can lead to conflicts.
Is this a vim bug or oversight, or have I configured something incorrectly?
--
--
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.
Instead of seeing a file like `%home%user%foo%bar.txt~` in my ~/.cache/vim/backup directory, I am seeing simply bar.txt~. This can lead to conflicts.
Is this a vim bug or oversight, or have I configured something incorrectly?
--
--
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: an update for the romanian spell checker
Vanilla Ice wrote:
> > > miercuri, 13 august 2014, 15:51:25 UTC+3, Bram Moolenaar a scris:
> > > > Vanilla Ice wrote:
> > > >
> > > >> <snip>
> > > >
> > > > Thanks for figuring this out. Can you please send me the .dic and .aff
> > > >
> > > > files you used to generate this .spl file? Or better: the URL of the
> > > >
> > > > files to be downloaded and a diff on top of that.
> > > >
> > >
> > > By all means. I hope that there aren't other mistakes (I loaded a
> > > text-formatted translation of "Caves of Steel" by Asimov and it
> > > looked ok). In any case, it should be better than the old one,
> > > which is quite unusable for correct fonts/new grammar rules.
> > >
> > > 1. The URL is: http://sourceforge.net/projects/rospell/files/Romanian%20dictionaries/dict-3.3.10/ro_RO.3.3.10.zip
> > >
> > > and
> > > 2. The diff file is attached to this post.
> >
> > I tried using that zip file with the diff, but I get lots of errors.
> >
> > The first one is easy to fix: Comment-out the KEY line.
> >
> > I get lots of "Trailing text" errors.
> > I get a few "Duplicate character in MAP" errors.
> >
> > For the cp1250 encoded file I get lots of "Conversion failure" errors.
> >
> > Did you not see these errors or did you just ignore them?
>
> The "trailing text" errors (a lot of them!) are caused by the fact
> that the authors of the spell files didn't put a comment start after
> the 5th element. From what i've seen in the vim spell.c source, the
> error messages are actually warnings, i.e. they don't affect the
> parsing.
I think these are grammar annotations. The problem is that they could
be mistakes. I think we need to add a flag that tells the parser that
the fifth item is to be ignored. We could edit the file and put the
changes in the diff, but that means the diff gets outdated very quickly.
> I don't know what the effect of the "Duplicate character in MAP" error
> is, but i've seen no invalid spell behaviour with the new .spl.
>
> Also, i just generated the ro.cp1250.spl file in gvim/Windows using
>
> :set encoding=cp1250
> :mkspell ro ro_RO in the right folder, and had no other errors than the above ones (no "Conversion failure" errors)
I'm doing this on Ubuntu. The locale handling is a bit complicated and
iconv is quite strict. I hope someone can make it work on Ubuntu
without errors. The errors might be harmless, but they will cause other
errors to go unnoticed.
Generally, I would really appreciate it when someone takes upon him the
task to update the spell files. Once you get the hang of it when doing
one language, it should get easier for others.
--
From "know your smileys":
:q vi user saying, "How do I get out of this damn emacs editor?"
/// 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.
> > > miercuri, 13 august 2014, 15:51:25 UTC+3, Bram Moolenaar a scris:
> > > > Vanilla Ice wrote:
> > > >
> > > >> <snip>
> > > >
> > > > Thanks for figuring this out. Can you please send me the .dic and .aff
> > > >
> > > > files you used to generate this .spl file? Or better: the URL of the
> > > >
> > > > files to be downloaded and a diff on top of that.
> > > >
> > >
> > > By all means. I hope that there aren't other mistakes (I loaded a
> > > text-formatted translation of "Caves of Steel" by Asimov and it
> > > looked ok). In any case, it should be better than the old one,
> > > which is quite unusable for correct fonts/new grammar rules.
> > >
> > > 1. The URL is: http://sourceforge.net/projects/rospell/files/Romanian%20dictionaries/dict-3.3.10/ro_RO.3.3.10.zip
> > >
> > > and
> > > 2. The diff file is attached to this post.
> >
> > I tried using that zip file with the diff, but I get lots of errors.
> >
> > The first one is easy to fix: Comment-out the KEY line.
> >
> > I get lots of "Trailing text" errors.
> > I get a few "Duplicate character in MAP" errors.
> >
> > For the cp1250 encoded file I get lots of "Conversion failure" errors.
> >
> > Did you not see these errors or did you just ignore them?
>
> The "trailing text" errors (a lot of them!) are caused by the fact
> that the authors of the spell files didn't put a comment start after
> the 5th element. From what i've seen in the vim spell.c source, the
> error messages are actually warnings, i.e. they don't affect the
> parsing.
I think these are grammar annotations. The problem is that they could
be mistakes. I think we need to add a flag that tells the parser that
the fifth item is to be ignored. We could edit the file and put the
changes in the diff, but that means the diff gets outdated very quickly.
> I don't know what the effect of the "Duplicate character in MAP" error
> is, but i've seen no invalid spell behaviour with the new .spl.
>
> Also, i just generated the ro.cp1250.spl file in gvim/Windows using
>
> :set encoding=cp1250
> :mkspell ro ro_RO in the right folder, and had no other errors than the above ones (no "Conversion failure" errors)
I'm doing this on Ubuntu. The locale handling is a bit complicated and
iconv is quite strict. I hope someone can make it work on Ubuntu
without errors. The errors might be harmless, but they will cause other
errors to go unnoticed.
Generally, I would really appreciate it when someone takes upon him the
task to update the spell files. Once you get the hang of it when doing
one language, it should get easier for others.
--
From "know your smileys":
:q vi user saying, "How do I get out of this damn emacs editor?"
/// Bram Moolenaar -- Bram@Moolenaar.net -- http://www.Moolenaar.net \\\
/// sponsor Vim, vote for features -- http://www.Vim.org/sponsor/ \\\
\\\ an exciting new programming language -- http://www.Zimbu.org ///
\\\ help me help AIDS victims -- http://ICCF-Holland.org ///
--
--
You received this message from the "vim_use" maillist.
Do not top-post! Type your reply below the text you are replying to.
For more information, visit http://www.vim.org/maillist.php
---
You received this message because you are subscribed to the Google Groups "vim_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Re: Unable to update Vim past ver 7.4.408
On Saturday, August 30, 2014 5:07:10 AM UTC+2, Bob Hyam wrote:
> On Friday, August 29, 2014 6:12:19 PM UTC-7, Eric Christopherson wrote:
> > On Fri, Aug 29, 2014, Bob Hyam wrote:
> >
> > > I have been using this script to update Vim for a long time, but noe I cannot upgrade beyond patch 408.
> >
> > >
> >
> > > I tried manually from cli but get same result.
> >
> > >
> >
> > >
> >
> > > cd /usr/src/vim
> >
> > > hg pull
> >
> > > hg update
> >
> > > make distclean
> >
> > > ./configure --enable-rubyinterp=yes --enable-pythoninterp=yes --with-python-config-dir=/usr/lib/python2.6/config --with-features=huge --enable-gui=auto --with-compiledby=Bob_Hyam
> >
> > > ##cd src && make first
> >
> > > cd src
> >
> > > make
> >
> > > make install
> >
> > >
> >
> > >
> >
> > >
> >
> > > Any guidance would be greatly appreciated !
> >
> > >
> >
> > > Thanks, Bob H
> >
> >
> >
> > What happens when you try? What OS are you using?
>
> Sorry about that, Debian wheezy amd64. No errors seem to occur, it just remains the same version I started with. Does anyone know if this building creates a log file I could go through ? The screen updates pretty quickly so I can't say for sure there are no errors.
>
> Thanks for answering, Bob H
I run the latest 429 on Debian Wheezy as I write.
Maybe you have several versions on your system. Did you try:
which -a vim
Also, did you try to run your locally compiled file, that is in /usr/src/vim/src/ ?
What "hg summary" says?
--
--
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 Friday, August 29, 2014 6:12:19 PM UTC-7, Eric Christopherson wrote:
> > On Fri, Aug 29, 2014, Bob Hyam wrote:
> >
> > > I have been using this script to update Vim for a long time, but noe I cannot upgrade beyond patch 408.
> >
> > >
> >
> > > I tried manually from cli but get same result.
> >
> > >
> >
> > >
> >
> > > cd /usr/src/vim
> >
> > > hg pull
> >
> > > hg update
> >
> > > make distclean
> >
> > > ./configure --enable-rubyinterp=yes --enable-pythoninterp=yes --with-python-config-dir=/usr/lib/python2.6/config --with-features=huge --enable-gui=auto --with-compiledby=Bob_Hyam
> >
> > > ##cd src && make first
> >
> > > cd src
> >
> > > make
> >
> > > make install
> >
> > >
> >
> > >
> >
> > >
> >
> > > Any guidance would be greatly appreciated !
> >
> > >
> >
> > > Thanks, Bob H
> >
> >
> >
> > What happens when you try? What OS are you using?
>
> Sorry about that, Debian wheezy amd64. No errors seem to occur, it just remains the same version I started with. Does anyone know if this building creates a log file I could go through ? The screen updates pretty quickly so I can't say for sure there are no errors.
>
> Thanks for answering, Bob H
I run the latest 429 on Debian Wheezy as I write.
Maybe you have several versions on your system. Did you try:
which -a vim
Also, did you try to run your locally compiled file, that is in /usr/src/vim/src/ ?
What "hg summary" says?
--
--
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 29, 2014
Re: Unable to update Vim past ver 7.4.408
On Friday, August 29, 2014 6:12:19 PM UTC-7, Eric Christopherson wrote:
> On Fri, Aug 29, 2014, Bob Hyam wrote:
>
> > I have been using this script to update Vim for a long time, but noe I cannot upgrade beyond patch 408.
>
> >
>
> > I tried manually from cli but get same result.
>
> >
>
> >
>
> > cd /usr/src/vim
>
> > hg pull
>
> > hg update
>
> > make distclean
>
> > ./configure --enable-rubyinterp=yes --enable-pythoninterp=yes --with-python-config-dir=/usr/lib/python2.6/config --with-features=huge --enable-gui=auto --with-compiledby=Bob_Hyam
>
> > ##cd src && make first
>
> > cd src
>
> > make
>
> > make install
>
> >
>
> >
>
> >
>
> > Any guidance would be greatly appreciated !
>
> >
>
> > Thanks, Bob H
>
>
>
> What happens when you try? What OS are you using?
Sorry about that, Debian wheezy amd64. No errors seem to occur, it just remains the same version I started with. Does anyone know if this building creates a log file I could go through ? The screen updates pretty quickly so I can't say for sure there are no errors.
Thanks for answering, Bob H
--
--
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 29, 2014, Bob Hyam wrote:
>
> > I have been using this script to update Vim for a long time, but noe I cannot upgrade beyond patch 408.
>
> >
>
> > I tried manually from cli but get same result.
>
> >
>
> >
>
> > cd /usr/src/vim
>
> > hg pull
>
> > hg update
>
> > make distclean
>
> > ./configure --enable-rubyinterp=yes --enable-pythoninterp=yes --with-python-config-dir=/usr/lib/python2.6/config --with-features=huge --enable-gui=auto --with-compiledby=Bob_Hyam
>
> > ##cd src && make first
>
> > cd src
>
> > make
>
> > make install
>
> >
>
> >
>
> >
>
> > Any guidance would be greatly appreciated !
>
> >
>
> > Thanks, Bob H
>
>
>
> What happens when you try? What OS are you using?
Sorry about that, Debian wheezy amd64. No errors seem to occur, it just remains the same version I started with. Does anyone know if this building creates a log file I could go through ? The screen updates pretty quickly so I can't say for sure there are no errors.
Thanks for answering, Bob H
--
--
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: Unable to update Vim past ver 7.4.408
On Fri, Aug 29, 2014, Bob Hyam wrote:
> I have been using this script to update Vim for a long time, but noe I cannot upgrade beyond patch 408.
>
> I tried manually from cli but get same result.
>
>
> cd /usr/src/vim
> hg pull
> hg update
> make distclean
> ./configure --enable-rubyinterp=yes --enable-pythoninterp=yes --with-python-config-dir=/usr/lib/python2.6/config --with-features=huge --enable-gui=auto --with-compiledby=Bob_Hyam
> ##cd src && make first
> cd src
> make
> make install
>
>
>
> Any guidance would be greatly appreciated !
>
> Thanks, Bob H
What happens when you try? What OS are you using?
--
--
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 been using this script to update Vim for a long time, but noe I cannot upgrade beyond patch 408.
>
> I tried manually from cli but get same result.
>
>
> cd /usr/src/vim
> hg pull
> hg update
> make distclean
> ./configure --enable-rubyinterp=yes --enable-pythoninterp=yes --with-python-config-dir=/usr/lib/python2.6/config --with-features=huge --enable-gui=auto --with-compiledby=Bob_Hyam
> ##cd src && make first
> cd src
> make
> make install
>
>
>
> Any guidance would be greatly appreciated !
>
> Thanks, Bob H
What happens when you try? What OS are you using?
--
--
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-7.4.389 UI extremely sluggish with custom syntax highlighting plugins
Nope, hadn't tried, I was just watching for an update on this thread.
Thanks for taking care of it!
David
On Fri, Aug 29, 2014 at 2:40 PM, Christian Brabandt <cblists@256bit.org> wrote:
Hi David!
Can you still reproduce the issue with the latest patch level? It should
On Fr, 29 Aug 2014, David Barnett wrote:
> Any updates here, or is it still broken in HEAD? If it's still not fixed,
> it would be great to have the offending change reverted while waiting for
> the complete solution.
have been fixed with patch 7.4.405
Best,
Christian
--
Niemand lebt davon, daß er das Leben verneint.
-- André Malraux
--
--
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 a topic in the Google Groups "vim_use" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/vim_use/V6cRWX4c13E/unsubscribe.
To unsubscribe from this group and all its topics, send an email to vim_use+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
--
You received this message from the "vim_use" maillist.
Do not top-post! Type your reply below the text you are replying to.
For more information, visit http://www.vim.org/maillist.php
---
You received this message because you are subscribed to the Google Groups "vim_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Re: vim-7.4.389 UI extremely sluggish with custom syntax highlighting plugins
Hi David!
On Fr, 29 Aug 2014, David Barnett wrote:
> Any updates here, or is it still broken in HEAD? If it's still not fixed,
> it would be great to have the offending change reverted while waiting for
> the complete solution.
Can you still reproduce the issue with the latest patch level? It should
have been fixed with patch 7.4.405
Best,
Christian
--
Niemand lebt davon, daß er das Leben verneint.
-- André Malraux
--
--
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 Fr, 29 Aug 2014, David Barnett wrote:
> Any updates here, or is it still broken in HEAD? If it's still not fixed,
> it would be great to have the offending change reverted while waiting for
> the complete solution.
Can you still reproduce the issue with the latest patch level? It should
have been fixed with patch 7.4.405
Best,
Christian
--
Niemand lebt davon, daß er das Leben verneint.
-- André Malraux
--
--
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-7.4.389 UI extremely sluggish with custom syntax highlighting plugins
Any updates here, or is it still broken in HEAD? If it's still not fixed, it would be great to have the offending change reverted while waiting for the complete solution.
David
On Sat, Aug 16, 2014 at 7:23 AM, Bram Moolenaar <Bram@moolenaar.net> wrote:
Thanks. It's a bit strange to use mb_l here, it's hard to see it has the
Christian Brabandt wrote:
> On Do, 14 Aug 2014, Bram Moolenaar wrote:
>
> > Christian Brabandt wrote:
> >
> > > >> But anyway, this raises the question again, why matchaddpos()
> > > >> accepts a list of positions (but only 8 items), while all other
> > > >> functions usually only accept 1 position.
> > > >
> > > > It's used for the matchparen plugin. The idea is that it's useful for
> > > > other plugins as well.
> > >
> > > Yes, but for consistency with the other match() functions and the VimL
> > > API it might still be a good idea to only accept a single position per
> > > matchaddpos() call. It shouldn't be too hard, to adjust the matchparen
> > > plugin to call matchaddpos() twice, right?
> >
> > It would require another way to deal with IDs. Or allow for adding
> > another match with the same ID.
>
> Okay, here is another patch. This should fix all known problems, that
> have been mentioned so far. BTW, perhaps we could use h_east (sorry
> don't remember your name) test and include it as performance test?
correct value.
I found another solution: check if shl->lnum is equal to lnum. That's
how the match is disabled by next_search_hl().
--
Apparently, 1 in 5 people in the world are Chinese. And there are 5
people in my family, so it must be one of them. It's either my mum
or my dad. Or my older brother Colin. Or my younger brother
Ho-Cha-Chu. But I think it's Colin.
/// 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 a topic in the Google Groups "vim_use" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/vim_use/V6cRWX4c13E/unsubscribe.
To unsubscribe from this group and all its topics, send an email to vim_use+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
--
You received this message from the "vim_use" maillist.
Do not top-post! Type your reply below the text you are replying to.
For more information, visit http://www.vim.org/maillist.php
---
You received this message because you are subscribed to the Google Groups "vim_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Unable to update Vim past ver 7.4.408
I have been using this script to update Vim for a long time, but noe I cannot upgrade beyond patch 408.
I tried manually from cli but get same result.
cd /usr/src/vim
hg pull
hg update
make distclean
./configure --enable-rubyinterp=yes --enable-pythoninterp=yes --with-python-config-dir=/usr/lib/python2.6/config --with-features=huge --enable-gui=auto --with-compiledby=Bob_Hyam
##cd src && make first
cd src
make
make install
Any guidance would be greatly appreciated !
Thanks, Bob H
--
--
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 tried manually from cli but get same result.
cd /usr/src/vim
hg pull
hg update
make distclean
./configure --enable-rubyinterp=yes --enable-pythoninterp=yes --with-python-config-dir=/usr/lib/python2.6/config --with-features=huge --enable-gui=auto --with-compiledby=Bob_Hyam
##cd src && make first
cd src
make
make install
Any guidance would be greatly appreciated !
Thanks, Bob H
--
--
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 not exiting with closed stdin
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512
Hi
I wonder why vim doesn't just exit when it's stdin is closed.
The problem I have right now is that I have program which runs
.. sourcecode: python
os.system("${EDITOR} tempfile")
and I'm testing it with nosetests. So obviously I need to fake this
function but it starts the vim if the test for some reason runs the
real function.
So I thought I'd just close the stdin for the whole nosetets but then
the tests instead of just failing the test get stuck on running
dysfunctional vim.
So I wonder if there is an actuall reason for vim not exiting here or
if check_tty(parmp) could be fixed to exit(1) just like it does there
with netbeans.
- --
Jan Matějka | QA Engineer for Maintenance
SUSE LINUX s.r.o. | https://www.suse.com/
GPG: A33E F5BC A9F6 DAFD 2021 6FB6 3EBF D45B EEB6 CA8B
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.22 (GNU/Linux)
iQEcBAEBCgAGBQJUANteAAoJEIN+7RD5ejahq2AIANd7bcxO5yFZDCDKVkiVbGfy
ZLgbz0hxjp3mLOaG724kO3O02zblY28D19npcDjnjzSqHEwtGIcIWebIZHUwx0wV
p48ep+DGXxLwWxXUL0OpTD2LyoKAgDzFcYorqNfbZOEUufBxFCItPXGjdCML8Yf8
gvfeeGiBuSjzy53rHq+s5tOin3myvlNek3SrNzVP/2yHNbIYGqcQToETpx538fCa
9QPtD+KCJ6J8kqfLumkPuJN9E48EIFT+u1Uq49EoKx2t+Jbd2tjgirEQdKXzsUtq
r6bGWulKfIuAzdrcdFQrWL6bdHStDHHAHXgOtMX8W3f3r6PPZXbnTRqs7VCo8Ew=
=Kxu7
-----END PGP SIGNATURE-----
--
--
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.
Hash: SHA512
Hi
I wonder why vim doesn't just exit when it's stdin is closed.
The problem I have right now is that I have program which runs
.. sourcecode: python
os.system("${EDITOR} tempfile")
and I'm testing it with nosetests. So obviously I need to fake this
function but it starts the vim if the test for some reason runs the
real function.
So I thought I'd just close the stdin for the whole nosetets but then
the tests instead of just failing the test get stuck on running
dysfunctional vim.
So I wonder if there is an actuall reason for vim not exiting here or
if check_tty(parmp) could be fixed to exit(1) just like it does there
with netbeans.
- --
Jan Matějka | QA Engineer for Maintenance
SUSE LINUX s.r.o. | https://www.suse.com/
GPG: A33E F5BC A9F6 DAFD 2021 6FB6 3EBF D45B EEB6 CA8B
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.22 (GNU/Linux)
iQEcBAEBCgAGBQJUANteAAoJEIN+7RD5ejahq2AIANd7bcxO5yFZDCDKVkiVbGfy
ZLgbz0hxjp3mLOaG724kO3O02zblY28D19npcDjnjzSqHEwtGIcIWebIZHUwx0wV
p48ep+DGXxLwWxXUL0OpTD2LyoKAgDzFcYorqNfbZOEUufBxFCItPXGjdCML8Yf8
gvfeeGiBuSjzy53rHq+s5tOin3myvlNek3SrNzVP/2yHNbIYGqcQToETpx538fCa
9QPtD+KCJ6J8kqfLumkPuJN9E48EIFT+u1Uq49EoKx2t+Jbd2tjgirEQdKXzsUtq
r6bGWulKfIuAzdrcdFQrWL6bdHStDHHAHXgOtMX8W3f3r6PPZXbnTRqs7VCo8Ew=
=Kxu7
-----END PGP SIGNATURE-----
--
--
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.
Problems with vim-repress and markdown
Hi,
I am trying to use vim-repress. When I am writing posts with the type
HTML everything works fine. But when I use markdown and want to save a
blog post the following error pops up:
Error detected while processing :
Traceback (most recent call last):
File "<string>", line 1, in <module>
File "<string>", line 41, in __check
File "<string>", line 47, in <lambda>
vim.error: Vim(echoerr):something wrong: cannot marshal <class 'markdown2.UnicodeWithAttrs'> objects
I am on vim 7.4.410. Vim is compiled with python-support. Any ideas what
the problem could be?
Niels
--
--
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 trying to use vim-repress. When I am writing posts with the type
HTML everything works fine. But when I use markdown and want to save a
blog post the following error pops up:
Error detected while processing :
Traceback (most recent call last):
File "<string>", line 1, in <module>
File "<string>", line 41, in __check
File "<string>", line 47, in <lambda>
vim.error: Vim(echoerr):something wrong: cannot marshal <class 'markdown2.UnicodeWithAttrs'> objects
I am on vim 7.4.410. Vim is compiled with python-support. Any ideas what
the problem could be?
Niels
--
--
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: Downloading Plugins
On Thu, Aug 28, 2014 at 5:47 PM, Nathan Schwarz <nathan@notwhite.ro> wrote:
> Oy mate,
>
> those commands are always typed on the command line of the system.
> *nix-OSes like linux and osx typcially provide bash as the standard
> shell.
>
> If you use windows you'll have to google or hope for another good soul
> to answer.
>
> Also - take a look at vundle (if it works in windows). It's a pretty
> darn neat tool that automatically downloads and updates your plugins for
> you.
>
> -Nathan
>
> --
> /"\ ASCII Ribbon Campaign
> \ / - against HTML emails
> X - against proprietory attachments
> / \ http://en.wikipedia.org/wiki/ASCII_Ribbon_Campaign
>
> On Thu, Aug 28, 2014 at 10:05:50AM -0700, Robert Cressman wrote:
>> I have read several pages of articles/explanations/etc. on downloading plugins. Most involve Github.com. and provide the command to do so.
>>
>> As a novice, what I don't find, or understand, is where the "Git clone git://github.com/etc./etc." gets typed to accomplish this task. Is it in Vim, Git Bash, the command line of the system prompt??
>>
>> Any help would be appreciated. PLEASE remember, your explaining to a Vim novice who is struggling to comprehend all the "jargon" used by the experienced users!
>>
>> Bob
Bob,
My 2 cents:
I agree with tooth pik in that I think you might benefit, at least at
first, by keeping it simple and just learning how to use vim by itself
and learning how to configure it to your liking.
Then, once you've become decently familiar with vim, look into custom
plugins. I love and use many vim plugins; there are many out there
that I find indispensable.
To manage the plugins I personally use vundle and really like it. Once
you've got Git installed you just have to 'git clone' once to install
vundle and then vundle takes care of the rest for your. (It looks like
you also need Curl for searching with vundle.) There are very nice
instructions on vundle's github page, including setup on Windows.
Note: I am not necessarily promoting vundle above any of the other
popular plugin managers, it's just the one I use. Do your own research
before you settle on your plugin manager. I am sure they all have
their pros and cons.
And, note that whenever you see a command like 'git clone ...' you do
typically run that command from your system terminal/console. At least
on systems like linux/osx. I am not in the least bit familiar with the
windows os.
Good luck, and welcome to vim!
Ethan Alan
>> --
>> --
>> You received this message from the "vim_use" maillist.
>> Do not top-post! Type your reply below the text you are replying to.
>> For more information, visit http://www.vim.org/maillist.php
>>
>> ---
>> You received this message because you are subscribed to the Google Groups "vim_use" group.
>> To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
>> For more options, visit https://groups.google.com/d/optout.
--
--
You received this message from the "vim_use" maillist.
Do not top-post! Type your reply below the text you are replying to.
For more information, visit http://www.vim.org/maillist.php
---
You received this message because you are subscribed to the Google Groups "vim_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
> Oy mate,
>
> those commands are always typed on the command line of the system.
> *nix-OSes like linux and osx typcially provide bash as the standard
> shell.
>
> If you use windows you'll have to google or hope for another good soul
> to answer.
>
> Also - take a look at vundle (if it works in windows). It's a pretty
> darn neat tool that automatically downloads and updates your plugins for
> you.
>
> -Nathan
>
> --
> /"\ ASCII Ribbon Campaign
> \ / - against HTML emails
> X - against proprietory attachments
> / \ http://en.wikipedia.org/wiki/ASCII_Ribbon_Campaign
>
> On Thu, Aug 28, 2014 at 10:05:50AM -0700, Robert Cressman wrote:
>> I have read several pages of articles/explanations/etc. on downloading plugins. Most involve Github.com. and provide the command to do so.
>>
>> As a novice, what I don't find, or understand, is where the "Git clone git://github.com/etc./etc." gets typed to accomplish this task. Is it in Vim, Git Bash, the command line of the system prompt??
>>
>> Any help would be appreciated. PLEASE remember, your explaining to a Vim novice who is struggling to comprehend all the "jargon" used by the experienced users!
>>
>> Bob
Bob,
My 2 cents:
I agree with tooth pik in that I think you might benefit, at least at
first, by keeping it simple and just learning how to use vim by itself
and learning how to configure it to your liking.
Then, once you've become decently familiar with vim, look into custom
plugins. I love and use many vim plugins; there are many out there
that I find indispensable.
To manage the plugins I personally use vundle and really like it. Once
you've got Git installed you just have to 'git clone' once to install
vundle and then vundle takes care of the rest for your. (It looks like
you also need Curl for searching with vundle.) There are very nice
instructions on vundle's github page, including setup on Windows.
Note: I am not necessarily promoting vundle above any of the other
popular plugin managers, it's just the one I use. Do your own research
before you settle on your plugin manager. I am sure they all have
their pros and cons.
And, note that whenever you see a command like 'git clone ...' you do
typically run that command from your system terminal/console. At least
on systems like linux/osx. I am not in the least bit familiar with the
windows os.
Good luck, and welcome to vim!
Ethan Alan
>> --
>> --
>> You received this message from the "vim_use" maillist.
>> Do not top-post! Type your reply below the text you are replying to.
>> For more information, visit http://www.vim.org/maillist.php
>>
>> ---
>> You received this message because you are subscribed to the Google Groups "vim_use" group.
>> To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
>> For more options, visit https://groups.google.com/d/optout.
--
--
You received this message from the "vim_use" maillist.
Do not top-post! Type your reply below the text you are replying to.
For more information, visit http://www.vim.org/maillist.php
---
You received this message because you are subscribed to the Google Groups "vim_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Re: an update for the romanian spell checker
vineri, 29 august 2014, 18:32:10 UTC+3, Bram Moolenaar a scris:
> Vanilla Ice wrote:
>
>
>
> > miercuri, 13 august 2014, 15:51:25 UTC+3, Bram Moolenaar a scris:
>
> > > Vanilla Ice wrote:
>
> > >
>
> > >> <snip>
>
> > >
>
> > > Thanks for figuring this out. Can you please send me the .dic and .aff
>
> > >
>
> > > files you used to generate this .spl file? Or better: the URL of the
>
> > >
>
> > > files to be downloaded and a diff on top of that.
>
> > >
>
> >
>
> > By all means. I hope that there aren't other mistakes (I loaded a text-formatted translation of "Caves of Steel" by Asimov and it looked ok). In any case, it should be better than the old one, which is quite unusable for correct fonts/new grammar rules.
>
> >
>
> > 1. The URL is: http://sourceforge.net/projects/rospell/files/Romanian%20dictionaries/dict-3.3.10/ro_RO.3.3.10.zip
>
> >
>
> > and
>
> > 2. The diff file is attached to this post.
>
>
>
> I tried using that zip file with the diff, but I get lots of errors.
>
>
>
> The first one is easy to fix: Comment-out the KEY line.
>
>
>
> I get lots of "Trailing text" errors.
>
> I get a few "Duplicate character in MAP" errors.
>
>
>
> For the cp1250 encoded file I get lots of "Conversion failure" errors.
>
>
>
> Did you not see these errors or did you just ignore them?
>
The "trailing text" errors (a lot of them!) are caused by the fact that the authors of the spell files didn't put a comment start after the 5th element. From what i've seen in the vim spell.c source, the error messages are actually warnings, i.e. they don't affect the parsing.
I don't know what the effect of the "Duplicate character in MAP" error is, but i've seen no invalid spell behaviour with the new .spl.
Also, i just generated the ro.cp1250.spl file in gvim/Windows using
:set encoding=cp1250
:mkspell ro ro_RO in the right folder, and had no other errors than the above ones (no "Conversion failure" errors)
--
--
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.
> Vanilla Ice wrote:
>
>
>
> > miercuri, 13 august 2014, 15:51:25 UTC+3, Bram Moolenaar a scris:
>
> > > Vanilla Ice wrote:
>
> > >
>
> > >> <snip>
>
> > >
>
> > > Thanks for figuring this out. Can you please send me the .dic and .aff
>
> > >
>
> > > files you used to generate this .spl file? Or better: the URL of the
>
> > >
>
> > > files to be downloaded and a diff on top of that.
>
> > >
>
> >
>
> > By all means. I hope that there aren't other mistakes (I loaded a text-formatted translation of "Caves of Steel" by Asimov and it looked ok). In any case, it should be better than the old one, which is quite unusable for correct fonts/new grammar rules.
>
> >
>
> > 1. The URL is: http://sourceforge.net/projects/rospell/files/Romanian%20dictionaries/dict-3.3.10/ro_RO.3.3.10.zip
>
> >
>
> > and
>
> > 2. The diff file is attached to this post.
>
>
>
> I tried using that zip file with the diff, but I get lots of errors.
>
>
>
> The first one is easy to fix: Comment-out the KEY line.
>
>
>
> I get lots of "Trailing text" errors.
>
> I get a few "Duplicate character in MAP" errors.
>
>
>
> For the cp1250 encoded file I get lots of "Conversion failure" errors.
>
>
>
> Did you not see these errors or did you just ignore them?
>
The "trailing text" errors (a lot of them!) are caused by the fact that the authors of the spell files didn't put a comment start after the 5th element. From what i've seen in the vim spell.c source, the error messages are actually warnings, i.e. they don't affect the parsing.
I don't know what the effect of the "Duplicate character in MAP" error is, but i've seen no invalid spell behaviour with the new .spl.
Also, i just generated the ro.cp1250.spl file in gvim/Windows using
:set encoding=cp1250
:mkspell ro ro_RO in the right folder, and had no other errors than the above ones (no "Conversion failure" errors)
--
--
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: an update for the romanian spell checker
Vanilla Ice wrote:
> miercuri, 13 august 2014, 15:51:25 UTC+3, Bram Moolenaar a scris:
> > Vanilla Ice wrote:
> >
> >> <snip>
> >
> > Thanks for figuring this out. Can you please send me the .dic and .aff
> >
> > files you used to generate this .spl file? Or better: the URL of the
> >
> > files to be downloaded and a diff on top of that.
> >
>
> By all means. I hope that there aren't other mistakes (I loaded a text-formatted translation of "Caves of Steel" by Asimov and it looked ok). In any case, it should be better than the old one, which is quite unusable for correct fonts/new grammar rules.
>
> 1. The URL is: http://sourceforge.net/projects/rospell/files/Romanian%20dictionaries/dict-3.3.10/ro_RO.3.3.10.zip
>
> and
> 2. The diff file is attached to this post.
I tried using that zip file with the diff, but I get lots of errors.
The first one is easy to fix: Comment-out the KEY line.
I get lots of "Trailing text" errors.
I get a few "Duplicate character in MAP" errors.
For the cp1250 encoded file I get lots of "Conversion failure" errors.
Did you not see these errors or did you just ignore them?
--
From "know your smileys":
:-)-O Smiling doctor with stethoscope
/// 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.
> miercuri, 13 august 2014, 15:51:25 UTC+3, Bram Moolenaar a scris:
> > Vanilla Ice wrote:
> >
> >> <snip>
> >
> > Thanks for figuring this out. Can you please send me the .dic and .aff
> >
> > files you used to generate this .spl file? Or better: the URL of the
> >
> > files to be downloaded and a diff on top of that.
> >
>
> By all means. I hope that there aren't other mistakes (I loaded a text-formatted translation of "Caves of Steel" by Asimov and it looked ok). In any case, it should be better than the old one, which is quite unusable for correct fonts/new grammar rules.
>
> 1. The URL is: http://sourceforge.net/projects/rospell/files/Romanian%20dictionaries/dict-3.3.10/ro_RO.3.3.10.zip
>
> and
> 2. The diff file is attached to this post.
I tried using that zip file with the diff, but I get lots of errors.
The first one is easy to fix: Comment-out the KEY line.
I get lots of "Trailing text" errors.
I get a few "Duplicate character in MAP" errors.
For the cp1250 encoded file I get lots of "Conversion failure" errors.
Did you not see these errors or did you just ignore them?
--
From "know your smileys":
:-)-O Smiling doctor with stethoscope
/// Bram Moolenaar -- Bram@Moolenaar.net -- http://www.Moolenaar.net \\\
/// sponsor Vim, vote for features -- http://www.Vim.org/sponsor/ \\\
\\\ an exciting new programming language -- http://www.Zimbu.org ///
\\\ help me help AIDS victims -- http://ICCF-Holland.org ///
--
--
You received this message from the "vim_use" maillist.
Do not top-post! Type your reply below the text you are replying to.
For more information, visit http://www.vim.org/maillist.php
---
You received this message because you are subscribed to the Google Groups "vim_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Re: Vim for Windows (Updated to 7.4.417)
Thanks for the tip. I will consider that for the next release.
--
--
You received this message from the "vim_use" maillist.
Do not top-post! Type your reply below the text you are replying to.
For more information, visit http://www.vim.org/maillist.php
---
You received this message because you are subscribed to the Google Groups "vim_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
--
--
You received this message from the "vim_use" maillist.
Do not top-post! Type your reply below the text you are replying to.
For more information, visit http://www.vim.org/maillist.php
---
You received this message because you are subscribed to the Google Groups "vim_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Thursday, August 28, 2014
Re: Downloading Plugins
On 17:11 Thu 28 Aug , tooth pik wrote:
> On Thu, Aug 28, 2014 at 10:05:50AM -0700, Robert Cressman wrote:
> > I have read several pages of articles/explanations/etc. on downloading
> > plugins. Most involve Github.com. and provide the command to do so.
>
> > As a novice, what I don't find, or understand, is where the "Git clone
> > git://github.com/etc./etc." gets typed to accomplish this task. Is it
> > in Vim, Git Bash, the command line of the system prompt??
>
> > Any help would be appreciated. PLEASE remember, your explaining to a
> > Vim novice who is struggling to comprehend all the "jargon" used by
> > the experienced users!
>
> To a novice I would recommend they stay way from plugins entirely until
> they have a firm grasp of how vim works and are comfortable with it --
> plugins are a very common cause of unexpected and undocumented behavior,
> which gets harder to debug the more of them you have.
>
> Then, if there is some plugin you feel compelled to experiment with even
> after having been warned, the best place for novices to get plugins is
> from the vim site: http://www.vim.org, where, for the vast majority of
> plugins (where they are referred to as "scripts") installation is a
> simple matter of dropping the item on your ~/.vim path and unpacking it.
>
> If you still insist on cloning someone's git workspace, the git commands
> are for the system prompt, but you have been warned.
>
> --
> _|_ _ __|_|_ ._ o|
> |_(_)(_)|_| ||_)||<
The ~/.vim directory has a special structure that is good to know: for
example filetype scripts are should be placed under ~/.vim/ftplugin,
colorscheme scripts under ~/.vim/colors, plugins ~/.vim/plugin. You can
read about them all from :help 'rtp'.
A plugin distributed on vim.org/github/... might (and often has) files
which land in all different parts of ~/.vim. For example documentation
file should be put under ~/.vim/doc/, ... . Often it is enough to
unpack tha gzip/tar/... in your ~/.vim directory; but it is good to
check what is the directory structure of the downloaded archive.
As for using git and grabbing plugins directly from github, this is
quite ease, but requires from you first to install/understand pathogen
plugin (and to know what :help 'rtp' is about) or vim addon manager
(though setting it up might be more difficult for beginners).
Remember that :help and :helpgrep are your first friends - after all
everything is documented, well almost (for example that this ":::::ls"
will work I think it isn't, though I might be wrong).
Best regards,
Marcin
> On Thu, Aug 28, 2014 at 10:05:50AM -0700, Robert Cressman wrote:
> > I have read several pages of articles/explanations/etc. on downloading
> > plugins. Most involve Github.com. and provide the command to do so.
>
> > As a novice, what I don't find, or understand, is where the "Git clone
> > git://github.com/etc./etc." gets typed to accomplish this task. Is it
> > in Vim, Git Bash, the command line of the system prompt??
>
> > Any help would be appreciated. PLEASE remember, your explaining to a
> > Vim novice who is struggling to comprehend all the "jargon" used by
> > the experienced users!
>
> To a novice I would recommend they stay way from plugins entirely until
> they have a firm grasp of how vim works and are comfortable with it --
> plugins are a very common cause of unexpected and undocumented behavior,
> which gets harder to debug the more of them you have.
>
> Then, if there is some plugin you feel compelled to experiment with even
> after having been warned, the best place for novices to get plugins is
> from the vim site: http://www.vim.org, where, for the vast majority of
> plugins (where they are referred to as "scripts") installation is a
> simple matter of dropping the item on your ~/.vim path and unpacking it.
>
> If you still insist on cloning someone's git workspace, the git commands
> are for the system prompt, but you have been warned.
>
> --
> _|_ _ __|_|_ ._ o|
> |_(_)(_)|_| ||_)||<
The ~/.vim directory has a special structure that is good to know: for
example filetype scripts are should be placed under ~/.vim/ftplugin,
colorscheme scripts under ~/.vim/colors, plugins ~/.vim/plugin. You can
read about them all from :help 'rtp'.
A plugin distributed on vim.org/github/... might (and often has) files
which land in all different parts of ~/.vim. For example documentation
file should be put under ~/.vim/doc/, ... . Often it is enough to
unpack tha gzip/tar/... in your ~/.vim directory; but it is good to
check what is the directory structure of the downloaded archive.
As for using git and grabbing plugins directly from github, this is
quite ease, but requires from you first to install/understand pathogen
plugin (and to know what :help 'rtp' is about) or vim addon manager
(though setting it up might be more difficult for beginners).
Remember that :help and :helpgrep are your first friends - after all
everything is documented, well almost (for example that this ":::::ls"
will work I think it isn't, though I might be wrong).
Best regards,
Marcin
Re: Downloading Plugins
On Thu, Aug 28, 2014 at 10:05:50AM -0700, Robert Cressman wrote:
> I have read several pages of articles/explanations/etc. on downloading
> plugins. Most involve Github.com. and provide the command to do so.
> As a novice, what I don't find, or understand, is where the "Git clone
> git://github.com/etc./etc." gets typed to accomplish this task. Is it
> in Vim, Git Bash, the command line of the system prompt??
> Any help would be appreciated. PLEASE remember, your explaining to a
> Vim novice who is struggling to comprehend all the "jargon" used by
> the experienced users!
To a novice I would recommend they stay way from plugins entirely until
they have a firm grasp of how vim works and are comfortable with it --
plugins are a very common cause of unexpected and undocumented behavior,
which gets harder to debug the more of them you have.
Then, if there is some plugin you feel compelled to experiment with even
after having been warned, the best place for novices to get plugins is
from the vim site: http://www.vim.org, where, for the vast majority of
plugins (where they are referred to as "scripts") installation is a
simple matter of dropping the item on your ~/.vim path and unpacking it.
If you still insist on cloning someone's git workspace, the git commands
are for the system prompt, but you have been warned.
--
_|_ _ __|_|_ ._ o|
|_(_)(_)|_| ||_)||<
|
--
--
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 read several pages of articles/explanations/etc. on downloading
> plugins. Most involve Github.com. and provide the command to do so.
> As a novice, what I don't find, or understand, is where the "Git clone
> git://github.com/etc./etc." gets typed to accomplish this task. Is it
> in Vim, Git Bash, the command line of the system prompt??
> Any help would be appreciated. PLEASE remember, your explaining to a
> Vim novice who is struggling to comprehend all the "jargon" used by
> the experienced users!
To a novice I would recommend they stay way from plugins entirely until
they have a firm grasp of how vim works and are comfortable with it --
plugins are a very common cause of unexpected and undocumented behavior,
which gets harder to debug the more of them you have.
Then, if there is some plugin you feel compelled to experiment with even
after having been warned, the best place for novices to get plugins is
from the vim site: http://www.vim.org, where, for the vast majority of
plugins (where they are referred to as "scripts") installation is a
simple matter of dropping the item on your ~/.vim path and unpacking it.
If you still insist on cloning someone's git workspace, the git commands
are for the system prompt, but you have been warned.
--
_|_ _ __|_|_ ._ o|
|_(_)(_)|_| ||_)||<
|
--
--
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: Downloading Plugins
Oy mate,
those commands are always typed on the command line of the system.
*nix-OSes like linux and osx typcially provide bash as the standard
shell.
If you use windows you'll have to google or hope for another good soul
to answer.
Also - take a look at vundle (if it works in windows). It's a pretty
darn neat tool that automatically downloads and updates your plugins for
you.
-Nathan
--
/"\ ASCII Ribbon Campaign
\ / - against HTML emails
X - against proprietory attachments
/ \ http://en.wikipedia.org/wiki/ASCII_Ribbon_Campaign
On Thu, Aug 28, 2014 at 10:05:50AM -0700, Robert Cressman wrote:
> I have read several pages of articles/explanations/etc. on downloading plugins. Most involve Github.com. and provide the command to do so.
>
> As a novice, what I don't find, or understand, is where the "Git clone git://github.com/etc./etc." gets typed to accomplish this task. Is it in Vim, Git Bash, the command line of the system prompt??
>
> Any help would be appreciated. PLEASE remember, your explaining to a Vim novice who is struggling to comprehend all the "jargon" used by the experienced users!
>
> Bob
>
> --
> --
> 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.
those commands are always typed on the command line of the system.
*nix-OSes like linux and osx typcially provide bash as the standard
shell.
If you use windows you'll have to google or hope for another good soul
to answer.
Also - take a look at vundle (if it works in windows). It's a pretty
darn neat tool that automatically downloads and updates your plugins for
you.
-Nathan
--
/"\ ASCII Ribbon Campaign
\ / - against HTML emails
X - against proprietory attachments
/ \ http://en.wikipedia.org/wiki/ASCII_Ribbon_Campaign
On Thu, Aug 28, 2014 at 10:05:50AM -0700, Robert Cressman wrote:
> I have read several pages of articles/explanations/etc. on downloading plugins. Most involve Github.com. and provide the command to do so.
>
> As a novice, what I don't find, or understand, is where the "Git clone git://github.com/etc./etc." gets typed to accomplish this task. Is it in Vim, Git Bash, the command line of the system prompt??
>
> Any help would be appreciated. PLEASE remember, your explaining to a Vim novice who is struggling to comprehend all the "jargon" used by the experienced users!
>
> Bob
>
> --
> --
> 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.
Downloading Plugins
I have read several pages of articles/explanations/etc. on downloading plugins. Most involve Github.com. and provide the command to do so.
As a novice, what I don't find, or understand, is where the "Git clone git://github.com/etc./etc." gets typed to accomplish this task. Is it in Vim, Git Bash, the command line of the system prompt??
Any help would be appreciated. PLEASE remember, your explaining to a Vim novice who is struggling to comprehend all the "jargon" used by the experienced users!
Bob
--
--
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 a novice, what I don't find, or understand, is where the "Git clone git://github.com/etc./etc." gets typed to accomplish this task. Is it in Vim, Git Bash, the command line of the system prompt??
Any help would be appreciated. PLEASE remember, your explaining to a Vim novice who is struggling to comprehend all the "jargon" used by the experienced users!
Bob
--
--
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 27, 2014
runtimepath/syntax dir question
hi,
i'm trying to build a portable static vim. compiling statically works
alright, now i'm looking for a portable place to put the runtime files
(those installed by "make install" into $PREFIX/share/). when i put
$PREFIX/share/vim/vim74/ into $HOME/.vim/ and move $PREFIX/share/ out of
the way (won't be there on other computers) the following happens:
.) vim correctly finds things in $HOME/.vim/plugin/ (according to strace)
.) when i want to use syntax highlighting vim complains about not
finding $PREFIX/share/vim/syntax/syntax.vim. that file is not there even
when i restore $PREFIX/share/! when i restore $PREFIX/share (containing
"vim/vim74") vim uses $PREFIX/share/vim/vim74/syntax/syntax.vim without
looking for $PREFIX/share/vim/syntax/syntax.vim. my expected behaviour
was vim using $HOME/.vim/syntax/
configure command was:
./configure --prefix=$PREFIX --disable-nls --without-x --enable-gui=no
--disable-gpm --with-features=big
system is ubuntu 14.04
no $HOME/.vimrc or system config/runtime files involved
thx for help
matthias
--
--
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 trying to build a portable static vim. compiling statically works
alright, now i'm looking for a portable place to put the runtime files
(those installed by "make install" into $PREFIX/share/). when i put
$PREFIX/share/vim/vim74/ into $HOME/.vim/ and move $PREFIX/share/ out of
the way (won't be there on other computers) the following happens:
.) vim correctly finds things in $HOME/.vim/plugin/ (according to strace)
.) when i want to use syntax highlighting vim complains about not
finding $PREFIX/share/vim/syntax/syntax.vim. that file is not there even
when i restore $PREFIX/share/! when i restore $PREFIX/share (containing
"vim/vim74") vim uses $PREFIX/share/vim/vim74/syntax/syntax.vim without
looking for $PREFIX/share/vim/syntax/syntax.vim. my expected behaviour
was vim using $HOME/.vim/syntax/
configure command was:
./configure --prefix=$PREFIX --disable-nls --without-x --enable-gui=no
--disable-gpm --with-features=big
system is ubuntu 14.04
no $HOME/.vimrc or system config/runtime files involved
thx for help
matthias
--
--
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 for Windows (Updated to 7.4.417)
miercuri, 27 august 2014, 20:52:50 UTC+3, Alexander Shukaev a scris:
> Hey guys,
>
> Vim for Windows [https://bitbucket.org/Haroogan/vim-for-windows] has been updated to 7.4.417.
>
> Supporting both x86 (32-bit) and x64 (64-bit) architectures. Providing "huge" feature set and scripting interfaces for Python 2.7.X, Python 3.4.X, Ruby 2.0.0, Lua 5.2.X, Perl 5.18.X. Have fun!
>
> Kind regards,
> Alexander Shukaev
Thank you!
If you'd want, you can also add 'DIRECTX=yes' to the build flags - it provides better font handling support (e.g. i can see various Unicode fonts *only* with this feature enabled, e.g. something like: set renderoptions = type:directx,gamma:1.0,contrast:0.2,geom:1,renmode:5,taamode:1)
--
--
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.
> Hey guys,
>
> Vim for Windows [https://bitbucket.org/Haroogan/vim-for-windows] has been updated to 7.4.417.
>
> Supporting both x86 (32-bit) and x64 (64-bit) architectures. Providing "huge" feature set and scripting interfaces for Python 2.7.X, Python 3.4.X, Ruby 2.0.0, Lua 5.2.X, Perl 5.18.X. Have fun!
>
> Kind regards,
> Alexander Shukaev
Thank you!
If you'd want, you can also add 'DIRECTX=yes' to the build flags - it provides better font handling support (e.g. i can see various Unicode fonts *only* with this feature enabled, e.g. something like: set renderoptions = type:directx,gamma:1.0,contrast:0.2,geom:1,renmode:5,taamode:1)
--
--
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 for Windows (Updated to 7.4.417)
Hey guys,
Vim for Windows [https://bitbucket.org/Haroogan/vim-for-windows] has been updated to 7.4.417.
Supporting both x86 (32-bit) and x64 (64-bit) architectures. Providing "huge" feature set and scripting interfaces for Python 2.7.X, Python 3.4.X, Ruby 2.0.0, Lua 5.2.X, Perl 5.18.X. Have fun!
Kind regards,
Alexander Shukaev
--
--
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 for Windows [https://bitbucket.org/Haroogan/vim-for-windows] has been updated to 7.4.417.
Supporting both x86 (32-bit) and x64 (64-bit) architectures. Providing "huge" feature set and scripting interfaces for Python 2.7.X, Python 3.4.X, Ruby 2.0.0, Lua 5.2.X, Perl 5.18.X. Have fun!
Kind regards,
Alexander Shukaev
--
--
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 24, 2014
Re: vim: leaders vs. character searches
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.12 (GNU/Linux)
iQEcBAEBCgAGBQJT+dspAAoJEERGtGilKM7wucwH/07k9HZtp3C5MPDN766gO+BP
2mQew8oaWLLH6IjHf/QK7ysT6O2yfwrzAooLkbe+6A4Sehvss95JkyHq5OyKKQ4S
DfrsIGtlcRFC8F9czRa98o6bZyNt+AbKiujIyozy0nqoMq06vn/S+UYYZeLd76+d
4fQSkjUTZu6MTjaEl06BDsZTC0XiZBXX/5zV6Pt4+wAaTQlriG+fGBA7MzuH4HOI
/PXIrESAQGtnohBNZw3dzDew2YeGP2awW7Wz9nAf0eHpaj0fJGZTq5NF83FUwfFE
aCk1yGYWXrXuV2Hg5veoI77JHmYDmduQLnHG57c9flNC9/f19rlyRx3I7WPlLAU=
=a4a3
-----END PGP SIGNATURE-----
On 2014-08-24 13:16, Óscar Pereira wrote:
> let g:mapleader = ","
> let g:maplocalleader = ";"
> nnoremap - ;
> nnoremap _ ,
>
> Now repeating a previous character search is done with a dash, and
> repeating a previous character search in reverse is done with an
> underscore. This works really nicely, and I see no drawbacks --
> other than the fact that it changes a vim default command...
>
> Does anyone see any problems with this solution, or has any other
> better alternatives?
I tend to not remap built-ins unless they have duplicates, so I
leave ,/; as their default (I use them ALL the time) and leave "\" as
the default leader. I've never had to use "g:maplocalleader", but
I'd consider "+" or Enter because they both perform the same
action, so remapping one of them doesn't interfere with using the
other. Alternatively, I'd consider the "_" which I don't use because
it's functionally almost identical to "+"/Enter except the count is
reduced by one (I find that pretty useless).
Some folks also remap "Q" because going into Ex mode doesn't really
net you much unless you know ahead of time that you're going to enter
lots of Ex commands consecutively.
I find that, if I'm reaching to remap something and it clashes with
an existing Vim key that I didn't know about, it's a good opportunity
to read up on that conflicting key and see if I can integrate it into
my day-to-day vimming.
-tim
Version: GnuPG v1.4.12 (GNU/Linux)
iQEcBAEBCgAGBQJT+dspAAoJEERGtGilKM7wucwH/07k9HZtp3C5MPDN766gO+BP
2mQew8oaWLLH6IjHf/QK7ysT6O2yfwrzAooLkbe+6A4Sehvss95JkyHq5OyKKQ4S
DfrsIGtlcRFC8F9czRa98o6bZyNt+AbKiujIyozy0nqoMq06vn/S+UYYZeLd76+d
4fQSkjUTZu6MTjaEl06BDsZTC0XiZBXX/5zV6Pt4+wAaTQlriG+fGBA7MzuH4HOI
/PXIrESAQGtnohBNZw3dzDew2YeGP2awW7Wz9nAf0eHpaj0fJGZTq5NF83FUwfFE
aCk1yGYWXrXuV2Hg5veoI77JHmYDmduQLnHG57c9flNC9/f19rlyRx3I7WPlLAU=
=a4a3
-----END PGP SIGNATURE-----
On 2014-08-24 13:16, Óscar Pereira wrote:
> let g:mapleader = ","
> let g:maplocalleader = ";"
> nnoremap - ;
> nnoremap _ ,
>
> Now repeating a previous character search is done with a dash, and
> repeating a previous character search in reverse is done with an
> underscore. This works really nicely, and I see no drawbacks --
> other than the fact that it changes a vim default command...
>
> Does anyone see any problems with this solution, or has any other
> better alternatives?
I tend to not remap built-ins unless they have duplicates, so I
leave ,/; as their default (I use them ALL the time) and leave "\" as
the default leader. I've never had to use "g:maplocalleader", but
I'd consider "+" or Enter because they both perform the same
action, so remapping one of them doesn't interfere with using the
other. Alternatively, I'd consider the "_" which I don't use because
it's functionally almost identical to "+"/Enter except the count is
reduced by one (I find that pretty useless).
Some folks also remap "Q" because going into Ex mode doesn't really
net you much unless you know ahead of time that you're going to enter
lots of Ex commands consecutively.
I find that, if I'm reaching to remap something and it clashes with
an existing Vim key that I didn't know about, it's a good opportunity
to read up on that conflicting key and see if I can integrate it into
my day-to-day vimming.
-tim
vim: leaders vs. character searches
Hello all,
So, these were my leader mappings:
let g:mapleader = ","
let g:maplocalleader = ";"
Which work very well, except for the fact that (repeating) character
searches (';' or ',') get slightly slower. Slightly, but noticeably
and very annoyingly slower. I tried other combinations of
leader/localleader, but they all sucked. So finally I thought this
solution up:
let g:mapleader = ","
let g:maplocalleader = ";"
nnoremap - ;
nnoremap _ ,
Now repeating a previous character search is done with a dash, and
repeating a previous character search in reverse is done with an
underscore. This works really nicely, and I see no drawbacks --
other than the fact that it changes a vim default command...
Does anyone see any problems with this solution, or has any other
better alternatives?
---Óscar Pereira
So, these were my leader mappings:
let g:mapleader = ","
let g:maplocalleader = ";"
Which work very well, except for the fact that (repeating) character
searches (';' or ',') get slightly slower. Slightly, but noticeably
and very annoyingly slower. I tried other combinations of
leader/localleader, but they all sucked. So finally I thought this
solution up:
let g:mapleader = ","
let g:maplocalleader = ";"
nnoremap - ;
nnoremap _ ,
Now repeating a previous character search is done with a dash, and
repeating a previous character search in reverse is done with an
underscore. This works really nicely, and I see no drawbacks --
other than the fact that it changes a vim default command...
Does anyone see any problems with this solution, or has any other
better alternatives?
---Óscar Pereira
Re: Matchit plugin doesn't match square brackets
miercuri, 20 august 2014, 21:39:39 UTC+3, Matteo Riva a scris:
> When using the matchit plugin I can't get the matching to work on
>
> square brackets, unless I use the :MatchDebug command, then they work
>
> fine.
>
> Everything else is working as far as I can tell, and b:match_words includes [:]
>
>
>
> Tested both on vim 7.2 and 7.3 (same config and plugins, two different
>
> debian systems).
>
>
>
> What could be causing this?
BTW, are you by any chance editing javascript/html? If so, i just happen to stumble upon this: http://vim.wikia.com/wiki/Script:39 (see the 2nd "bug"). The solution described would be in this case to add (again):
let b:match_words .= ',{:},(:),[:]'
to an 'after/ftplugin/html.vim' file.
--
--
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.
> When using the matchit plugin I can't get the matching to work on
>
> square brackets, unless I use the :MatchDebug command, then they work
>
> fine.
>
> Everything else is working as far as I can tell, and b:match_words includes [:]
>
>
>
> Tested both on vim 7.2 and 7.3 (same config and plugins, two different
>
> debian systems).
>
>
>
> What could be causing this?
BTW, are you by any chance editing javascript/html? If so, i just happen to stumble upon this: http://vim.wikia.com/wiki/Script:39 (see the 2nd "bug"). The solution described would be in this case to add (again):
let b:match_words .= ',{:},(:),[:]'
to an 'after/ftplugin/html.vim' file.
--
--
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 22, 2014
Re: Conqueterm blanks some lines
On Fri, Aug 22, 2014 at 12:45 PM, Tim Chase <vim@tim.thechases.com> wrote:
> On 2014-08-22 10:42, John Biederstedt wrote:
>> Whenever I use conqueterm (on linux) to ssh to a nexus switch, and
>> backspace causes the line to go blank. Anyone else experience this?
>
> I think you may have sent this to the wrong mailing list.
Nope; ConqueTerm is a Vim plugin :)
>
> That said, I'd check what your $TERM settings are on both ends and
> make sure they aren't getting manually set to something wrong.
>
> -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.
> On 2014-08-22 10:42, John Biederstedt wrote:
>> Whenever I use conqueterm (on linux) to ssh to a nexus switch, and
>> backspace causes the line to go blank. Anyone else experience this?
>
> I think you may have sent this to the wrong mailing list.
Nope; ConqueTerm is a Vim plugin :)
>
> That said, I'd check what your $TERM settings are on both ends and
> make sure they aren't getting manually set to something wrong.
>
> -tim
--
--
You received this message from the "vim_use" maillist.
Do not top-post! Type your reply below the text you are replying to.
For more information, visit http://www.vim.org/maillist.php
---
You received this message because you are subscribed to the Google Groups "vim_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Re: Conqueterm blanks some lines
On 2014-08-22 10:42, John Biederstedt wrote:
> Whenever I use conqueterm (on linux) to ssh to a nexus switch, and
> backspace causes the line to go blank. Anyone else experience this?
I think you may have sent this to the wrong mailing list.
That said, I'd check what your $TERM settings are on both ends and
make sure they aren't getting manually set to something wrong.
-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.
> Whenever I use conqueterm (on linux) to ssh to a nexus switch, and
> backspace causes the line to go blank. Anyone else experience this?
I think you may have sent this to the wrong mailing list.
That said, I'd check what your $TERM settings are on both ends and
make sure they aren't getting manually set to something wrong.
-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.
Conqueterm blanks some lines
Whenever I use conqueterm (on linux) to ssh to a nexus switch, and backspace causes the line to go blank. Anyone else experience this?
thanks
john biederstedt
--
--
You received this message from the "vim_use" maillist.
Do not top-post! Type your reply below the text you are replying to.
For more information, visit http://www.vim.org/maillist.php
---
You received this message because you are subscribed to the Google Groups "vim_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
thanks
john biederstedt
--
--
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 21, 2014
Re: Matchit plugin doesn't match square brackets
joi, 21 august 2014, 13:10:03 UTC+3, Christian Brabandt a scris:
> Am 2014-08-21 12:01, schrieb 'Vanilla Ice' via vim_use:
>
> > Strange, as % matches [,] even when i start with 'vim -u NONE' (7.4
>
> > version here).
>
>
>
> That's because the [] pair is in set matchpairs setting by default (:h
>
> 'mps')
>
>
> > It doesn't match in a simple situation though: when you
>
> > have unbalanced [s in your file. E.g. "[ ] ]" and cursor on last
>
> > bracket.
>
>
>
> Well, where should it go?
>
>
>
> Best,
>
> Christian
Yes - i didn't mean it doesn't work as it should - on the contrary :) Just trying to clarify for the OP that 'default' Vim works with [,].
Regards
--
--
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 2014-08-21 12:01, schrieb 'Vanilla Ice' via vim_use:
>
> > Strange, as % matches [,] even when i start with 'vim -u NONE' (7.4
>
> > version here).
>
>
>
> That's because the [] pair is in set matchpairs setting by default (:h
>
> 'mps')
>
>
> > It doesn't match in a simple situation though: when you
>
> > have unbalanced [s in your file. E.g. "[ ] ]" and cursor on last
>
> > bracket.
>
>
>
> Well, where should it go?
>
>
>
> Best,
>
> Christian
Yes - i didn't mean it doesn't work as it should - on the contrary :) Just trying to clarify for the OP that 'default' Vim works with [,].
Regards
--
--
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: Matchit plugin doesn't match square brackets
Am 2014-08-21 12:01, schrieb 'Vanilla Ice' via vim_use:
> Strange, as % matches [,] even when i start with 'vim -u NONE' (7.4
> version here).
That's because the [] pair is in set matchpairs setting by default (:h
'mps')
> It doesn't match in a simple situation though: when you
> have unbalanced [s in your file. E.g. "[ ] ]" and cursor on last
> bracket.
Well, where should it go?
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.
> Strange, as % matches [,] even when i start with 'vim -u NONE' (7.4
> version here).
That's because the [] pair is in set matchpairs setting by default (:h
'mps')
> It doesn't match in a simple situation though: when you
> have unbalanced [s in your file. E.g. "[ ] ]" and cursor on last
> bracket.
Well, where should it go?
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: Matchit plugin doesn't match square brackets
Strange, as % matches [,] even when i start with 'vim -u NONE' (7.4 version here). It doesn't match in a simple situation though: when you have unbalanced [s in your file. E.g. "[ ] ]" and cursor on last bracket.
--
--
You received this message from the "vim_use" maillist.
Do not top-post! Type your reply below the text you are replying to.
For more information, visit http://www.vim.org/maillist.php
---
You received this message because you are subscribed to the Google Groups "vim_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
--
--
You received this message from the "vim_use" maillist.
Do not top-post! Type your reply below the text you are replying to.
For more information, visit http://www.vim.org/maillist.php
---
You received this message because you are subscribed to the Google Groups "vim_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Re: Matchit plugin doesn't match square brackets
Am 2014-08-20 15:09, schrieb Matteo Riva:
> When using the matchit plugin I can't get the matching to work on
> square brackets, unless I use the :MatchDebug command, then they work
> fine.
> Everything else is working as far as I can tell, and b:match_words
> includes [:]
>
> Tested both on vim 7.2 and 7.3 (same config and plugins, two different
> debian systems).
>
> What could be causing this?
My guess is, the plugin is using the values of b:match_words as a
pattern,
and '[' and ']' needs to be escaped to be a valid pattern.
Therefore try either to use
:let b:match_words='\[:\]'
or as a quick look into matchit.vim reveals,
add '[:]' to the 'matchpairs' option which will be handled by the
matchit
plugin automatically (and it escapes those values correctly).
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.
> When using the matchit plugin I can't get the matching to work on
> square brackets, unless I use the :MatchDebug command, then they work
> fine.
> Everything else is working as far as I can tell, and b:match_words
> includes [:]
>
> Tested both on vim 7.2 and 7.3 (same config and plugins, two different
> debian systems).
>
> What could be causing this?
My guess is, the plugin is using the values of b:match_words as a
pattern,
and '[' and ']' needs to be escaped to be a valid pattern.
Therefore try either to use
:let b:match_words='\[:\]'
or as a quick look into matchit.vim reveals,
add '[:]' to the 'matchpairs' option which will be handled by the
matchit
plugin automatically (and it escapes those values correctly).
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.
Wednesday, August 20, 2014
Looking forward to hearing from you - my vim plugin - Session-Viminfo-Management
Hey Guys,
I made a vim plugin named Session-Viminfo-Management(http://www.vim.org/scripts/script.php?script_id=5005), built upon Vim's built-in :mksession and :wviminfo commands.
It provide great convinience to save and load your Vim session and viminfo files automatically.
Will anybody to have a try?
I will be glad to read your feedback if any :)
BTW, actually, I didn't want to reinvent wheels. So I've had done some researches on vim.org before real development:
Searched on vim.org by keywords "workspace", seems no relative plugin found.
Searched on vim.org by keywords "viminfo", seems no relative plugin found.
Searched on vim.org by keywords "session", found some: session.vim, obsession.vim , autosession.vim , session.vim, Vim-Sessions, Vim-simple-session
The conclusion was that I didn't think there was a plugin can be used to manage Vim's session and viminfo files together.
Then I spent some spare time on it.
--
--
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 made a vim plugin named Session-Viminfo-Management(http://www.vim.org/scripts/script.php?script_id=5005), built upon Vim's built-in :mksession and :wviminfo commands.
It provide great convinience to save and load your Vim session and viminfo files automatically.
Will anybody to have a try?
I will be glad to read your feedback if any :)
BTW, actually, I didn't want to reinvent wheels. So I've had done some researches on vim.org before real development:
Searched on vim.org by keywords "workspace", seems no relative plugin found.
Searched on vim.org by keywords "viminfo", seems no relative plugin found.
Searched on vim.org by keywords "session", found some: session.vim, obsession.vim , autosession.vim , session.vim, Vim-Sessions, Vim-simple-session
The conclusion was that I didn't think there was a plugin can be used to manage Vim's session and viminfo files together.
Then I spent some spare time on it.
--
--
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: Matchit plugin doesn't match square brackets
On Wednesday, August 20, 2014 1:39:39 PM UTC-5, Matteo Riva wrote:
> When using the matchit plugin I can't get the matching to work on
>
> square brackets, unless I use the :MatchDebug command, then they work
>
> fine.
>
> Everything else is working as far as I can tell, and b:match_words includes [:]
>
>
>
> Tested both on vim 7.2 and 7.3 (same config and plugins, two different
>
> debian systems).
>
>
>
> What could be causing this?
Don't know. Works fine for me. You have the plugin enabled, and you checked b:match_words in the same buffer it's not working in?
--
--
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.
> When using the matchit plugin I can't get the matching to work on
>
> square brackets, unless I use the :MatchDebug command, then they work
>
> fine.
>
> Everything else is working as far as I can tell, and b:match_words includes [:]
>
>
>
> Tested both on vim 7.2 and 7.3 (same config and plugins, two different
>
> debian systems).
>
>
>
> What could be causing this?
Don't know. Works fine for me. You have the plugin enabled, and you checked b:match_words in the same buffer it's not working in?
--
--
You received this message from the "vim_use" maillist.
Do not top-post! Type your reply below the text you are replying to.
For more information, visit http://www.vim.org/maillist.php
---
You received this message because you are subscribed to the Google Groups "vim_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Subscribe to:
Posts (Atom)