Re: Interloper vi

On Wednesday, August 1, 2018 at 4:24:14 PM UTC+12, Suresh Govindachar wrote:
...
> $ alias vi
> bash: alias: vi: not found

reveals your shell is bash.

> $ which vi
> /lhome/me/tools/bin/vi

"which" is not what you want with bash. It is /usr/bin/which, not a bash built-in, so it doesn't tell you what bash will do. In a new bash window, if I run:

$ type vim
vim is /usr/local/bin/vim
$ vim -c q
# the screen clears...
$ which vim
/usr/local/bin/vim
$ type vim
vim is hashed (/usr/local/bin/vim)

So, better use "type". Seeing vim hashed to something you don't expect would at least be a hint towards Tony's advice to try hash -r.

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.

Re: Interloper vi

Maybe your shell has forgotten to update its hash tables of
"remembered" program locations.

Try (at a shell prompt)
hash -r

to forget everything, then invoke vi again.

Best regards,
Tony.

On Wed, Aug 1, 2018 at 6:24 AM, 'Suresh Govindachar' via vim_use
<vim_use@googlegroups.com> wrote:
>
> Tried the suggestions from Tim and Tony, but to no avail:
>
>
> $ echo $PATH
>
> /lhome/me/tools/bin:/lhome/me/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games:/snap/bin:/usr/local/cuda/bin:/usr/local/cuda/bin:/opt/rocm/bin:/lhome/me/g/bin
>
> $ alias vi
> bash: alias: vi: not found
>
> $ cd
> $ find . -maxdepth 1 -type f |xargs grep alias | grep vi
> <no output>
>
> $ type -a vi
> vi is /lhome/me/tools/bin/vi
> vi is /usr/bin/vi
>
> $ ll /lhome/me/tools/bin/vi
> lrwxrwxrwx 1 hidden hidden 28 Jul 31 19:18 /lhome/me/tools/bin/vi ->
> /lhome/me/tools/bin/vim*
>
> $ ll /lhome/me/tools/bin/vim
> -rwxr-xr-x 1 hidden hidden 2723248 Jul 31 18:53 /lhome/me/tools/bin/vim*
>
> $ ll /usr/bin/vi
> lrwxrwxrwx 1 root root 20 Jun 16 2017 /usr/bin/vi ->
> /etc/alternatives/vi*
>
> $ ll /etc/alternatives/vi
> lrwxrwxrwx 1 root root 17 Jun 21 2017 /etc/alternatives/vi ->
> /usr/bin/vim.gtk3*
>
> $ ll /usr/bin/vim.gtk3
> -rwxr-xr-x 1 root root 2927872 Nov 24 2016 /usr/bin/vim.gtk3*
>
> $ which vi
> /lhome/me/tools/bin/vi
>
> Still `vi --version` shows the old version (and `vim --version` shows
> the latest version)
>
>
> --
> --
> You received this message from the "vim_use" maillist.
> Do not top-post! Type your reply below the text you are replying to.
> For more information, visit http://www.vim.org/maillist.php
>
> --- You received this message because you are subscribed to the Google
> Groups "vim_use" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to vim_use+unsubscribe@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.

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

---
You received this message because you are subscribed to the Google Groups "vim_use" group.
To unsubscribe from this group and 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: Interloper vi

Tried the suggestions from Tim and Tony, but to no avail:


$ echo $PATH

/lhome/me/tools/bin:/lhome/me/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games:/snap/bin:/usr/local/cuda/bin:/usr/local/cuda/bin:/opt/rocm/bin:/lhome/me/g/bin

$ alias vi
bash: alias: vi: not found

$ cd
$ find . -maxdepth 1 -type f |xargs grep alias | grep vi
<no output>

$ type -a vi
vi is /lhome/me/tools/bin/vi
vi is /usr/bin/vi

$ ll /lhome/me/tools/bin/vi
lrwxrwxrwx 1 hidden hidden 28 Jul 31 19:18 /lhome/me/tools/bin/vi
-> /lhome/me/tools/bin/vim*

$ ll /lhome/me/tools/bin/vim
-rwxr-xr-x 1 hidden hidden 2723248 Jul 31 18:53
/lhome/me/tools/bin/vim*

$ ll /usr/bin/vi
lrwxrwxrwx 1 root root 20 Jun 16 2017 /usr/bin/vi ->
/etc/alternatives/vi*

$ ll /etc/alternatives/vi
lrwxrwxrwx 1 root root 17 Jun 21 2017 /etc/alternatives/vi ->
/usr/bin/vim.gtk3*

$ ll /usr/bin/vim.gtk3
-rwxr-xr-x 1 root root 2927872 Nov 24 2016 /usr/bin/vim.gtk3*

$ which vi
/lhome/me/tools/bin/vi

Still `vi --version` shows the old version (and `vim --version`
shows the latest version)

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

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

Re: Interloper vi

On Wed, Aug 1, 2018 at 4:37 AM, Tony Mechelynck
<antoine.mechelynck@gmail.com> wrote:
> If you use the bash shell, the command "type -a vi" (without the
> quotes) will tell you every alias and every executable in the $PATH
> with the name "vi", and it will display them in the order in which the
> shell loks for them.
>
> If there is an alias for "vi", you can remove it with
> unalias vi
> then the symlink you already have ought to become the first "vi" that
> bash finds, and it loads your new home-compiled vim.

P.S. This "unalias" command is only temporary. If you want to make it
permanent, you will have to remove or override that alias, which is
set by one (or more) of the startup scripts run by your shell. See the
shell's manpage for details.
>
> Best regards,
> Tony.
>
> On Wed, Aug 1, 2018 at 4:23 AM, Tim Chase <vim@tim.thechases.com> wrote:
>> On 2018-07-31 19:20, 'Suresh Govindachar' via vim_use wrote:
>>> Why is the old vi being executed even though `which vi` shows the
>>> newer one? And how to get vi to execute the newly installed vim?
>>
>> Have you checked for an alias? Possibly something like
>>
>> $ alias vi
>> alias vi='/usr/bin/vi'
>>
>> Also, what's your $PATH?
>>
>> $ echo $PATH
>>
>> -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.

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

---
You received this message because you are subscribed to the Google Groups "vim_use" group.
To unsubscribe from this group and 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: Interloper vi

If you use the bash shell, the command "type -a vi" (without the
quotes) will tell you every alias and every executable in the $PATH
with the name "vi", and it will display them in the order in which the
shell loks for them.

If there is an alias for "vi", you can remove it with
unalias vi
then the symlink you already have ought to become the first "vi" that
bash finds, and it loads your new home-compiled vim.

Best regards,
Tony.

On Wed, Aug 1, 2018 at 4:23 AM, Tim Chase <vim@tim.thechases.com> wrote:
> On 2018-07-31 19:20, 'Suresh Govindachar' via vim_use wrote:
>> Why is the old vi being executed even though `which vi` shows the
>> newer one? And how to get vi to execute the newly installed vim?
>
> Have you checked for an alias? Possibly something like
>
> $ alias vi
> alias vi='/usr/bin/vi'
>
> Also, what's your $PATH?
>
> $ echo $PATH
>
> -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.

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

---
You received this message because you are subscribed to the Google Groups "vim_use" group.
To unsubscribe from this group and 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: Interloper vi

