[ANN] minpac v1.0: a minimal package manager for Vim 8

2017-04-21 Thread Ken Takata
Hi all,

I announce release of minpac ver 1.0.
It is a minimal package manager for Vim 8 (and Neovim).

  https://github.com/k-takata/minpac

Minpac utilizes the packages feature of Vim 8, and uses the jobs feature for
parallel install/update.  So, it is simple and fast.

Have fun!

Regards,
Ken Takata

-- 
-- 
You received this message from the "vim_use" maillist.
Do not top-post! Type your reply below the text you are replying to.
For more information, visit http://www.vim.org/maillist.php

--- 
You received this message because you are subscribed to the Google Groups 
"vim_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to vim_use+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Re: Swap directory changes when opening files under /media [Fedora]

2017-04-21 Thread Ben Fritz
On Friday, April 21, 2017 at 5:16:17 AM UTC-5, Ian wrote:
> Perfect, thanks. Here's what I get:
> 
> --- Auto-Commands ---
> fedora  BufReadPre
> /media/*  set directory=~/tmp,/var/tmp,/tmp
>   Last set from /etc/vimrc
> /run/media/*
>   set directory=~/tmp,/var/tmp,/tmp
>   Last set from /etc/vimrc
> /mnt/*set directory=~/tmp,/var/tmp,/tmp
>   Last set from /etc/vimrc
> ...
> 
> This lead me to /etc/vimrc which has a line:
> 
>   " don't write swapfile on most commonly used directories for NFS mounts or 
> USB sticks
>   autocmd BufNewFile,BufReadPre /media/*,/run/media/*,/mnt/* set 
> directory=~/tmp,/var/tmp,/tmp
> 
> Which confuses me. The aim appears to be to NOT write swap files but all it 
> does is change the location of swap files. And I do want swap files for my 
> mounts in case of recovery.
> 
> 

I think the intent is not to block swap files, but rather to prevent swap files 
being written to removable media, which can degrade the lifetime of said media 
with limited write cycles before failure.

-- 
-- 
You received this message from the "vim_use" maillist.
Do not top-post! Type your reply below the text you are replying to.
For more information, visit http://www.vim.org/maillist.php

--- 
You received this message because you are subscribed to the Google Groups 
"vim_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to vim_use+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Re: A million Euro raised for Uganda

2017-04-21 Thread Bram Moolenaar

Martin Tournoij wrote:

> Hey all,
> 
> It looks like that as of 2017, about a million Euro in total has been
> raised for Uganda. See my answer here for details:
> https://vi.stackexchange.com/q/572/51
> 
> Of course, we don't know if it was all Vimmers that raised the million,
> but the majority probably is.

Wow, that's impressive!

The estimate for the German donations are a bit too high though.  Last
year was about 16,000 euro.

If you wonder what the children get for the money: We recently had two
students finish their university studies that we are proud of.  One of
them is now a Doctor (still has to finish his practical year) and one a
registered lawyer.  Less than twenty years ago they were hungry and
sleeping on a mud floor with only an old blanket...

-- 
ARTHUR:  Bloody peasant!
DENNIS:  Oh, what a give away.  Did you hear that, did you hear that, eh?
 That's what I'm on about -- did you see him repressing me, you saw it
 didn't you?
  The Quest for the Holy Grail (Monty Python)

 /// Bram Moolenaar -- b...@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+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


A million Euro raised for Uganda

2017-04-21 Thread Martin Tournoij
Hey all,

It looks like that as of 2017, about a million Euro in total has been
raised for Uganda. See my answer here for details:
https://vi.stackexchange.com/q/572/51

Of course, we don't know if it was all Vimmers that raised the million,
but the majority probably is.

Cheers,
Martin

-- 
-- 
You received this message from the "vim_use" maillist.
Do not top-post! Type your reply below the text you are replying to.
For more information, visit http://www.vim.org/maillist.php

--- 
You received this message because you are subscribed to the Google Groups 
"vim_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to vim_use+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Vim documentation index.txt using word "buffer" for the word "register"

2017-04-21 Thread rene . heymans
Dear All,

I'm preparing a presentation of Vim's essentials hence I'm extensively browsing 
through Vim's documentation. Unless I'm mistaken it seems that in the index.txt 
file the word 'buffer' is quite often used in lieu of 'register'. I found this 
by chance while I was looking for the word 'buffer' (:help index   :set hls
/buffer).

For instance:

|C| ["x]C   2  change from the cursor position to the end
   of the line, and N-1 more lines [into
   buffer x]; synonym for "c$"

Now if I follow the tag |C| (positioning my cursor on it, then typing CTRL-]) I 
read in change.txt:

*C*
["x]C   Delete from the cursor position to the end of the
line and [count]-1 more lines [into register x], and
start insert.  Synonym for c$ (not |linewise|).

The notation '"x' unambiguously refers to 'register x'. So in the index.txt 
file I think that one should read 'register' in lieu of 'buffer' while the text 
in change.txt uses the word 'register' correctly.

This is mostly the case in section 2 (Normal mode) and once in section 2.4 (gp 
command). In other places (section 5 EX commands) the word 'buffer' seems to be 
always used appropriately.

These small discrepancies might confuse new users. Indeed clear vocabulary and 
precise definitions are important in the learning process.

I'm too new to Vim and far from an expert but I'd be very happy to contribute 
by reviewing the index.txt file and proposing an update with the word changes. 
It seems not too difficult: everywhere one reads '["x]' one should also read 
'[into register x]'.  However I'd prefer to pass my updates to someone with 
expertise and authority to review my proposed changes.

Note: I found it in Vim version 7.4 and 8.0

Thanks in advance for your feedback.
René

-- 
-- 
You received this message from the "vim_use" maillist.
Do not top-post! Type your reply below the text you are replying to.
For more information, visit http://www.vim.org/maillist.php

--- 
You received this message because you are subscribed to the Google Groups 
"vim_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to vim_use+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Re: command-t plugin need wrong ruby version

2017-04-21 Thread Sand Glass
On Friday, April 21, 2017 at 12:48:01 AM UTC+8, Sand Glass wrote:
> I want to install command-t plugin.(gvim 7.4; windows)
> https://github.com/wincent/command-t
> It needs ruby 1.9.2. I download the right ruby version.
> http://rubyinstaller.org/downloads/archives
> But when I run ':ruby 1' to test ruby. It shows Error "E370  
> msvcrt-ruby192.dll
>  lost", then I goto the ruby diretory to search the 192.dll, but only 
> msvcrt-ruby191.dll, I tried all 192 ruby verion in above page. All of them 
> 191.dll, I tried to change msvcrt-ruby191.dll to msvcrt-ruby192.dll, not work.
> 
> question:
> Is there anyone istall command-t plugin, how do you do it?

command-t is a good plugin, so there should be someone tracked in here.

-- 
-- 
You received this message from the "vim_use" maillist.
Do not top-post! Type your reply below the text you are replying to.
For more information, visit http://www.vim.org/maillist.php

--- 
You received this message because you are subscribed to the Google Groups 
"vim_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to vim_use+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Re: Swap directory changes when opening files under /media [Fedora]

2017-04-21 Thread Gary Johnson
On 2017-04-21, Ian wrote:
> I've just added this to my profile and it has fixed the problem:
> 
> autocmd BufNewFile,BufReadPre /media/*,/run/media/*,/mnt/* set 
> directory=~/.vim/swap//
> 
> Though there might be a better way to just disable the other
> autocmd somehow.

To disable it, put this in your ~/.vimrc:

if exists("#fedora#BufNewFile#/media/*")
au! fedora BufNewFile /media/*
endif
if exists("#fedora#BufNewFile#/mnt/*")
au! fedora BufNewFile /mnt/*
endif
if exists("#fedora#BufReadPre#/media/*")
au! fedora BufReadPre /media/*
endif
if exists("#fedora#BufReadPre#/mnt/*")
au! fedora BufReadPre /mnt/*
endif

That will test for the presence of each of those autocommand events
and patterns in the fedora group and remove them.

Regards,
Gary

-- 
-- 
You received this message from the "vim_use" maillist.
Do not top-post! Type your reply below the text you are replying to.
For more information, visit http://www.vim.org/maillist.php

--- 
You received this message because you are subscribed to the Google Groups 
"vim_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to vim_use+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Re: Swap directory changes when opening files under /media [Fedora]

2017-04-21 Thread Ian
I've just added this to my profile and it has fixed the problem:

autocmd BufNewFile,BufReadPre /media/*,/run/media/*,/mnt/* set 
directory=~/.vim/swap//

Though there might be a better way to just disable the other autocmd somehow.

-- 
-- 
You received this message from the "vim_use" maillist.
Do not top-post! Type your reply below the text you are replying to.
For more information, visit http://www.vim.org/maillist.php

--- 
You received this message because you are subscribed to the Google Groups 
"vim_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to vim_use+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Re: Swap directory changes when opening files under /media [Fedora]

2017-04-21 Thread Ian
Perfect, thanks. Here's what I get:

--- Auto-Commands ---
fedora  BufReadPre
/media/*  set directory=~/tmp,/var/tmp,/tmp
Last set from /etc/vimrc
/run/media/*
  set directory=~/tmp,/var/tmp,/tmp
Last set from /etc/vimrc
/mnt/*set directory=~/tmp,/var/tmp,/tmp
Last set from /etc/vimrc
...

This lead me to /etc/vimrc which has a line:

  " don't write swapfile on most commonly used directories for NFS mounts or 
USB sticks
  autocmd BufNewFile,BufReadPre /media/*,/run/media/*,/mnt/* set 
directory=~/tmp,/var/tmp,/tmp

Which confuses me. The aim appears to be to NOT write swap files but all it 
does is change the location of swap files. And I do want swap files for my 
mounts in case of recovery.

I am tempted to remove this line though it feels a bit hacky to change this in 
/etc/vimrc. I will see if I can work out how to override this autocmd in my own 
profile perhaps.

-- 
-- 
You received this message from the "vim_use" maillist.
Do not top-post! Type your reply below the text you are replying to.
For more information, visit http://www.vim.org/maillist.php

--- 
You received this message because you are subscribed to the Google Groups 
"vim_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to vim_use+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.