On 2018-07-31 19:20, 'Suresh Govindachar' via vim_use wrote:
> Why is the old vi being executed even though `which vi` shows the
> newer one? And how to get vi to execute the newly installed vim?

Have you checked for an alias? Possibly something like

$ alias vi
alias vi='/usr/bin/vi'

Also, what's your $PATH?

$ echo $PATH

-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.

Interloper vi

Hello,

On Ubuntu 16.04, downloaded sources from github, and executed

cd vim
./configure --prefix=/lhome/me/tools
cd src
make
make install

ls /lhome/me/tools/bin does not show any vi. So executed

cd /lhome/me/tools/bin
ln -s /lhome/me/tools/bin/vim vi

$ which vi
/lhome/me/tools/bin/vi

$ ll /lhome/me/tools/bin/vi
lrwxrwxrwx 1 hidden hidden 3 Jul 31 19:01 /lhome/me/tools/bin/vi ->
/lhome/me/tools/bin/vim*

vim --version does show the expected version.
However, vi --version shows some old version!

Why is the old vi being executed even though `which vi` shows the newer
one? And how to get vi to execute the newly installed vim?

$ ll /usr/bin/vi
lrwxrwxrwx 1 root root 20 Jun 16 2017 /usr/bin/vi ->
/etc/alternatives/vi*

$ ll /etc/alternatives/vi
lrwxrwxrwx 1 root root 17 Jun 21 2017 /etc/alternatives/vi ->
/usr/bin/vim.gtk3*

Thanks,

--Suresh

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

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

Re: how to match the first pattern

On Tue, 31 Jul 2018, Michael Wagner wrote:

> On Jul 30, 2018 um 18:46:42, Sand Glass wrote:
> If you are on Linux, you can test 'txt2regex'.

Interesting! And a good way to compose for more
than one of the dialects. Bit ALAS, it does
not know (as far as I saw) about 'shortest'
aka non-greedy matches.


--
Christoph von Stuckrad * * | also XMPP = |Mail <stucki@mi.fu-berlin.de> \
Freie Universitaet Berlin |/_*| 'jabber' via|Tel(Mo.,Mi.):+49 30 838-75 459|
IT Mathematik & Informatik|\ *|stucki@jabber| (Di,Do,Fr):+49 30 77 39 6600|
Takustr. 9 / 14195 Berlin * * |.fu-berlin.de|Fax(home): +49 30 77 39 6601/


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

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

Re: how to match the first pattern

On Jul 30, 2018 um 18:46:42, Sand Glass wrote:
> On Monday, July 30, 2018 at 8:13:26 PM UTC+8, Tony Mechelynck wrote:
> >
> > Ah yes, there are several regular-expression "dialects", often quite
> > similar but not always strictly identical, and depending on whether
> > you are using grep (which has two: "normal" and "extended"), Vim
> > (which has four: "very nomagic", "nomagic", "magic" and "very magic"),
> > perl, less, etc. you need to always use just the precisely right
> > dialect for whichever RE engine will be interpreting it.
> >
> > Best regards,
> > Tony.
>
> I use some simple regular expression in 'windows search', 'notepad++
> search', 'ultraedit search', 'visual studio ENV'. The regular
> expression is so precisely that I cannot remember all of them. So
> each time when I using RE in a programming language(c/cpp) or a
> tool, I will try and try again, until the result is I want.
> Before I post this topic, I only try '*', '.', '+', '?' for RE
> matching. After I post the topic, I learned the '{n,m}', '-'. Thanks
> a lot.
> By the way, find a help doc is another way. This is the perl RE
> online doc:
> For more options, visit https://groups.google.com/d/optout.
> http://perldoc.perl.org/perlretut.html#Matching-repetitions
>

If you are on Linux, you can test 'txt2regex'.

apt show txt2regex
Package: txt2regex
Version: 0.8-5
Description: A Regular Expression "wizard", all written with bash2
builtins
^txt2regex$ is a Regular Expression "wizard", all written with bash2
builtins, that converts human sentences to RegExs. With a simple
interface, you just answer to questions and build your own RegEx for a
large variety of programs, like awk, emacs, grep, perl, php, procmail,
python, sed and vim. There are more than 20 supported programs.

Just my 2¢
Michael

--
Sound Blaster Pro - A professional way to blow your ears

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

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

International Vim conference VimConf 2018

Hello Vim users!

Announcing an international Vim conference VimConf 2018 and its CFP being open.

https://vimconf.org/2018/

VimConf is the only and the first international Vim conference that has been running periodically by a Vim community. It had been running for 5 times, and in Tokyo, Japan, so far. We organize VimConf this year again. It'll be in Tokyo, Japan, on Nov 24, 2018.
I'm going to give a keynote speech there this year. This is a big news you probably don't know, Bram has plan to come to vimconf 2018!!

All the talks will be translated to English/Japanese vice versa. The tickets to participate aren't sold yet but you can already submit a proposal to speech there. Would you like to try talking there to share what you know about Vim inside?
Please check the VimConf website for details.

See you there,
mattn

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

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

Re: how to match the first pattern

On Tuesday, July 31, 2018 at 9:46:43 AM UTC+8, Sand Glass wrote:
> On Monday, July 30, 2018 at 8:13:26 PM UTC+8, Tony Mechelynck wrote:
> > On Mon, Jul 30, 2018 at 1:55 PM, Chr. von Stuckrad
> > <stucki@mi.fu-berlin.de> wrote:
> > > On Mon, 30 Jul 2018, Sand Glass wrote:
> > >
> > >> On Saturday, July 28, 2018 at 3:18:23 PM UTC+8, Sand Glass wrote:
> > >> > how can I stop the pattern at the first "]"?
> > >> It's good in vim. Then I try to use the regular in perl script, but failed.
> > >
> > > Same 'thing', i.e. the shortest match, so (in linux 'man perlre')
> > > as far as I remember a '?' behind the '*' makes it 'non-greedy'
> > > and this \[.*?\] gives 'the next closing ']' .

If I use perl script to get the same result in vim. The RE is(match the pattern and remove them):
$line =~ s/\[.*?\]//g

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

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

Re: how to match the first pattern

On Monday, July 30, 2018 at 8:13:26 PM UTC+8, Tony Mechelynck wrote:
> On Mon, Jul 30, 2018 at 1:55 PM, Chr. von Stuckrad
> <stucki@mi.fu-berlin.de> wrote:
> > On Mon, 30 Jul 2018, Sand Glass wrote:
> >
> >> On Saturday, July 28, 2018 at 3:18:23 PM UTC+8, Sand Glass wrote:
> >> > how can I stop the pattern at the first "]"?
> >> It's good in vim. Then I try to use the regular in perl script, but failed.
> >
> > Same 'thing', i.e. the shortest match, so (in linux 'man perlre')
> > as far as I remember a '?' behind the '*' makes it 'non-greedy'
> > and this \[.*?\] gives 'the next closing ']' .
> >
> > Stucki
>
> Ah yes, there are several regular-expression "dialects", often quite
> similar but not always strictly identical, and depending on whether
> you are using grep (which has two: "normal" and "extended"), Vim
> (which has four: "very nomagic", "nomagic", "magic" and "very magic"),
> perl, less, etc. you need to always use just the precisely right
> dialect for whichever RE engine will be interpreting it.
>
> Best regards,
> Tony.

I use some simple regular expression in 'windows search', 'notepad++ search', 'ultraedit search', 'visual studio ENV'. The regular expression is so precisely that I cannot remember all of them. So each time when I using RE in a programming language(c/cpp) or a tool, I will try and try again, until the result is I want.
Before I post this topic, I only try '*', '.', '+', '?' for RE matching. After I post the topic, I learned the '{n,m}', '-'. Thanks a lot.
By the way, find a help doc is another way. This is the perl RE online doc:
http://perldoc.perl.org/perlretut.html#Matching-repetitions

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

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

Re: how to match the first pattern

On Mon, Jul 30, 2018 at 1:55 PM, Chr. von Stuckrad
<stucki@mi.fu-berlin.de> wrote:
> On Mon, 30 Jul 2018, Sand Glass wrote:
>
>> On Saturday, July 28, 2018 at 3:18:23 PM UTC+8, Sand Glass wrote:
>> > how can I stop the pattern at the first "]"?
>> It's good in vim. Then I try to use the regular in perl script, but failed.
>
> Same 'thing', i.e. the shortest match, so (in linux 'man perlre')
> as far as I remember a '?' behind the '*' makes it 'non-greedy'
> and this \[.*?\] gives 'the next closing ']' .
>
> Stucki

Ah yes, there are several regular-expression "dialects", often quite
similar but not always strictly identical, and depending on whether
you are using grep (which has two: "normal" and "extended"), Vim
(which has four: "very nomagic", "nomagic", "magic" and "very magic"),
perl, less, etc. you need to always use just the precisely right
dialect for whichever RE engine will be interpreting it.

Best regards,
Tony.

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

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

Re: how to match the first pattern

On Mon, 30 Jul 2018, Sand Glass wrote:

> On Saturday, July 28, 2018 at 3:18:23 PM UTC+8, Sand Glass wrote:
> > how can I stop the pattern at the first "]"?
> It's good in vim. Then I try to use the regular in perl script, but failed.

Same 'thing', i.e. the shortest match, so (in linux 'man perlre')
as far as I remember a '?' behind the '*' makes it 'non-greedy'
and this \[.*?\] gives 'the next closing ']' .

Stucki

--
Christoph von Stuckrad * * | also XMPP = |Mail <stucki@mi.fu-berlin.de> \
Freie Universitaet Berlin |/_*| 'jabber' via|Tel(Mo.,Mi.):+49 30 838-75 459|
IT Mathematik & Informatik|\ *|stucki@jabber| (Di,Do,Fr):+49 30 77 39 6600|
Takustr. 9 / 14195 Berlin * * |.fu-berlin.de|Fax(home): +49 30 77 39 6601/


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

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

Re: how to match the first pattern

On Saturday, July 28, 2018 at 3:18:23 PM UTC+8, Sand Glass wrote:
> This is my code block:
> ###########
> output [NUM_STAGE-1:0] enable;
> input [7:0] big_grad_thr;//8'h10 [2:0]
> ###########
> I want to find pattern "[NUM_STAGE-1:0]" "[7:0]",
> I tried '/\[.*\]', but the result is "[7:0] big_grad_thr;//8'h10 [2:0]",
> how can I stop the pattern at the first "]"?

It's good in vim. Then I try to use the regular in perl script, but failed.

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

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

Re: syntax highlighting not correct in bash script

On Sun, Jul 29, 2018 at 7:37 AM, John Little <john.b.little@gmail.com> wrote:
> With the vim 8.1.0224 from git, I see the problem.

Thanks for your help.

> The maintainer of sh.vim has fixed quoting problems in his latest version, 179, at http://www.drchip.org/astronaut/vim/index.html#SYNTAX_SH and indeed version 179 colours your snippet correctly for me; it works with the 8.0.1453 I get with my distro, derived from Ubuntu 18.04, so I expect it will work for you.
>

Confirm that using the 179 version fixed the problem. For the record,
my vim version is 8.0.707 and I just copied the sh.vim to
~/.vim/syntax .

> I imagine your snippet is a minimal example of the problem, kudos for that, but still looks pathological to me; I avoid tricky stuff like that for the sake of my sanity.

Yes.The snippet I provided is a minimal example. The
UPSTREAM=${1:-'@{u}'} sets UPSTREAM variable to the first argument. If
no such argument is supplied, it uses @u which represents the upstream
branch (in git parlance). If you are curious, the complete script is
at https://github.com/KamarajuKusumanchi/rutils/blob/master/bin/git-up
.

regards
raju
--
Kamaraju S Kusumanchi | http://raju.shoutwiki.com/wiki/Blog

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

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

Re: syntax highlighting not correct in bash script

With the vim 8.1.0224 from git, I see the problem. (BTW, the colours depend totally upon the colour scheme being used, so characterizing the problem by the colours seen isn't very useful. Maybe using the default scheme, starting vim with --clean -N could be.)

The problem causes the syntax colouring to lose track of what is quoted, and following lines of script are coloured as if quoted.

The maintainer of sh.vim has fixed quoting problems in his latest version, 179, at http://www.drchip.org/astronaut/vim/index.html#SYNTAX_SH and indeed version 179 colours your snippet correctly for me; it works with the 8.0.1453 I get with my distro, derived from Ubuntu 18.04, so I expect it will work for you.

I imagine your snippet is a minimal example of the problem, kudos for that, but still looks pathological to me; I avoid tricky stuff like that for the sake of my sanity.

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.

Re: syntax highlighting not correct in bash script

On Sat, Jul 28, 2018 at 3:00 PM, tooth pik <toothpik6@gmail.com> wrote:
> my vim is newer than yours, so i'll wager my syntax/sh.vim is newer too
>
> anyway, that exact command renders just fine in my vim (8.1.223)
>

My /usr/share/vim/vim80/syntax/sh.vim is

" Last Change: Sep 22, 2016
" Version: 165

I see the 8.1.223 file in
https://github.com/vim/vim/blob/v8.1.0223/runtime/syntax/sh.vim . I
downloaded it to ~/.vim/syntax/sh.vim . Even then I get the same
behavior. Do I need to copy any other files besides that?

thanks
raju

--
Kamaraju S Kusumanchi | http://raju.shoutwiki.com/wiki/Blog

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

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

Re: syntax highlighting not correct in bash script

my vim is newer than yours, so i'll wager my syntax/sh.vim is newer too

anyway, that exact command renders just fine in my vim (8.1.223)

On Sat, Jul 28, 2018 at 10:13 AM, kamaraju kusumanchi
<raju.mailinglists@gmail.com> wrote:
> The following shell script is not highlighted correctly.
>
> . % cat foo.sh
> #!/usr/bin/bash
>
> UPSTREAM=${1:-'@{u}'}
>
> Please find the screenshot at https://pasteboard.co/HwyXxZU.png .
>
> As you can see in the screenshot, the first and second left curly
> braces are blue and yellow while the third and fourth right curly
> braces are blue and magenta. Any idea why?
>
> Using vim 8.0, on Debian 9.5 (Stretch).
>
> thanks
> raju
> --
> Kamaraju S Kusumanchi | http://raju.shoutwiki.com/wiki/Blog
>
> --
> --
> You received this message from the "vim_use" maillist.
> Do not top-post! Type your reply below the text you are replying to.
> For more information, visit http://www.vim.org/maillist.php
>
> ---
> You received this message because you are subscribed to the Google Groups "vim_use" group.
> To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.

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

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

syntax highlighting not correct in bash script

The following shell script is not highlighted correctly.

. % cat foo.sh
#!/usr/bin/bash

UPSTREAM=${1:-'@{u}'}

Please find the screenshot at https://pasteboard.co/HwyXxZU.png .

As you can see in the screenshot, the first and second left curly
braces are blue and yellow while the third and fourth right curly
braces are blue and magenta. Any idea why?

Using vim 8.0, on Debian 9.5 (Stretch).

thanks
raju
--
Kamaraju S Kusumanchi | http://raju.shoutwiki.com/wiki/Blog

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

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

Re: how to match the first pattern

On Sat, Jul 28, 2018 at 9:18 AM, Sand Glass <youngluoyang@gmail.com> wrote:
> This is my code block:
> ###########
> output [NUM_STAGE-1:0] enable;
> input [7:0] big_grad_thr;//8'h10 [2:0]
> ###########
> I want to find pattern "[NUM_STAGE-1:0]" "[7:0]",
> I tried '/\[.*\]', but the result is "[7:0] big_grad_thr;//8'h10 [2:0]",
> how can I stop the pattern at the first "]"?

See :help pattern-overview

The * multi matches "as many as possible" of the preceding atom. To
match "as few as possible", use \{-} instead.

Best regards,
Tony.

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

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

how to match the first pattern

This is my code block:
###########
output [NUM_STAGE-1:0] enable;
input [7:0] big_grad_thr;//8'h10 [2:0]
###########
I want to find pattern "[NUM_STAGE-1:0]" "[7:0]",
I tried '/\[.*\]', but the result is "[7:0] big_grad_thr;//8'h10 [2:0]",
how can I stop the pattern at the first "]"?

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

---
You received this message because you are subscribed to the Google Groups "vim_use" group.
To unsubscribe from this group and 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: highlight some line

On Fri, Jul 27, 2018 at 11:28 AM, Константин Изюмов
<konstantin8105@gmail.com> wrote:
> Hello, vimers!
> Could you help.
> I always use "syntax off" and use regex "/\/\/.*" for highlight the single line comments.
> May I add somewhere 2 regex:
> 1) "/\/\/.*" Color: yellow
> 2) "\".*\"" Color: red
> for always switch on without "syntax on".
>
> Thank you for help.

See :help :match


Best regards,
Tony.

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

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

highlight some line

Hello, vimers!
Could you help.
I always use "syntax off" and use regex "/\/\/.*" for highlight the single line comments.
May I add somewhere 2 regex:
1) "/\/\/.*" Color: yellow
2) "\".*\"" Color: red
for always switch on without "syntax on".

Thank you for help.

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

---
You received this message because you are subscribed to the Google Groups "vim_use" group.
To unsubscribe from this group and 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: at second launch E121 : Undefined variable: paste#paste_cmd

Le mercredi 25 juillet 2018 16:35:05 UTC+2, Tony Mechelynck a écrit :
> On Wed, Jul 25, 2018 at 4:08 PM, Ni Va <nivaemail@gmail.com> wrote:
> > Hi,
> >
> > I deploy this Vim 8.1.209 x86 built on windows 10 on windows 7 in $tmp directory.
> >
> > At first launch no problem appears.
> > At second launch, for any reason, the message E121 : Undefined variable: paste#paste_cmd of line 156 of (c:\users\myUser\appdata\local\temp\vim_x86\vim81\menu.vim)
> >
> > Don't understand why ?
> > Thank you in advance.
> > NiVa
>
> Are you sure you have all the latest runtime files? I see that
> particular line at line 163, not 156, of $VIMRUNTIME/menu.vim, maybe
> you also "forgot" to download and install
> $VIMRUNTIME/autoload/paste.vim? (That file is almost one year old
> though, you really ought to have it.)
>
> Best regards,
> Tony.

Yes that's it. I forget to merge runtimefiles at this time.
Thank you and Sorry for inconvenience.
NiVa

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

---
You received this message because you are subscribed to the Google Groups "vim_use" group.
To unsubscribe from this group and 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: at second launch E121 : Undefined variable: paste#paste_cmd

On Wed, Jul 25, 2018 at 4:08 PM, Ni Va <nivaemail@gmail.com> wrote:
> Hi,
>
> I deploy this Vim 8.1.209 x86 built on windows 10 on windows 7 in $tmp directory.
>
> At first launch no problem appears.
> At second launch, for any reason, the message E121 : Undefined variable: paste#paste_cmd of line 156 of (c:\users\myUser\appdata\local\temp\vim_x86\vim81\menu.vim)
>
> Don't understand why ?
> Thank you in advance.
> NiVa

Are you sure you have all the latest runtime files? I see that
particular line at line 163, not 156, of $VIMRUNTIME/menu.vim, maybe
you also "forgot" to download and install
$VIMRUNTIME/autoload/paste.vim? (That file is almost one year old
though, you really ought to have it.)

Best regards,
Tony.

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

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

at second launch E121 : Undefined variable: paste#paste_cmd

Hi,

I deploy this Vim 8.1.209 x86 built on windows 10 on windows 7 in $tmp directory.

At first launch no problem appears.
At second launch, for any reason, the message E121 : Undefined variable: paste#paste_cmd of line 156 of (c:\users\myUser\appdata\local\temp\vim_x86\vim81\menu.vim)

Don't understand why ?
Thank you in advance.
NiVa

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

---
You received this message because you are subscribed to the Google Groups "vim_use" group.
To unsubscribe from this group and 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: restricted search & replace

On 25/07/2018 05:20, tuxic@posteo.de wrote:
> Hi,
>
> in a table made pure from ascii :) I want to
> replace certain character for all lines but
> in a certain column only.
>
> Therefore I have to restrict search and replace
> to a certain range of colums (vim context not table context).
>
> How can I do that?

See :help \%c, \%<c and \%>c. For instance, /\%>7cX\%<13c/ will
match a sequence of X's, but only between column 8 and 11. So,
s/\%>7cX\%<13c/Y/g will replace the X's with Y's.

Hope this helps,
Life.

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

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

Re: restricted search & replace

On Wed, Jul 25, 2018 at 5:20 AM, <tuxic@posteo.de> wrote:
> Hi,
>
> in a table made pure from ascii :) I want to
> replace certain character for all lines but
> in a certain column only.
>
> Therefore I have to restrict search and replace
> to a certain range of colums (vim context not table context).
>
> How can I do that?
>
> Thank you very much for any help in advance. :)
>
> Cheers
> Meino

Dr. Charles "Chip" Campbell's vis.vim "Visual Block Commands" script
might interest you, but don't take my word for it: go to one of the
pages below, look at the description, and see if it can help you.
"Stable" version: http://vim.sourceforge.net/scripts/script.php?script_id=1195
"Development" version: http://www.drchip.org/astronaut/vim/#VIS

Best regards,
Tony.

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

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

restricted search & replace

Hi,

in a table made pure from ascii :) I want to
replace certain character for all lines but
in a certain column only.

Therefore I have to restrict search and replace
to a certain range of colums (vim context not table context).

How can I do that?

Thank you very much for any help in advance. :)

Cheers
Meino


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

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

Re: yank and put not vmapping in debian stretch

On Mo, 23 Jul 2018, tom arnall wrote:

> Here is output of 'version':
>
> :version
> VIM - Vi IMproved 8.0 (2016 Sep 12, compiled Sep 30 2017 18:21:38)
> Included patches: 1-197, 322, 377-378, 550, 703, 706-707
> Modified by pkg-vim-maintainers@lists.alioth.debian.org
> Compiled by pkg-vim-maintainers@lists.alioth.debian.org
> Huge version without GUI. Features included (+) or not (-):

Missing output....

>
> Here is my procedure for mapping "+y:
>
> 1. enter ':vmap <c-i> "+y<cr>' (to map the visual mode yank)
>
> 2. in blank screen, hit 'i' key (for insert mode)
>
> 3. enter 'now is the time<cr>'.
>
> 4. hit <esc> key
>
> 5. hit 'v' key (for visual mode)
>
> 6. hit 'k' key to select the text
>
> 7. do <c-i> ( actual result is that editor stays in visual mode;
> expected that it would return to normal mode)

I guess it beep? I second the guess, that your Vim/Terminal is unable to
access your clipboard. Please check the detail :version output and try
again with a different register. Also to reproduce, make sure to start
with vim -i NONE -u NONE -N (or use --clean, however that might not be
available on older Vims)


Mit freundlichen Grüßen
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: yank and put not vmapping in debian stretch

This seems to be the source of the confusion right here:

> ... (to map the visual mode yank)

Visual mode doesn't need a separate form of yank. Just use the regular
yank:

:vmap <c-i> y

No <cr> required. When you're in visual mode and then hit y, it yanks the
text and exits visual mode immediately. The <c-i> map then inherits that
behaviour.

As Jürgen says, if you really do want to use the X11 clipboard, you'll need
something like vim-gtk from your package manager, something that ships with
"+X11" (when you check `vim --version`).

If you do end up with a version that has +X11 and you want mappings to work
with the clipboard, you might find something like the following useful:

"""
if has('x11')
nnoremap + :let @+=@0<CR>
nnoremap <silent> <C-c> :set opfunc=YankCB<CR>g@
vnoremap <silent> <C-c> :<C-U>call YankCB(visualmode(), 1)<CR>
function! YankCB(type, ...)
let l:sel_save = &selection
let &selection = 'inclusive'
if a:0 " Invoked from Visual mode, use gv command.
silent exe "normal! gv\"+y"
elseif a:type ==# 'line'
silent exe "normal! '[V']\"+y"
else
silent exe "normal! `[v`]\"+y"
endif
let &selection = l:sel_save
endfunction

nnoremap * :let @*=@0<CR>
nnoremap <silent> <leader>c :set opfunc=YankPS<CR>g@
vnoremap <silent> <leader>c :<C-U>call YankPS(visualmode(), 1)<CR>
function! YankPS(type, ...)
let l:sel_save = &selection
let &selection = 'inclusive'
if a:0 " Invoked from Visual mode, use gv command.
silent exe "normal! gv\"*y"
elseif a:type ==# 'line'
silent exe "normal! '[V']\"*y"
else
silent exe "normal! `[v`]\"*y"
endif
let &selection = l:sel_save
endfunction
endif
"""

This sets up operations that act like the familiar old yank, but sends it
to clipboard or primary selection respectively.


~ 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: yank and put not vmapping in debian stretch

Hi,

tom arnall schrieb am 24.07.2018 um 04:42:
>
> Here is (I hope) the presentation which you have requested.
>
> Here is output of 'version':
>
> :version
> VIM - Vi IMproved 8.0 (2016 Sep 12, compiled Sep 30 2017 18:21:38)
> Included patches: 1-197, 322, 377-378, 550, 703, 706-707
> Modified by pkg-vim-maintainers@lists.alioth.debian.org
> Compiled by pkg-vim-maintainers@lists.alioth.debian.org
> Huge version without GUI. Features included (+) or not (-):
>
> Here is my procedure for mapping "+y:
>
> 1. enter ':vmap <c-i> "+y<cr>' (to map the visual mode yank)

you are using the clipboard register in a non-GUI version. Are you sure
the clipboard register is available? What do

:echo has('x11')

and

:echo has('clipboard')

output? Does your mapping work with a different register, e.g.

:vmap <c-i> "ay

?

Regards,
Jürgen

--
Sometimes I think the surest sign that intelligent life exists elsewhere
in the universe is that none of it has tried to contact us. (Calvin)

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

---
You received this message because you are subscribed to the Google Groups "vim_use" group.
To unsubscribe from this group and 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: yank and put not vmapping in debian stretch

On Tue, Jul 24, 2018 at 4:42 AM, tom arnall <kloro2006@gmail.com> wrote:
> Tony,
>
> Here is (I hope) the presentation which you have requested.
>
> Here is output of 'version':
>
> :version
> VIM - Vi IMproved 8.0 (2016 Sep 12, compiled Sep 30 2017 18:21:38)
> Included patches: 1-197, 322, 377-378, 550, 703, 706-707
> Modified by pkg-vim-maintainers@lists.alioth.debian.org
> Compiled by pkg-vim-maintainers@lists.alioth.debian.org
> Huge version without GUI. Features included (+) or not (-):

As you can see, this Vim executable was compiled almost ten months
ago. Since then, Vim 8.0 went up to patchlevel 1850, Vim 8.1 was
released on 18 May 2018, and its patch level is (as of this writing)
at 209 (and counting). I've tried to reproduce your problem with a Big
build of Vim 8.1.209 on 64-bit openSUSE Linux 15.0 but I couldn't;
you'll see below the tests I did and what happened to me.

One possibility, unlikely as it may seem, is that the problem you got
might be due to the changes from Bram Moolenaar's original sources,
summarized by «Modified by
pkg-vim-maintainers@lists.alioth.debian.org». Another possibility is
that the problem was fixed, either in one of the 1352 patchlevels
published after the source for your Vim was downloaded, or maybe even
in one or more of Vim 8.0 patches 198-321, 379-549, 551-702, 704-705,
(a total of 449 of 707 patches, or 63.5% — almost two-thirds) which
the Debian maintainers did not apply to their source even though they
were available to them when they downloaded it.

I build my Vim executables myself using Bram's original sources, and I
apply all patches, though if they are Windows-only patches ot
tests-only patches I don't build a binary until a patch comes along
which looks relevant to me. I've written up how I do it and uploaded
it online at:
https://vim.wikia.com/wiki/Getting_the_Vim_source_with_Mercurial
http://users.skynet.be/antoine.mechelynck/vim/compunix.htm
I'm told that other people have since then uploaded simplified HowTo
pages for the more common usecases, but I tried to be complete and the
above two llinks are the result.

Could you please compile "your own Vim 8.1" from the latest sources
and tell us if the problem happens again?

Now here are the results of my tests (on a Vim whose first lines of
the ":version" output are further down). I followed your "steps to
reproduce".

After step 7, I saw --VISUAL-- go away near bottom left of my Vim
screen. After step 10, there was a second line identical to the first
one.

So I did it again, neutralizing my vimrc, by invoking Vim as: vim --clean
Then I noticed that I had been typing <C-I> in capitals when defining
the mapping, so I closed Vim down and restarted it, this time defining
the mapping with a {lhs} in all lowercase.

In all cases I got the same result: I am unable to reproduce your problem.

I was doing all this in a konsole terminal, so I hit Ctrl-Alt-F2 and
did it again in the text-only Linux console. Same result as above, so
I came back with Ctrl-Alt-F7.

Here is how my Vim version identifies itself:

VIM - Vi IMproved 8.1 (2018 May 18, compiled Jul 24 2018 05:49:23)
Included patches: 1-209
Compiled by antoine.mechelynck@gmail.com
Big version with GTK2 GUI. Features included (+) or not (-):

>
> Here is my procedure for mapping "+y:
>
> 1. enter ':vmap <c-i> "+y<cr>' (to map the visual mode yank)
>
> 2. in blank screen, hit 'i' key (for insert mode)
>
> 3. enter 'now is the time<cr>'.
>
> 4. hit <esc> key
>
> 5. hit 'v' key (for visual mode)
>
> 6. hit 'k' key to select the text
>
> 7. do <c-i> ( actual result is that editor stays in visual mode;
> expected that it would return to normal mode)
>
> 8. hit 'v' key to exit visual mode
>
> 9. hit 'j' key to move to next line
>
> 10. hit 'p' key to put the selected text (actual result is no change;
> expected that editor would put 'now is the time' in the document)
>
> Thanks again for your help,
>
> Tom Arnall
>
>
>
> On 7/22/18, Tony Mechelynck <antoine.mechelynck@gmail.com> wrote:
>> On Mon, Jul 23, 2018 at 3:40 AM, tom arnall <kloro2006@gmail.com> wrote:
>>> i can't get yank or put to map to a kb shortcut in visual mode. i'm
>>> running debian stretch.
>>
>> This problem description is so vague that I can't even begin to try to
>> reproduce it. Please include the following:
>>
>> 1. Which Vim version, patchlevel, and featureset? (Please paste the
>> first lines of the output of the :version command, up to and including
>> the one which ends in "Features included (+) or not (-)"). How to get
>> that into a file or into the clipboard is explained at ":help :redir".
>>
>> 2. Please describe in detail what you do (as a "recipe": 1. do this,
>> 2. do that) using clear and simple language, so that even someone only
>> half-proficient in English can understand it.
>>
>> 3. At the end, or after the important steps of the procedure at 2
>> above, please say what you see ("Actual result") and what you expected
>> ("Expected result").
>>
>> Best regards,
>> Tony.
>>
>> --
>> --
>> You received this message from the "vim_use" maillist.
>> Do not top-post! Type your reply below the text you are replying to.
>> For more information, visit http://www.vim.org/maillist.php
>>
>> ---
>> You received this message because you are subscribed to the Google Groups
>> "vim_use" group.
>> To unsubscribe from this group and stop receiving emails from it, send an
>> email to vim_use+unsubscribe@googlegroups.com.
>> For more options, visit https://groups.google.com/d/optout.
>>
>
> --
> --
> You received this message from the "vim_use" maillist.
> Do not top-post! Type your reply below the text you are replying to.
> For more information, visit http://www.vim.org/maillist.php
>
> ---
> You received this message because you are subscribed to the Google Groups "vim_use" group.
> To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.

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

---
You received this message because you are subscribed to the Google Groups "vim_use" group.
To unsubscribe from this group and 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: yank and put not vmapping in debian stretch

Tony,

Here is (I hope) the presentation which you have requested.

Here is output of 'version':

:version
VIM - Vi IMproved 8.0 (2016 Sep 12, compiled Sep 30 2017 18:21:38)
Included patches: 1-197, 322, 377-378, 550, 703, 706-707
Modified by pkg-vim-maintainers@lists.alioth.debian.org
Compiled by pkg-vim-maintainers@lists.alioth.debian.org
Huge version without GUI. Features included (+) or not (-):

Here is my procedure for mapping "+y:

1. enter ':vmap <c-i> "+y<cr>' (to map the visual mode yank)

2. in blank screen, hit 'i' key (for insert mode)

3. enter 'now is the time<cr>'.

4. hit <esc> key

5. hit 'v' key (for visual mode)

6. hit 'k' key to select the text

7. do <c-i> ( actual result is that editor stays in visual mode;
expected that it would return to normal mode)

8. hit 'v' key to exit visual mode

9. hit 'j' key to move to next line

10. hit 'p' key to put the selected text (actual result is no change;
expected that editor would put 'now is the time' in the document)

Thanks again for your help,

Tom Arnall



On 7/22/18, Tony Mechelynck <antoine.mechelynck@gmail.com> wrote:
> On Mon, Jul 23, 2018 at 3:40 AM, tom arnall <kloro2006@gmail.com> wrote:
>> i can't get yank or put to map to a kb shortcut in visual mode. i'm
>> running debian stretch.
>
> This problem description is so vague that I can't even begin to try to
> reproduce it. Please include the following:
>
> 1. Which Vim version, patchlevel, and featureset? (Please paste the
> first lines of the output of the :version command, up to and including
> the one which ends in "Features included (+) or not (-)"). How to get
> that into a file or into the clipboard is explained at ":help :redir".
>
> 2. Please describe in detail what you do (as a "recipe": 1. do this,
> 2. do that) using clear and simple language, so that even someone only
> half-proficient in English can understand it.
>
> 3. At the end, or after the important steps of the procedure at 2
> above, please say what you see ("Actual result") and what you expected
> ("Expected result").
>
> Best regards,
> Tony.
>
> --
> --
> You received this message from the "vim_use" maillist.
> Do not top-post! Type your reply below the text you are replying to.
> For more information, visit http://www.vim.org/maillist.php
>
> ---
> You received this message because you are subscribed to the Google Groups
> "vim_use" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to vim_use+unsubscribe@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>

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

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

font specifiers and options on Windows version of vim

I'm running a native version of Vim on windows and had some
questions regarding the font dialog

It shows 3 list boxes at the top: Font: Font stye: and Size.
On the 2nd "row" there is a Sample box.
and on a 3rd row, there is a 1-line list box, "Script:" with
the only options being: Western, Greek, Turkish, Baltic, Central
European Cyrillic.

toward the bottom there is a blue link
"Show more fonts"
followed by (Ok) and (Cancel)

Maybe 1st question is how can I select script 'Unicode' or UTF-8?

Second question is -- if I click on "Show more fonts", how do enter
one of those fonts into the font dialogue or how do I use one of
those fonts in vim?

Third question... if I select a font via the Edit->Fonts menu,
like "Ubuntu Mono", it translates it into
Ubunto_Mono:h11:cANSI:qDRAFT

I get that it is using underscore instead of the more
literal "Ubuntu\ Mono", h11 has something to do with the
height, and q has something to do with the rendering quality,
but where does it get the cANSI? When I look at the vim
options, I see encoding and file-encoding both set to utf-8.
But where does ANSI come in? I don't remember that even
being a windows codepage. I don't see anyplace that explains
what these are. The win32_gui certainly seems to support
UTF-8 these days...so how do I get that?

I guess that's enough questions for this email -- hopefully not
too many. Thanks!

Linda

version:
VIM - Vi IMproved 8.0 (2016 Sep 12, compiled Sep 20 2016 22:02:37)
MS-Windows 64-bit GUI version with OLE support
Included patches: 1-6
Compiled by appveyor@APPVYR-WIN
Huge version with GUI. Features included (+) or not (-):
+acl +eval +mouse +syntax
+arabic +ex_extra +mouseshape +tag_binary
+autocmd +extra_search +multi_byte_ime/dyn +tag_old_static
+balloon_eval +farsi +multi_lang -tag_any_white
+browse +file_in_path +mzscheme/dyn +tcl/dyn
++builtin_terms +find_in_path +netbeans_intg -termguicolors
+byte_offset +float +num64 -tgetent
+channel +folding +ole -termresponse
+cindent -footer +packages +textobjects
+clientserver +gettext/dyn +path_extra +timers
+clipboard -hangul_input +perl/dyn +title
+cmdline_compl +iconv/dyn +persistent_undo +toolbar
+cmdline_hist +insert_expand -postscript +user_commands
+cmdline_info +job +printer +vertsplit
+comments +jumplist +profile +virtualedit
+conceal +keymap +python/dyn +visual
+cryptv +lambda +python3/dyn +visualextra
+cscope +langmap +quickfix +viminfo
+cursorbind +libcall +reltime +vreplace
+cursorshape +linebreak +rightleft +wildignore
+dialog_con_gui +lispindent +ruby/dyn +wildmenu
+diff +listcmds +scrollbind +windows
+digraphs +localmap +signs +writebackup
+directx +lua/dyn +smartindent -xfontset
-dnd +menu +startuptime -xim
-ebcdic +mksession +statusline +xpm_w32
+emacs_tags +modify_fname -sun_workshop -xterm_save
system vimrc file: "$VIM\vimrc"
user vimrc file: "$HOME\.vimrc"
2nd user vimrc file: "$HOME\vimfiles\vimrc"
3rd user vimrc file: "$VIM\.vimrc"
user exrc file: "$HOME\.exrc"
2nd user exrc file: "$VIM\.exrc"
system gvimrc file: "$VIM\gvimrc"
user gvimrc file: "$HOME\.gvimrc"
2nd user gvimrc file: "$HOME\vimfiles\gvimrc"
3rd user gvimrc file: "$VIM\.gvimrc"
defaults file: "$VIMRUNTIME\defaults.vim"
system menu file: "$VIMRUNTIME\menu.vim"
Compilation: cl -c /W3 /nologo -I. -Iproto -DHAVE_PATHDEF -DWIN32
-DFEAT_CSCOPE -DFEAT_NETBEANS_INTG -DFEAT_JOB_CHANNEL -DFEAT_XPM_W32
-DWINVER=0x500 -D_WIN32_WINNT=0x500 /Fo.\ObjGXOULYHTRZAMD64/
-DHAVE_STDINT_H /Ox /GL -DNDEBUG /Zl /MT -DFEAT_OLE -DFEAT_MBYTE_IME
-DDYNAMIC_IME -DFEAT_MBYTE -DFEAT_GUI_W32 -DFEAT_DIRECTX
-DDYNAMIC_DIRECTX -DDYNAMIC_ICONV -DDYNAMIC_GETTEXT -DFEAT_TCL
-DDYNAMIC_TCL -DDYNAMIC_TCL_DLL=\"tcl86.dll\" -DDYNAMIC_TCL_VER=\"8.6\"
-DFEAT_LUA -DDYNAMIC_LUA -DDYNAMIC_LUA_DLL=\"lua53.dll\" -DFEAT_PYTHON
-DDYNAMIC_PYTHON -DDYNAMIC_PYTHON_DLL=\"python27.dll\" -DFEAT_PYTHON3
-DDYNAMIC_PYTHON3-DDYNAMIC_PYTHON3_DLL=\"python35.dll\" -DFEAT_MZSCHEME
-I "C:\Program Files\Racket\include" -DMZ_PRECISE_GC -DDYNAMIC_MZSCHEME
-DDYNAMIC_MZSCH_DLL=\"libracket3m_a0solc.dll\"
-DDYNAMIC_MZGC_DLL=\"libracket3m_a0solc.dll\" -DFEAT_PERL
-DPERL_IMPLICIT_CONTEXT -DPERL_IMPLICIT_SYS -DDYNAMIC_PERL
-DDYNAMIC_PERL_DLL=\"perl524.dll\" -DFEAT_RUBY -DDYNAMIC_RUBY
-DDYNAMIC_RUBY_VER=22 -DDYNAMIC_RUBY_DLL=\"x64-msvcrt-ruby220.d
ll\" -DFEAT_HUGE /Fd.\ObjGXOULYHTRZAMD64/ /Zi Linking: link /RELEASE
/nologo /subsystem:windows /LTCG:STATUS oldnames.lib kernel32.lib
advapi32.lib shell32.lib gdi32.lib comdlg32.lib ole32.lib uuid.lib
/machine:AMD64 gdi32.lib version.lib winspool.lib comctl32.lib
advapi32.lib shell32.lib /machine:AMD64 /nodefaultlib libcmt.lib
oleaut32.lib user32.lib /nodefaultlib:lua53.lib /STACK:8388608
/nodefaultlib:python27.lib /nodefaultlib:python35.lib
"C:\Tcl\lib\tclstub86.lib" WSock32.lib xpm\x64\lib\libXpm.lib
/PDB:gvim.pdb -debug


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

---
You received this message because you are subscribed to the Google Groups "vim_use" group.
To unsubscribe from this group and 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: Why does it work to select text in visual mode and then type "d", but not when I do the same and type ":normal d" ?

Yes, you are correct. That makes sense. Thanks!

On Sun, Jul 22, 2018 at 1:44 PM, Tony Mechelynck
<antoine.mechelynck@gmail.com> wrote:
> On Sun, Jul 22, 2018 at 7:53 PM, Duane Knesek <duane.knesek@gmail.com> wrote:
>> I'm writing a script and it isn't working. I basically replaced the guts of my script with exec "normal d" to see if it did anything. It did not. So then I tried just typing it at the : prompt, and that also didn't work. Shouldn't that work? Or do I fundamentally misunderstand the normal command?
>
> What happens if you do «:normal gvd» instead?
>
> If that works, then it means that :normal goes to Normal mode,
> canceling Visual mode if set. («gv» restarts Visual mode with the
> latest Visual selection active.)
>
> Best regards,
> Tony.
>
> --
> --
> You received this message from the "vim_use" maillist.
> Do not top-post! Type your reply below the text you are replying to.
> For more information, visit http://www.vim.org/maillist.php
>
> ---
> You received this message because you are subscribed to the Google Groups "vim_use" group.
> To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.

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

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

Re: yank and put not vmapping in debian stretch

will do. thanks very much for your offer of help.

On 7/22/18, Tony Mechelynck <antoine.mechelynck@gmail.com> wrote:
> On Mon, Jul 23, 2018 at 3:40 AM, tom arnall <kloro2006@gmail.com> wrote:
>> i can't get yank or put to map to a kb shortcut in visual mode. i'm
>> running debian stretch.
>
> This problem description is so vague that I can't even begin to try to
> reproduce it. Please include the following:
>
> 1. Which Vim version, patchlevel, and featureset? (Please paste the
> first lines of the output of the :version command, up to and including
> the one which ends in "Features included (+) or not (-)"). How to get
> that into a file or into the clipboard is explained at ":help :redir".
>
> 2. Please describe in detail what you do (as a "recipe": 1. do this,
> 2. do that) using clear and simple language, so that even someone only
> half-proficient in English can understand it.
>
> 3. At the end, or after the important steps of the procedure at 2
> above, please say what you see ("Actual result") and what you expected
> ("Expected result").
>
> Best regards,
> Tony.
>
> --
> --
> You received this message from the "vim_use" maillist.
> Do not top-post! Type your reply below the text you are replying to.
> For more information, visit http://www.vim.org/maillist.php
>
> ---
> You received this message because you are subscribed to the Google Groups
> "vim_use" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to vim_use+unsubscribe@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>

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

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

Re: yank and put not vmapping in debian stretch

On Mon, Jul 23, 2018 at 3:40 AM, tom arnall <kloro2006@gmail.com> wrote:
> i can't get yank or put to map to a kb shortcut in visual mode. i'm
> running debian stretch.

This problem description is so vague that I can't even begin to try to
reproduce it. Please include the following:

1. Which Vim version, patchlevel, and featureset? (Please paste the
first lines of the output of the :version command, up to and including
the one which ends in "Features included (+) or not (-)"). How to get
that into a file or into the clipboard is explained at ":help :redir".

2. Please describe in detail what you do (as a "recipe": 1. do this,
2. do that) using clear and simple language, so that even someone only
half-proficient in English can understand it.

3. At the end, or after the important steps of the procedure at 2
above, please say what you see ("Actual result") and what you expected
("Expected result").

Best regards,
Tony.

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

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

yank and put not vmapping in debian stretch

i can't get yank or put to map to a kb shortcut in visual mode. i'm
running debian stretch.

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

---
You received this message because you are subscribed to the Google Groups "vim_use" group.
To unsubscribe from this group and 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: Why does it work to select text in visual mode and then type "d", but not when I do the same and type ":normal d" ?

On Sun, Jul 22, 2018 at 7:53 PM, Duane Knesek <duane.knesek@gmail.com> wrote:
> I'm writing a script and it isn't working. I basically replaced the guts of my script with exec "normal d" to see if it did anything. It did not. So then I tried just typing it at the : prompt, and that also didn't work. Shouldn't that work? Or do I fundamentally misunderstand the normal command?

What happens if you do «:normal gvd» instead?

If that works, then it means that :normal goes to Normal mode,
canceling Visual mode if set. («gv» restarts Visual mode with the
latest Visual selection active.)

Best regards,
Tony.

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

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

Why does it work to select text in visual mode and then type "d", but not when I do the same and type ":normal d" ?

I'm writing a script and it isn't working. I basically replaced the guts of my script with exec "normal d" to see if it did anything. It did not. So then I tried just typing it at the : prompt, and that also didn't work. Shouldn't that work? Or do I fundamentally misunderstand the normal command?

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

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

can't get vmap to work

here it is:

:vmap <c-i> "+y

then when i do <c-i> nothing happens

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

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

Re: gvim8.1 on ubuntu

On Friday, July 20, 2018 at 11:48:12 PM UTC+12, Robert Solomon wrote:
> I cloned the github source and compiled vim 8.1. That went smoothly.
>
> How do I get gvim 8.1 on Ubuntu?

I'm not sure I understand your question, and I take it differently to Christian Brabandt.

If your newly built vim does not have a GUI, as shown by :ver, or vim --version, then configure didn't find the needed GUI headers and libraries, and

sudo apt-get build-dep vim-gtk

will get what you need, assuming your Ubuntu version is still in support. (14.04, 16.04, 17.10, 18.04). Then

make reconfig

will rerun configure, and it should find the GUI, these days that's the default.

If your :ver output shows a GUI (mine straight from git master says "Huge version with GTK2 GUI") then you have gvim; on *n?x the same executable is used for gvim. Run it with

vim -g

or use the :gui command to confirm this.

Either way,

sudo make install

makes /usr/local/bin/gvim a link to vim, to completely answer your question.

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.

Re: vim 8.1 on windows

The version of vim that is working fine for me, from the :version
command, is

8.0 (2016 Sep 12, compiled Sep 12 2016 18:17:48)

Included patches 1-2

compiled by mool@tororo

huge version without GUI

I am also getting those funny characters inserted when I hit F11 or F12
in vim 8.1

--rob



On 07/21/2018 09:07 AM, Christian Brabandt wrote:
> On Fr, 20 Jul 2018, JohnBeckett wrote:
>
>> On Friday, July 20, 2018 at 11:29:59 PM UTC+10, rob wrote:
>>> Main issue is with vim
>> What is it that tells you something is not working?
>> The question was "What exactly did you try?".
> There is something funny going on definitely. I tried in a cmd window.
> Running Vim --clean typing i to enter insert mode and pressing
> <f9> <f10> <f11> and <f12>
>
> This resulted in this:
> <F9><F10>΅Ά
>
> Not sure what is actually going. My codepage is cp850 and encoding is "latin1"
>
> I briefly played around with the 'termencoding' setting and compared the
> output of :set t_k; for the f10 key with :set t_F1 and t_F2 for <f11>
> and <f12>. They are set, but I don't know if they are set correctly and
> even when reseting e.g. t_k9=empty for <f9> it will still be detected
> correctly by Vim which leads me to believe that the terminal-key-codes
> are not actually used by vim. Also `:set <f11>=<c-v><f11>` did not work.
> So there might be a problem here.
>
> This was with Vim 8.0.1451 perhaps I need to update it and test again.
>
> 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: vim 8.1 on windows

On Fr, 20 Jul 2018, JohnBeckett wrote:

> On Friday, July 20, 2018 at 11:29:59 PM UTC+10, rob wrote:
> > Main issue is with vim
>
> What is it that tells you something is not working?
> The question was "What exactly did you try?".

There is something funny going on definitely. I tried in a cmd window.
Running Vim --clean typing i to enter insert mode and pressing
<f9> <f10> <f11> and <f12>

This resulted in this:
<F9><F10>΅Ά

Not sure what is actually going. My codepage is cp850 and encoding is "latin1"

I briefly played around with the 'termencoding' setting and compared the
output of :set t_k; for the f10 key with :set t_F1 and t_F2 for <f11>
and <f12>. They are set, but I don't know if they are set correctly and
even when reseting e.g. t_k9=empty for <f9> it will still be detected
correctly by Vim which leads me to believe that the terminal-key-codes
are not actually used by vim. Also `:set <f11>=<c-v><f11>` did not work.
So there might be a problem here.

This was with Vim 8.0.1451 perhaps I need to update it and test again.

Best,
Christian
--
Gewissen ist die innere Stimme, die uns warnt, daß jemand zuschauen
könnte.
-- Henry Louis Mencken

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

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