Rebbe Malachi: April 2014

Tuesday, April 29, 2014

Re: Completing functions with # in the name

On 4/28/14, Nikolay Pavlov <zyx.vim@gmail.com> wrote:
> On Apr 29, 2014 7:13 AM, "Vlad Irnov" <vlad.irnov@gmail.com> wrote:
>>
>> On 4/25/14, Nikolay Pavlov <zyx.vim@gmail.com> wrote:
>> > On Apr 25, 2014 11:21 AM, "Chris Allison" <
> chris.charles.allison@gmail.com>
>> > wrote:
>> >>
>> >> Hi skeept,
>> >>
>> >> what version are you using, as with my version it works as expected
>> >
>> > Try doing
>> >
>> > :set iskeyword&vim isident&vim
>> > before completing (this will reset iskeyword and isident options to the
>> > default for vim).
>> >
>> >>
>> >> :call unite# <TAB> will complete with functions that start unite# and
>> >> not at the beginning of the list as in your case.
>> >>
>>
>> I always had this problem. I assumed it was a bug. It can be annoying
>> when developing autoload functions.
>>
>> Doing
>> :set iskeyword&vim isident&vim
>> does not help.
>
> Check out what I replied to: it should not *help* it should make completion
> *no longer work* for a person who says it does work.

OK, I get it. But changing 'iskeyword' and/or 'isident' does not help
either. I tried
:set iskeyword+=# isident+=#
and even crazy
:set isk=1-255 isi=1-255 isf=1-255
without success. Still no command line completion for autoloaded
functions afer #, for example
:call netrw#E<Tab>

Best regards,
Vlad

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

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

Blogging on multiple blogs with vim?

-----BEGIN PGP SIGNATURE-----
Version: GnuPG/MacGPG2 v2.0.22 (Darwin)
Comment: GPGTools - http://gpgtools.org

iQIcBAEBAgAGBQJTX8FfAAoJEHWv8EScabi8tscP/j51G7R+6kCIRdeecYzxuH2Z
+XRdBCQo62/rKKJSm1vplAUllLpSR1IRncNOfVHxRJtVWfqBwXQkXtD6eVki/VqR
OmzNWKH267HwIx2BGPk0wz7SjghRhOAr5ZF1hYnSRZFOdip0IwQ5j8lu8iMRRQov
RjGsC7Ic4NesTv437ybw9aTVj5EJcccbsR83seISaGrYGwOl49pF1/rtz0b4mls2
8BKtGtuF7eDXSSmknolrVky36tRmcDGjGzvME/yKm+tOKLacr1Vy+83MS7OtNqsd
19ml0g7RLGcHtw0IVgPUjFDAwsY2meu8XZmbMTtAzi9GyFlaLzPyEg+N2cBz37UI
iZvwMfpGoyHViNeo7GohEYzVlW+3OjviwhhXkqW7zlypwBNyKIaTEqGF+vHW/4dg
wFXLdE6zDpxcaKmljS+8GoebkV5t73QO+QN8pdfDcYwnv7pXm7dOYTqhWJyxc1D1
kEaqR3n3MayByPg13jRsUT6eyRy/pDK+tYe7Wa/Z5BzyxzJ/EnnSzjXnJZme+n3k
wWgblxq3mZ+VwnS77Hg0boOeAaV+71Q56gIhU5oVcrNZpH2AaeIacvuHA8+YiCRz
+qOiidcIHFCVfkow8mDlUs/AbIvkdzPKFUgIw2xXNqgPd1sUEUOhxUxBt4V2T6c2
L6FUU32jlzWfDWWV9IhR
=6Ty4
-----END PGP SIGNATURE-----
Hi,

does anyone know if there is a blog-plugin out there for blogging with vim that supports having multiple wordpress-blogs?

Thanks,

Niels

Re: Opening large files?

Ken Takata wrote:

> 2014/4/17 Thu 0:58:01 UTC+9 Adrian wrote:
> > 'm helping another user open a large, 3Gb, file. The standard windows
> > editors balk, so I recommended VIM. Unfortunately, even vim crashes
> > after scrolling some amount. For instance, he can't go straight to
> > the end of file.
> >
> > The work station is Windows 7, 64 bit, with 32Gb of RAM. Are there
> > any settings to modify to make vim more stable with large files, or is
> > there some Windows performance limitation and just out of luck?
>
> There is a related item in the todo.txt:
>
> | Win64: Seek error in swap file for a very big file (3 Gbyte). Check storing
> | pointer in long and seek offset in 64 bit var.
>
> I wrote some patches to fix this, but they seem to be still unstable.
>
> https://bitbucket.org/k_takata/vim-ktakata-mq/src/192069dac4356c186b89e0451a254599713d2309/support-largefiles-on-windows.patch?at=default
> https://bitbucket.org/k_takata/vim-ktakata-mq/src/192069dac4356c186b89e0451a254599713d2309/use-stat_T.patch?at=default

Did you make progress on this?
Can we also add some tests to verify the fix?

--
From "know your smileys":
:-E Has major dental problems

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

Monday, April 28, 2014

Re: Compare files, save differences

On Mon 21 Apr 2014 at 02:28:20 PDT Christian Brabandt wrote:
>That is what external commands are good for. I would use comm(1)
>
>#v+
>/tmp/compare % comm -23 <(sort allwords.txt) <(sort mywords.txt)

That's probably the best solution if you're on Unix, Linux or OS X.

Not sure if comm(1) is available by default on Windows, however.
It's been a while since I've worked on one of those systems.
I'm pretty sure you can get comm(1) by installing Cygwin, the MKS Toolkit,
or Microsoft's Subsystem for Unix-based Applications (SUA).
But if this is the only Unix-like task the OP needs done,
it might not be worth the trouble.

In general, whenever possible I prefer to use external commands
rather than plugins. If I wanted my editor to do everything itself,
I'd be using emacs. ;)

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

---
You received this message because you are subscribed to the Google Groups "vim_use" group.
To unsubscribe from this group and 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: Completing functions with # in the name

On Apr 29, 2014 7:13 AM, "Vlad Irnov" <vlad.irnov@gmail.com> wrote:
>
> On 4/25/14, Nikolay Pavlov <zyx.vim@gmail.com> wrote:
> > On Apr 25, 2014 11:21 AM, "Chris Allison" <chris.charles.allison@gmail.com>
> > wrote:
> >>
> >> Hi skeept,
> >>
> >> what version are you using, as with my version it works as expected
> >
> > Try doing
> >
> > :set iskeyword&vim isident&vim
> > before completing (this will reset iskeyword and isident options to the
> > default for vim).
> >
> >>
> >> :call unite# <TAB> will complete with functions that start unite# and
> >> not at the beginning of the list as in your case.
> >>
>
> I always had this problem. I assumed it was a bug. It can be annoying
> when developing autoload functions.
>
> Doing
> :set iskeyword&vim isident&vim
> does not help.

Check out what I replied to: it should not *help* it should make completion *no longer work* for a person who says it does work.

>
> This can be tested with any autoload plugin, such as netrw. First
> activate it with :Exp or :Sexp.
> When I do
> :call netrw<TAB>
> I get a bunch of functions as expected, first one is netrw#ErrorMsg().
> But completion fails afer typing #. This finds nothing:
> :call netrw#E<TAB>
>
> Currently using Vim 7.4.179, Windows.
>
> Possibly related issue on the todo list:
> If the variable "g:x#y#z" exists completion after ":echo g:x#" doesn't work.
>
> Best regards,
> Vlad
>
> --
> --
> You received this message from the "vim_use" maillist.
> Do not top-post! Type your reply below the text you are replying to.
> For more information, visit http://www.vim.org/maillist.php
>
> ---
> You received this message because you are subscribed to the Google Groups "vim_use" group.
> To unsubscribe from this group and 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: Completing functions with # in the name

On 4/25/14, Nikolay Pavlov <zyx.vim@gmail.com> wrote:
> On Apr 25, 2014 11:21 AM, "Chris Allison" <chris.charles.allison@gmail.com>
> wrote:
>>
>> Hi skeept,
>>
>> what version are you using, as with my version it works as expected
>
> Try doing
>
> :set iskeyword&vim isident&vim
> before completing (this will reset iskeyword and isident options to the
> default for vim).
>
>>
>> :call unite# <TAB> will complete with functions that start unite# and
>> not at the beginning of the list as in your case.
>>

I always had this problem. I assumed it was a bug. It can be annoying
when developing autoload functions.

Doing
:set iskeyword&vim isident&vim
does not help.

This can be tested with any autoload plugin, such as netrw. First
activate it with :Exp or :Sexp.
When I do
:call netrw<TAB>
I get a bunch of functions as expected, first one is netrw#ErrorMsg().
But completion fails afer typing #. This finds nothing:
:call netrw#E<TAB>

Currently using Vim 7.4.179, Windows.

Possibly related issue on the todo list:
If the variable "g:x#y#z" exists completion after ":echo g:x#" doesn't work.

Best regards,
Vlad

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

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

Re: Compare files, save differences

On Sat, Apr 26, 2014 at 10:05 AM, Jeri Raye <jeri.raye@gmail.com> wrote:

Hi David,

I've installed it, and open the two files:
When I do trough the GUI or with :WhatsMissing I get the error
WM: cannot search other buffers with :set nohidden

How do I solve that?

:set hidden

:WhatsMissing

David

Re: Do you use status line plugins like powerline or airline?

On Apr 27, 2014 1:58 PM, "Pritesh Ugrankar" <pritesh.ugrankar@gmail.com> wrote:
>
> Hi,
>
> Try the lightline plugin. I use it on win and Linux and it works great. No need to install patched fonts.

You do not need to do this with powerline and airline as well. Though powerline is harder to configure to not use custom glyphs.

>
> --
> --
> You received this message from the "vim_use" maillist.
> Do not top-post! Type your reply below the text you are replying to.
> For more information, visit http://www.vim.org/maillist.php
>
> ---
> You received this message because you are subscribed to the Google Groups "vim_use" group.
> To unsubscribe from this group and 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: libcall E364

On Sunday, April 27, 2014 11:40:59 AM UTC+1, Yukihiro Nakadaira wrote:
> On Sun, Apr 27, 2014 at 7:24 PM, Ni Va <niva...@gmail.com> wrote:
>
> On Sunday, April 27, 2014 11:19:25 AM UTC+1, Yukihiro Nakadaira wrote:
>
>
>
> > On Sun, Apr 27, 2014 at 7:07 PM, Ni Va <niva...@gmail.com> wrote:
>
> >
>
> > On Sunday, April 27, 2014 10:52:25 AM UTC+1, Yukihiro Nakadaira wrote:
>
> >
>
> >
>
> >
>
> > > On Sun, Apr 27, 2014 at 6:10 PM, Ni Va <niva...@gmail.com> wrote:
>
> >
>
> > >
>
> >
>
> > >
>
> >
>
> > > On Friday, April 25, 2014 10:04:57 AM UTC+1, Ni Va wrote:
>
> >
>
> > >
>
> >
>
> > > > Hi,
>
> >
>
> > >
>
> >
>
> > > >
>
> >
>
> > >
>
> >
>
> > > >
>
> >
>
> > >
>
> >
>
> > > > I compiled a dlltest.dll under windows 64bits that fails at vim libcall.
>
> >
>
> > >
>
> >
>
> > > >
>
> >
>
> > >
>
> >
>
> > > > _____________source code____________
>
> >
>
> > >
>
> >
>
> > > > .h
>
> >
>
> > >
>
> >
>
> > > > extern "C" __declspec(dllexport) int decrease(long a);
>
> >
>
> > >
>
> >
>
> > > >
>
> >
>
> > >
>
> >
>
> > > > .cpp
>
> >
>
> > >
>
> >
>
> > > > extern "C" __declspec(dllexport)
>
> >
>
> > >
>
> >
>
> > > > int decrease(long a)
>
> >
>
> > >
>
> >
>
> > > > {
>
> >
>
> > >
>
> >
>
> > > > return (a-1);
>
> >
>
> > >
>
> >
>
> > > > }
>
> >
>
> > >
>
> >
>
> > > > ___end____of______source code____________
>
> >
>
> > >
>
> >
>
> > > >
>
> >
>
> > >
>
> >
>
> > > >
>
> >
>
> > >
>
> >
>
> > > >
>
> >
>
> > >
>
> >
>
> > > > :echo libcallnr('dlltest', 'Decrease', 5)
>
> >
>
> > >
>
> >
>
> > > > E364: Library call failed for "Decrase()"
>
> >
>
> > >
>
> >
>
> > > >
>
> >
>
> > >
>
> >
>
> > > >
>
> >
>
> > >
>
> >
>
> > > > dlltest.dll is under vim74 directory with gvim.exe.
>
> >
>
> > >
>
> >
>
> > >
>
> >
>
> > >
>
> >
>
> > > Any help?
>
> >
>
> > >
>
> >
>
> > >
>
> >
>
> > > Maybe typo? 'Decrease' -> 'decrease'
>
> >
>
> > > Or try dll full path.
>
> >
>
> > >
>
> >
>
> > > --
>
> >
>
> > > Yukihiro Nakadaira - yukihiro....@gmail.com
>
> >
>
> >
>
> >
>
> > Hi Yukihiro,
>
> >
>
> >
>
> >
>
> > Already both tried. Can I send you files ?
>
> >
>
> >
>
> > I don't have 64bit Windows PC.
>
> >
>
> > gvim.exe and dlltest.dll are both 64bit version?
>
> >
>
> > --
>
> > Yukihiro Nakadaira - yukihiro....@gmail.com
>
>
>
>
>
> gVim 64bits
>
> dll is 32bits compiled
>
>
>
> I think 64bit dll will work.
>
> --
> Yukihiro Nakadaira - yukihiro....@gmail.com

Yes,

I confirm that gvim32bits call my dll which was compiled for 32bits only
Then, as I have got two versions of gvim in 32bits and 64bits, I think I will have to link my dll for both plateforms.

Thank you

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

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

Re: libcall E364

On Sun, Apr 27, 2014 at 7:24 PM, Ni Va <nivaemail@gmail.com> wrote:

On Sunday, April 27, 2014 11:19:25 AM UTC+1, Yukihiro Nakadaira wrote:

> On Sun, Apr 27, 2014 at 7:07 PM, Ni Va <niva...@gmail.com> wrote:
>
> On Sunday, April 27, 2014 10:52:25 AM UTC+1, Yukihiro Nakadaira wrote:
>
>
>
> > On Sun, Apr 27, 2014 at 6:10 PM, Ni Va <niva...@gmail.com> wrote:
>
> >
>
> >
>
> > On Friday, April 25, 2014 10:04:57 AM UTC+1, Ni Va wrote:
>
> >
>
> > > Hi,
>
> >
>
> > >
>
> >
>
> > >
>
> >
>
> > > I compiled a dlltest.dll under windows 64bits that fails at vim libcall.
>
> >
>
> > >
>
> >
>
> > > _____________source code____________
>
> >
>
> > > .h
>
> >
>
> > > extern "C" __declspec(dllexport) int decrease(long a);
>
> >
>
> > >
>
> >
>
> > > .cpp
>
> >
>
> > > extern "C" __declspec(dllexport)
>
> >
>
> > > int decrease(long a)
>
> >
>
> > > {
>
> >
>
> > > return (a-1);
>
> >
>
> > > }
>
> >
>
> > > ___end____of______source code____________
>
> >
>
> > >
>
> >
>
> > >
>
> >
>
> > >
>
> >
>
> > > :echo libcallnr('dlltest', 'Decrease', 5)
>
> >
>
> > > E364: Library call failed for "Decrase()"
>
> >
>
> > >
>
> >
>
> > >
>
> >
>
> > > dlltest.dll is under vim74 directory with gvim.exe.
>
> >
>
> >
>
> >
>
> > Any help?
>
> >
>
> >
>
> > Maybe typo? 'Decrease' -> 'decrease'
>
> > Or try dll full path.
>
> >
>
> > --
>
> > Yukihiro Nakadaira - yukihiro....@gmail.com
>
>
>
> Hi Yukihiro,
>
>
>
> Already both tried. Can I send you files ?
>
>
> I don't have 64bit Windows PC.
>
> gvim.exe and dlltest.dll are both 64bit version?
>
> --

> Yukihiro Nakadaira - yukihiro....@gmail.com

gVim 64bits
dll is 32bits compiled

I think 64bit dll will work.

--
Yukihiro Nakadaira - yukihiro.nakadaira@gmail.com

Re: libcall E364

On Sunday, April 27, 2014 11:19:25 AM UTC+1, Yukihiro Nakadaira wrote:
> On Sun, Apr 27, 2014 at 7:07 PM, Ni Va <niva...@gmail.com> wrote:
>
> On Sunday, April 27, 2014 10:52:25 AM UTC+1, Yukihiro Nakadaira wrote:
>
>
>
> > On Sun, Apr 27, 2014 at 6:10 PM, Ni Va <niva...@gmail.com> wrote:
>
> >
>
> >
>
> > On Friday, April 25, 2014 10:04:57 AM UTC+1, Ni Va wrote:
>
> >
>
> > > Hi,
>
> >
>
> > >
>
> >
>
> > >
>
> >
>
> > > I compiled a dlltest.dll under windows 64bits that fails at vim libcall.
>
> >
>
> > >
>
> >
>
> > > _____________source code____________
>
> >
>
> > > .h
>
> >
>
> > > extern "C" __declspec(dllexport) int decrease(long a);
>
> >
>
> > >
>
> >
>
> > > .cpp
>
> >
>
> > > extern "C" __declspec(dllexport)
>
> >
>
> > > int decrease(long a)
>
> >
>
> > > {
>
> >
>
> > > return (a-1);
>
> >
>
> > > }
>
> >
>
> > > ___end____of______source code____________
>
> >
>
> > >
>
> >
>
> > >
>
> >
>
> > >
>
> >
>
> > > :echo libcallnr('dlltest', 'Decrease', 5)
>
> >
>
> > > E364: Library call failed for "Decrase()"
>
> >
>
> > >
>
> >
>
> > >
>
> >
>
> > > dlltest.dll is under vim74 directory with gvim.exe.
>
> >
>
> >
>
> >
>
> > Any help?
>
> >
>
> >
>
> > Maybe typo? 'Decrease' -> 'decrease'
>
> > Or try dll full path.
>
> >
>
> > --
>
> > Yukihiro Nakadaira - yukihiro....@gmail.com
>
>
>
> Hi Yukihiro,
>
>
>
> Already both tried. Can I send you files ?
>
>
> I don't have 64bit Windows PC.
>
> gvim.exe and dlltest.dll are both 64bit version?
>
> --
> Yukihiro Nakadaira - yukihiro....@gmail.com

gVim 64bits
dll is 32bits compiled

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

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

On Sun, Apr 27, 2014 at 7:07 PM, Ni Va <nivaemail@gmail.com> wrote:

On Sunday, April 27, 2014 10:52:25 AM UTC+1, Yukihiro Nakadaira wrote:

> On Sun, Apr 27, 2014 at 6:10 PM, Ni Va <niva...@gmail.com> wrote:
>
>
> On Friday, April 25, 2014 10:04:57 AM UTC+1, Ni Va wrote:
>
> > Hi,
>
> >
>
> >
>
> > I compiled a dlltest.dll under windows 64bits that fails at vim libcall.
>
> >
>
> > _____________source code____________
>
> > .h
>
> > extern "C" __declspec(dllexport) int decrease(long a);
>
> >
>
> > .cpp
>
> > extern "C" __declspec(dllexport)
>
> > int decrease(long a)
>
> > {
>
> > return (a-1);
>
> > }
>
> > ___end____of______source code____________
>
> >
>
> >
>
> >
>
> > :echo libcallnr('dlltest', 'Decrease', 5)
>
> > E364: Library call failed for "Decrase()"
>
> >
>
> >
>
> > dlltest.dll is under vim74 directory with gvim.exe.
>
>
>
> Any help?
>
>
> Maybe typo? 'Decrease' -> 'decrease'
> Or try dll full path.
>
> --

> Yukihiro Nakadaira - yukihiro....@gmail.com

Hi Yukihiro,

Already both tried. Can I send you files ?

I don't have 64bit Windows PC.

gvim.exe and dlltest.dll are both 64bit version?

--
Yukihiro Nakadaira - yukihiro.nakadaira@gmail.com

Re: libcall E364

On Sunday, April 27, 2014 10:52:25 AM UTC+1, Yukihiro Nakadaira wrote:
> On Sun, Apr 27, 2014 at 6:10 PM, Ni Va <niva...@gmail.com> wrote:
>
>
> On Friday, April 25, 2014 10:04:57 AM UTC+1, Ni Va wrote:
>
> > Hi,
>
> >
>
> >
>
> > I compiled a dlltest.dll under windows 64bits that fails at vim libcall.
>
> >
>
> > _____________source code____________
>
> > .h
>
> > extern "C" __declspec(dllexport) int decrease(long a);
>
> >
>
> > .cpp
>
> > extern "C" __declspec(dllexport)
>
> > int decrease(long a)
>
> > {
>
> > return (a-1);
>
> > }
>
> > ___end____of______source code____________
>
> >
>
> >
>
> >
>
> > :echo libcallnr('dlltest', 'Decrease', 5)
>
> > E364: Library call failed for "Decrase()"
>
> >
>
> >
>
> > dlltest.dll is under vim74 directory with gvim.exe.
>
>
>
> Any help?
>
>
> Maybe typo? 'Decrease' -> 'decrease'
> Or try dll full path.
>
> --
> Yukihiro Nakadaira - yukihiro....@gmail.com

Hi Yukihiro,

Already both tried. Can I send you files ?

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

---
You received this message because you are subscribed to the Google Groups "vim_use" group.
To unsubscribe from this group and 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: Do you use status line plugins like powerline or airline?

Hi,

Try the lightline plugin. I use it on win and Linux and it works great. No need to install patched fonts.

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

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

On Sun, Apr 27, 2014 at 6:10 PM, Ni Va <nivaemail@gmail.com> wrote:

On Friday, April 25, 2014 10:04:57 AM UTC+1, Ni Va wrote:
> Hi,
>
>
> I compiled a dlltest.dll under windows 64bits that fails at vim libcall.
>
> _____________source code____________
> .h
> extern "C" __declspec(dllexport) int decrease(long a);
>
> .cpp
> extern "C" __declspec(dllexport)
> int decrease(long a)
> {
> return (a-1);
> }
> ___end____of______source code____________
>
>
>
> :echo libcallnr('dlltest', 'Decrease', 5)
> E364: Library call failed for "Decrase()"
>
>
> dlltest.dll is under vim74 directory with gvim.exe.

Any help?

Maybe typo? 'Decrease' -> 'decrease'
Or try dll full path.

--
Yukihiro Nakadaira - yukihiro.nakadaira@gmail.com

Re: libcall E364

On Friday, April 25, 2014 10:04:57 AM UTC+1, Ni Va wrote:
> Hi,
>
>
> I compiled a dlltest.dll under windows 64bits that fails at vim libcall.
>
> _____________source code____________
> .h
> extern "C" __declspec(dllexport) int decrease(long a);
>
> .cpp
> extern "C" __declspec(dllexport)
> int decrease(long a)
> {
> return (a-1);
> }
> ___end____of______source code____________
>
>
>
> :echo libcallnr('dlltest', 'Decrease', 5)
> E364: Library call failed for "Decrase()"
>
>
> dlltest.dll is under vim74 directory with gvim.exe.

Any 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: vim fold: how to avoid the "+--" marks

On Apr 27, 2014 6:30 AM, "ping song" <songpingemail@gmail.com> wrote:
>
> experts:
>
> a question about vim fold:
>
> I can fold these:
>
> a
> b
> c
> d
> e
>
> into :
>
> a
> b
> +-- 2 lines: c
> e
>
> I just wonder, how to avoid displaying the "+--", and just leave it as:
>
> a
> b
> 2 lines: c
> e
>
> sometime this looks "cleaner" for me... especially if I need to refer the folded text in other docs...
>
> any idea?

Check out :h 'foldtext'.

> --
> --
> You received this message from the "vim_use" maillist.
> Do not top-post! Type your reply below the text you are replying to.
> For more information, visit http://www.vim.org/maillist.php
>
> ---
> You received this message because you are subscribed to the Google Groups "vim_use" group.
> To unsubscribe from this group and 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: S&R with search input from a file

Hi Ti,

I've removed the mapping that was misusing the default vim <C-R> behaviour.

I've reworked your code to the function below.

When I now do:

:call SRT_CorrectNames()

- I see my input list transformed to a joined line with \| between the words

- I see that I move to my file where I want to do substitution.
- I now get an error on the substitute

E486: pattern not found : \c\<$<C-R>0$\>

Any idea why pattern isn't found?

function! SRT_CorrectNames()
:sp input.txt
:%s/$/\\|/
:%j!
":s/..$
execute "normal! \<end>xx"

"0y$
        let @0 = getline(1)
        di 0

"
:wincmd w
%s/\c\<$<C-R>0$\>/\u&/g
"                   " substitute across the entire file (":%s/")
"                   " ignoring case ("\c")
"                   " a word must start here to match ("\<")
"                   " start the list of alternatives ("$")
"                   " use control+R followed by zero
"                   "    to include the word-list joined by \|
"                   "    that we yanked previously
"                   " close the list of alternatives ("$")
"                   " ensure that the word ends here ("\>")
"                   " and replace it with ("/")
"                   " the next letter uppercased ("\u")
"                   " the text we captured ("&")
"                   " and do all replacements on the line ("/g")
"
"This assumes that your input list is all just whole words, no funky
"regexp metachars (periods, backslashes, asterisks, or
"open-square-brackets come to mind).endfunction
endfunction

Rgds,
Jeri

On Wed, Apr 23, 2014 at 7:58 PM, Jeri Raye <jeri.raye@gmail.com> wrote:

Hi Tim,

I'm trying to make a function out of your commands.
Perhaps that that is the reason why it's not working straight away.

Rgds, Jeri

On Mon, Apr 21, 2014 at 4:42 PM, Tim Chase <vim@tim.thechases.com> wrote:

On 2014-04-21 08:37, Jeri Raye wrote:
> :s/..$
> doesn't work at my windows system
> I use:
> execute "normal! \<end>xx"

This should work on all versions of vim, regardless of operating
system. How are you determining that it isn't working? Is it giving
you an error? Is it not removing the last two characters (the "\|")
from the line? If you are having a problem, you could tweak the
first couple steps to

:1,$-s/$/\\|/

which will tack them onto every line *except* the last one, saving
you that ":s/..$/" step.

> Then it fails on
> 0y$
>
> I get the error message E488: Trailing characters

This sounds like you're trying to do this in some mode that isn't
normal-mode. Perhaps command-mode?

You could yank the entire line and then just remove the newline at
the end if that's easier.

> I also noticed that the <C-R> mapping in the last substitute
> command is already used in another plugin.
> Is there a workaround for?

You mean...other than not remapping away something that is incredibly
valuable? ;-) You can always map something else to it:

:cnoremap <f4> <c-r>

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

Problem with gvim, latexsuite and japanese input

Hello all,

I have encounter a serious bug which prevents me from using gvim to edit
latexfile in japanese. (I am a beginner with latexsuite so I still need
the menu to learn the shortcuts for latex elements).

Steps to reproduce the bug :

Use a linux box with ibus and mozc set up.
Launch gvim on a file with *.tex suffix.
start Japanese input. Anytime you press enter should transfer the
characters currently typed in the gvim buffer. This not the case. No
character is ever transfered. The following warning appears :
** (gvim:22533): WARNING **: Invalid change to preedit string, first=0
length=1 (orig length == 0)

Typing Japanese with a file ending in *txt in vim or gvim is OK.
Typing Japanese in a file ending in *tex in vim is mostly OK.

Where can I report this bug ?

Best regards,

Alain

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

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

Re: Possible to auto add / to end of line when vim reaches textwidth and does a new line?

>> When I'm writing shell scripts I tend to have textwidth at around 72
>>
>> characters. Is there a way that vim can auto add a \ at the end of the
>>
>> line when it starts a new line?
>>
>
>I think you can use the 'formatexpr' option for this. You'll need to write a function to do your formatting for you, including breaking the line and adding the '\'.

Well, I've almost got something to work, but it behaves in a
strange way. I set it to split at 10 characters for testing:

set formatexpr=EndLine()

fun EndLine()
let c = col(".")

if c == 10
exec "normal Bh"
exec "normal i \\\<CR>"
exec "normal $A"
return
endif
endfun

When I type a long line it swaps the last 2 letters for some reason
that I can't figure out. 'acdefghij' changes to 'abcdefghji'.

Also, if I use '> 10' rather than '== 10' it spits out about 100 lines
of '\', as if the cursor position hasn't updated. I tried using
setpos() but that had no effect.

I expect there are much better ways of doing this so if anyone has any
suggestions I'd be glad for the help.

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.

vim fold: how to avoid the "+--" marks

experts:

a question about vim fold:

I can fold these:

into :

+-- 2 lines: c

I just wonder, how to avoid displaying the "+--", and just leave it as:

2 lines: c

sometime this looks "cleaner" for me... especially if I need to refer the folded text in other docs...

any idea?

Re: Do you use status line plugins like powerline or airline?

yes I use vim airline, that's a great plugin!

On Sat, Mar 15, 2014 at 7:17 AM, Paul Isambert <zappathustra@free.fr> wrote:

Charles Campbell <Charles.E.Campbell@nasa.gov> a écrit:

> Joseph Orbegoso Pea wrote:
> > I'm curious to gain some insight on powerline/airline usage. If you know what powerline and airline are, can you answer this poll?
> > http://www.easypolls.net/poll.html?p=531ade39e4b061af6f246519

I can see the results, but I can't vote.

> I use StlShowFunc.vim which shows the name of the current function that
> I'm editing in the status line (C, C++, Matlab, Maple, perl, sh, tex,
> vim, fortran). Its available at:
> http://www.drchip.org/astronaut/vim/index.html#STLSHOWFUNC

That's an excellent idea! I'll certainly use it soon (the idea, not
the plugin, since I use my own statusline).

Paul

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

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

Hi David,

I've installed it, and open the two files:

When I do trough the GUI or with :WhatsMissing I get the error

WM: cannot search other buffers with :set nohidden

How do I solve that?

Rgds,

Jeri

On Mon, Apr 21, 2014 at 4:16 PM, David Fishburn <dfishburn.vim@gmail.com> wrote:

On Mon, Apr 21, 2014 at 5:14 AM, Jeri Raye <jeri.raye@gmail.com> wrote:

Hi,

I have a file allwords.txt.
And I have another file mywords.txt

How can I filter the differences, and safe them in another file called difwords.txt?

Example:
+------ allwords.txt -------+
James
Richard
Anna
Claude
Ben
+------------+

+------mywords.txt-----+
Anna
Ben
+-------------------+

This should then make the following file

+------difwords.txt-----+
James
Richard
Claude
+-----------+

Jeri,

I had the same problem when I create Vim syntax files.

I have a list of "words" and I need to compare those against all the words in my Vim syntax file. So when the product I wrote the syntax file for comes out with a new version, there is typically more "keywords" which need to be added to the syntax file.

I have a process which creates 1 file with all the keywords for the new version. Now I need to merge that with my existing Vim syntax file.

I want to see any combination of:

1. All words missing.
2. All words in both (not missing).
3. Can also do the same linewise, rather than wordwise.

So I wrote a plugin to do it:

WhatMissing.vim - Shows what is missing between 2 buffers
http://vim.sourceforge.net/script.php?script_id=1108

It has a menu to help with the choices and getting started.

Enjoy.
David

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

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

Re: Completing functions with # in the name

On Apr 25, 2014 11:21 AM, "Chris Allison" <chris.charles.allison@gmail.com> wrote:
>
> Hi skeept,
>
> what version are you using, as with my version it works as expected

Try doing

:set iskeyword&vim isident&vim
before completing (this will reset iskeyword and isident options to the default for vim).

>
> :call unite# <TAB> will complete with functions that start unite# and
> not at the beginning of the list as in your case.
>
> chris@druida: ~ $ vim --version
> VIM - Vi IMproved 7.4 (2013 Aug 10, compiled Mar 24 2014 19:35:25)
> Included patches: 1-214
> Compiled by Arch Linux
>
> regards
>
> Chris
>
> On 24 April 2014 19:31, skeept <skeept@gmail.com> wrote:
> > Hi all,
> >
> > is there a setting that I can use that will allow me to complete a function with # in the name?
> >
> > The current situation is as follows:
> > Suppose I want to call a function called unite#custom#alias()
> > If I type
> >
> > :call unite
> >
> > and hit <tab> multiple times then eventually matching completions will cycle until it matches the function I am looking for.
> >
> > But if I type
> >
> > :call unite#
> >
> > and hit <tab> the completions offered are in my case Agrep_Path AlternateFile, ... which would be the completions offered if I didn't had specified anything.
> >
> >
> > Thanks for any hints.
> > Jorge
> >
> > --
> > --
> > You received this message from the "vim_use" maillist.
> > Do not top-post! Type your reply below the text you are replying to.
> > For more information, visit http://www.vim.org/maillist.php
> >
> > ---
> > You received this message because you are subscribed to the Google Groups "vim_use" group.
> > To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
> > For more options, visit https://groups.google.com/d/optout.
>
>
>
> --
> _ 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: Completing functions with # in the name

>
> what version are you using, as with my version it works as expected
>
>
>
> :call unite# <TAB> will complete with functions that start unite# and
>
> not at the beginning of the list as in your case.
>

Hi Chris,

my current vim version is 7.4.265, compiled this morning.
I can reproduce the behavior I mentioned with a very minimal setting:

############# test.vim#############
set nocompatible
set runtimepath+=~/vimfiles/bundle/unite
###################################

vim -u test.vim

Does it work fine for you with this minimal setting?

Thanks,
Jorge.

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

---
You received this message because you are subscribed to the Google Groups "vim_use" group.
To unsubscribe from this group and 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: Possible to auto add / to end of line when vim reaches textwidth and does a new line?

>On Thursday, April 24, 2014 1:15:23 PM UTC-5, slack woody wrote:
>> Hi
>>
>>
>>
>> When I'm writing shell scripts I tend to have textwidth at around 72
>>
>> characters. Is there a way that vim can auto add a \ at the end of the
>>
>> line when it starts a new line?
>>
>
>I think you can use the 'formatexpr' option for this. You'll need to write a function to do your formatting for you, including breaking the line and adding the '\'.

Thanks, I'll look into that.

-Dave

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

---
You received this message because you are subscribed to the Google Groups "vim_use" group.
To unsubscribe from this group and 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: Possible to auto add / to end of line when vim reaches textwidth and does a new line?

On Thursday, April 24, 2014 1:15:23 PM UTC-5, slack woody wrote:
> Hi
>
>
>
> When I'm writing shell scripts I tend to have textwidth at around 72
>
> characters. Is there a way that vim can auto add a \ at the end of the
>
> line when it starts a new line?
>

I think you can use the 'formatexpr' option for this. You'll need to write a function to do your formatting for you, including breaking the line and adding the '\'.

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

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

libcall E364

Hi,

I compiled a dlltest.dll under windows 64bits that fails at vim libcall.

_____________source code____________
.h
extern "C" __declspec(dllexport) int decrease(long a);

.cpp
extern "C" __declspec(dllexport)
int decrease(long a)
{
return (a-1);
}
___end____of______source code____________

:echo libcallnr('dlltest', 'Decrease', 5)
E364: Library call failed for "Decrase()"

dlltest.dll is under vim74 directory with gvim.exe.

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

---
You received this message because you are subscribed to the Google Groups "vim_use" group.
To unsubscribe from this group and 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: Completing functions with # in the name

Hi skeept,

what version are you using, as with my version it works as expected

:call unite# <TAB> will complete with functions that start unite# and
not at the beginning of the list as in your case.

chris@druida: ~ $ vim --version
VIM - Vi IMproved 7.4 (2013 Aug 10, compiled Mar 24 2014 19:35:25)
Included patches: 1-214
Compiled by Arch Linux

regards

Chris

On 24 April 2014 19:31, skeept <skeept@gmail.com> wrote:
> Hi all,
>
> is there a setting that I can use that will allow me to complete a function with # in the name?
>
> The current situation is as follows:
> Suppose I want to call a function called unite#custom#alias()
> If I type
>
> :call unite
>
> and hit <tab> multiple times then eventually matching completions will cycle until it matches the function I am looking for.
>
> But if I type
>
> :call unite#
>
> and hit <tab> the completions offered are in my case Agrep_Path AlternateFile, ... which would be the completions offered if I didn't had specified anything.
>
>
> Thanks for any hints.
> Jorge
>
> --
> --
> You received this message from the "vim_use" maillist.
> Do not top-post! Type your reply below the text you are replying to.
> For more information, visit http://www.vim.org/maillist.php
>
> ---
> You received this message because you are subscribed to the Google Groups "vim_use" group.
> To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.

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

Thursday, April 24, 2014

Re: taglist: how to display tcl variables?

thanks. I'll look into it.

On Wed, Apr 23, 2014 at 2:49 PM, Yegappan Lakshmanan <yegappanl@gmail.com> wrote:

Hi,

On Sat, Apr 19, 2014 at 10:20 AM, ping song <songpingemail@gmail.com> wrote:
> I remember I ever saw the variables in tlist window.
> but currently I only see functions/procedures,nothing else.
> I change the taglist.vim :
>
> let s:tlist_def_tcl_settings =
> 'tcl;c:class;v:variable;f:method;m:method;p:procedure'
>
> but still not working...
>
> research on ctag showing that it might not support this:
>
> ping@ubuntu1404:~/bin$ ctags --list-kinds=all | grep -iA5 tcl
> Tcl
> c classes
> m methods
> p procedures
> Tex
> c chapters
>
> any way to work around?
>
>

You have to extend exuberant ctags to generate tags for Tcl variables.
You can refer to the following pages for information about extending
exuberant ctags and the taglist plugin:

http://ctags.sourceforge.net/EXTENDING.html
http://vim-taglist.sourceforge.net/extend.html

- Yegappan

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

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

Completing functions with # in the name

Hi all,

is there a setting that I can use that will allow me to complete a function with # in the name?

The current situation is as follows:
Suppose I want to call a function called unite#custom#alias()
If I type

:call unite

and hit <tab> multiple times then eventually matching completions will cycle until it matches the function I am looking for.

But if I type

:call unite#

and hit <tab> the completions offered are in my case Agrep_Path AlternateFile, ... which would be the completions offered if I didn't had specified anything.

Thanks for any hints.
Jorge

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

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

Possible to auto add / to end of line when vim reaches textwidth and does a new line?

Hi

When I'm writing shell scripts I tend to have textwidth at around 72
characters. Is there a way that vim can auto add a \ at the end of the
line when it starts a new line?

Thanks

--
Studioware. We provide the tools - You make the music.
http://www.studioware.org
irc.freenode.net #studioware
irc.oftc.net #studioware

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

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

Keymaps on the command line

I use keymaps a lot because I write in different languages and scripts and cannot afford different physical keyboards and also frequently need phonetic characters and other more or less 'exotic' characters the Latin script. Since I do practically all my writing in Vim using Pandoc and/or LaTeX for typeset rendering I do not feel a need for fancier IMEs.

However I have noticed that when typing in the command line the currently active keymap mostly is not effective but somtimes it is. Why is this so and how can it be controlled? Assuming it can be controlled and is not a bug!

Most of the time I simply yank and put any 'fancy' strings I need on the command line or use * and n but sometimes it is desirable to type on the commandline with a keymap enabled, so I really would like to know how to control this.

TIA,

/bpj

Wednesday, April 23, 2014

Re: taglist: how to display tcl variables?

Hi,

On Sat, Apr 19, 2014 at 10:20 AM, ping song <songpingemail@gmail.com> wrote:
> I remember I ever saw the variables in tlist window.
> but currently I only see functions/procedures,nothing else.
> I change the taglist.vim :
>
> let s:tlist_def_tcl_settings =
> 'tcl;c:class;v:variable;f:method;m:method;p:procedure'
>
> but still not working...
>
> research on ctag showing that it might not support this:
>
> ping@ubuntu1404:~/bin$ ctags --list-kinds=all | grep -iA5 tcl
> Tcl
> c classes
> m methods
> p procedures
> Tex
> c chapters
>
> any way to work around?
>
>

You have to extend exuberant ctags to generate tags for Tcl variables.
You can refer to the following pages for information about extending
exuberant ctags and the taglist plugin:

http://ctags.sourceforge.net/EXTENDING.html
http://vim-taglist.sourceforge.net/extend.html

- Yegappan

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

---
You received this message because you are subscribed to the Google Groups "vim_use" group.
To unsubscribe from this group and 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: S&R with search input from a file

Hi Tim,

I'm trying to make a function out of your commands.
Perhaps that that is the reason why it's not working straight away.

Rgds, Jeri

On Mon, Apr 21, 2014 at 4:42 PM, Tim Chase <vim@tim.thechases.com> wrote:

On 2014-04-21 08:37, Jeri Raye wrote:
> :s/..$
> doesn't work at my windows system
> I use:
> execute "normal! \<end>xx"

This should work on all versions of vim, regardless of operating
system. How are you determining that it isn't working? Is it giving
you an error? Is it not removing the last two characters (the "\|")
from the line? If you are having a problem, you could tweak the
first couple steps to

:1,$-s/$/\\|/

which will tack them onto every line *except* the last one, saving
you that ":s/..$/" step.

> Then it fails on
> 0y$
>
> I get the error message E488: Trailing characters

This sounds like you're trying to do this in some mode that isn't
normal-mode. Perhaps command-mode?

You could yank the entire line and then just remove the newline at
the end if that's easier.

> I also noticed that the <C-R> mapping in the last substitute
> command is already used in another plugin.
> Is there a workaround for?

You mean...other than not remapping away something that is incredibly
valuable? ;-) You can always map something else to it:

:cnoremap <f4> <c-r>

-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: C++11 Lambda indentation in vim 7.4

Did you try clang-format? C++ is so complex a language that only a real C++ parser can deal things correctly. Clang-format is also highly configurable, with easy integration with Vim.

On 26 March 2014 22:12, Klaus Rudolph <lts-rudolph@gmx.de> wrote:

C++ Lambda Expressions are now not longer an error in syntax highlighting and indentation since vim 7.4. But inside a lambda expression the indentation did not work as I expect.

Auto indent (gg=G) gives the following result:

auto x1=GenFunktor(
[]()
{
a+=2;
{
int x;
x++;
}
}
);

What I expect:

auto x1=GenFunktor
(
[]()
{
a+=2;
{
int x;
x++;
}
}
);

"simply" the normal indentation rules should also work inside the lambda expression. Is there a configuration setting to enable that?

Regards
Klaus

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

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

--
Wu Yongwei
URL: http://wyw.dcweb.cn/

Tuesday, April 22, 2014

Re: vim: missing register * and #

maybe I forgot to mention: I was always working from within ssh, not within the linux GUI (gnome e.g)...

I tested it from within the ubuntu desktop,

launching console vim from gnome-terminal,

select some text into * +,

I can then see the * +

then I exit everything from my ssh and re-login again remotely,

now within GNU screen I can see the * +

so confusing....I'll post if I can figure this out...

On Tue, Apr 22, 2014 at 11:41 PM, ping song <songpingemail@gmail.com> wrote:

On Sat, Apr 19, 2014 at 2:25 PM, Gary Johnson <garyjohn@spocom.com> wrote:

On 2014-04-19, ping song wrote:

> On Thu, Apr 17, 2014 at 6:46 AM, Tim Chase wrote:
>
> On 2014-04-17 03:13, John Little wrote:
> > Shlomi Fish said:
> >
> > > it's possible the Ubuntu console vim packages don't have that
> > > functionality.
> >
> > No, after installing vim-gnome /etc/alternatives/vi and vim will
> > point to /usr/bin/vim.gtk, so the xterm clipboard (+) and selection
> > (*) should be working.
>
> It's possible that the alternatives didn't get updated. I *think*
> (Ubuntu being a Debian derivative, and this works on Debian) you can
> do
>
> sudo update-alternatives --config vi
>
> which will let you manually specify the binary to use. In this case,
> it *should* point to vim.gtk, so if it doesn't, you can repoint it.
>
> It would also help to know how the OP is invoking it: if Ping is
> invoking it as "vim.gtk" to obtain the correct version information,
> but then invokes it as "vi" or "vim", it might be using some other
> binary.

> thanks.
>
> I means the "+" and "*" register..
>
> It looks both vi and vim were linked to the right target -- vim.gnome:
>
>
> ping@ubuntu1404:~$ sudo update-alternatives --config vi
> [sudo] password for ping:
> There are 4 choices for the alternative vi (providing /usr/bin/vi).
>
> Selection Path Priority Status
> ------------------------------------------------------------
> * 0 /usr/bin/vim.gnome 60 auto mode
> 1 /usr/bin/vim.basic 30 manual mode
> 2 /usr/bin/vim.gnome 60 manual mode
> 3 /usr/bin/vim.gtk 50 manual mode
> 4 /usr/bin/vim.tiny 10 manual mode
>
>
> this is very strange -- I actually finally get it worked around, but with a
> weird way that myself still does not quite get it - but it works, only under
> gnu screen:
> as long as I have the following .screenrc , vim *+ register works, if I remove
> this .screenrc, the register gone...
> without gnu screen still no register * and +
>
> isn't it weird ???
>
>
> #record log in file session-year-month-date.screen.log
> logfile $HOME/temp/%t-%Y-%m%d-.screen.log
> #this doesn't work as expected
> log on
> #scrollback to 10k lines in cp/paste mode
> defscrollback 100000
> # hardstatus line
> hardstatus alwayslastline
> #hardstatus alwayslastline "%{Yk}%-w%{.Yk}%n %t%{-}%+w %=%{.w}"
> hardstatus string "%{= B}:%{= b}: %{= r}[ %{=b G}%H%{= r} ] %= %{=b b}%-w%{=rb
> db}%>%n %t%{-}%+w %=%{= r}[ %{G}%c %{M}%D %m-%d %{r}] %{= b}:%{B}:"
> # Make the xterm scroller work in screen, also works
> # with mouse scrollwheel(does not work...)
> #terminfo xterm*|rxvt ti@:te@
> # use audio bell
> #vbell off
> vbell on
> vbell_msg " Wuff ---- Wuff!! "
> #use zshell as default shell
> #shell zsh
> #for vim integration, seems no use
> maptimeout 5
>
> #caption always "%{+b Yk}%w"
>
> #looks these no much use...
> #bindkey -m ) eval "stuff ' '" "writebuf /tmp/sx" "!sh -c 'xsel -b < /tmp/sx'"
> #bind ( eval "stuff ' '" "!sh -c 'xsel -b > /tmp/sx'" "readbuf /tmp/sx"
>
> backtick 1 5 5 uptime
>
> setenv DISPLAY :0.0

I think the reason that you see those registers only when using
screen is that last line, the one that sets DISPLAY. Without
DISPLAY in the environment, Vim thinks it is not running under X so
it does not enable any features that depend on X.

However, setting DISPLAY manually is not the correct solution. Your
system should set DISPLAY itself. If it is not setting DISPLAY
itself, you need to find out why and fix that.

And please don't top-post to this list.

Regards,
Gary

just figured out how to down-post from within gmail..

I just realized so weird that my *+ dissappear again, within or without GNU screen -- I think I just did some update and rebooted the PC...

I configured DISPLAY manually, no change...

ping@ubuntu1404:~$ export DISPLAY=:.0.0
ping@ubuntu1404:~$ echo $DISPLAY
:.0.0

ping@ubuntu1404:vim

NORMAL >> [N
:registers
--- Registers
"" sdfljsl^
"0 sdfljsl^
"1 Work1#^J

"2 Work1#^J
"3 Work1#^J
"4 Work1#^J
"5 Work1#^J
"6 /data/my
"7 /data/my
"8 ^J
"9 # [link]

"-
": register
"/ export
Press ENTER o

ping@ubuntu1404:~$ sudo update-alternatives --config vim
There are 3 choices for the alternative vim (providing /usr/bin/vim).

Selection Path Priority Status
------------------------------------------------------------
* 0 /usr/bin/vim.gnome 60 auto mode
1 /usr/bin/vim.basic 30 manual mode

2 /usr/bin/vim.gnome 60 manual mode
3 /usr/bin/vim.gtk 50 manual mode

VIM - Vi IMproved 7.4 (2013 Aug 10, compiled Jan 2 2014 19:39:47)

Included patches: 1-52
Modified by pkg-vim-maintainers@lists.alioth.debian.org
Compiled by buildd@
Huge version with GTK2-GNOME GUI. Features included (+) or not (-):

+acl +clientserver +cscope +emacs_tags +folding +keymap +menu +mouse_netterm +netbeans_intg -python3 -sniff +tcl +virtualedit +

writebackup
+arabic +clipboard +cursorbind +eval -footer +langmap +mksession +mouse_sgr +path_extra +quickfix +startuptime +terminfo +visual +X11

+autocmd +cmdline_compl +cursorshape +ex_extra +fork() +libcall +modify_fname -mouse_sysmouse +perl +reltime +statusline +termresponse +visualextra -xfontset

+balloon_eval +cmdline_hist +dialog_con_gui +extra_search +gettext +linebreak +mouse +mouse_urxvt +persistent_undo +rightleft -sun_workshop +textobjects +viminfo +xim

+browse +cmdline_info +diff +farsi -hangul_input +lispindent +mouseshape +mouse_xterm +postscript +ruby +syntax +title +vreplace +

xsmp_interact
++builtin_terms +comments +digraphs +file_in_path +iconv +listcmds +mouse_dec +multi_byte +printer +scrollbind +tag_binary +toolbar +wildignore +

xterm_clipboard
+byte_offset +conceal +dnd +find_in_path +insert_expand +localmap +mouse_gpm +multi_lang +profile +signs +tag_old_static +user_commands +wildmenu -

xterm_save
+cindent +cryptv -ebcdic +float +jumplist +lua -mouse_jsbterm -mzscheme +python +smartindent -tag_any_white +vertsplit +windows +xpm

system vimrc file: "$VIM/vimrc"
user vimrc file: "$HOME/.vimrc"
2nd user vimrc file: "~/.vim/vimrc"
user exrc file: "$HOME/.exrc"

system gvimrc file: "$VIM/gvimrc"
user gvimrc file: "$HOME/.gvimrc"
2nd user gvimrc file: "~/.vim/gvimrc"
system menu file: "$VIMRUNTIME/menu.vim"

fall-back for $VIM: "/usr/share/vim"
Compilation: gcc -c -I. -Iproto -DHAVE_CONFIG_H -DFEAT_GUI_GTK -pthread -I/usr/include/gtk-2.0 -I/usr/lib/x86_64-linux-gnu/gtk-2.0/include -I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/

pango-1.0 -I/usr/include/gio-unix-2.0/ -I/usr/include/freetype2 -I/usr/include/glib-2.0 -I/usr/lib/x86_64-linux-gnu/glib-2.0/include -I/usr/include/pixman-1 -I/usr/include/libpng12 -I/usr/include/harfbuzz -pthread -DORBIT2=1 -

D_REENTRANT -I/usr/include/libgnomeui-2.0 -I/usr/include/libart-2.0 -I/usr/include/gconf/2 -I/usr/include/gnome-keyring-1 -I/usr/include/libgnome-2.0 -I/usr/include/libbonoboui-2.0 -I/usr/include/libgnomecanvas-2.0 -I/usr/include/

gtk-2.0 -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/gnome-vfs-2.0 -I/usr/lib/x86_64-linux-gnu/gnome-vfs-2.0/include -I/usr/include/dbus-1.0 -I/usr/lib/x86_64-linux-gnu/dbus-1.0/include -I/usr/include/glib-2.0 -I/usr/lib/x86_64-

linux-gnu/glib-2.0/include -I/usr/include/orbit-2.0 -I/usr/include/libbonobo-2.0 -I/usr/include/bonobo-activation-2.0 -I/usr/include/libxml2 -I/usr/include/pango-1.0 -I/usr/include/gail-1.0 -I/usr/include/harfbuzz -I/usr/include/

freetype2 -I/usr/include/atk-1.0 -I/usr/lib/x86_64-linux-gnu/gtk-2.0/include -I/usr/include/cairo -I/usr/include/gio-unix-2.0/ -I/usr/include/pixman-1 -I/usr/include/libpng12 -g -O2 -fstack-protector --param=ssp-buffer-size=4

Wformat -Werror=format-security -U_FORTIFY_SOURCE -D_FORTIFY_SOURCE=1 -I/usr/include/tcl8.6 -D_REENTRANT=1 -D_THREAD_SAFE=1 -D_LARGEFILE64_SOURCE=1
Linking: gcc -L. -Wl,-Bsymbolic-functions -Wl,-z,relro -rdynamic -Wl,-export-dynamic -Wl,-E -Wl,-Bsymbolic-functions -Wl,-z,relro -Wl,--as-needed -o vim -lgtk-x11-2.0 -lgdk-x11-2.0 -latk-1.0 -lgio-2.0 -lpangoft2-1.0 -

lpangocairo-1.0 -lgdk_pixbuf-2.0 -lcairo -lpango-1.0 -lfontconfig -lgobject-2.0 -lglib-2.0 -lfreetype -lgnomeui-2 -lSM -lICE -lbonoboui-2 -lgnomevfs-2 -lgnomecanvas-2 -lgnome-2 -lpopt -lbonobo-2 -lbonobo-activation -lORBit-2 -

lart_lgpl_2 -lgtk-x11-2.0 -lgdk-x11-2.0 -latk-1.0 -lgio-2.0 -lpangoft2-1.0 -lpangocairo-1.0 -lgdk_pixbuf-2.0 -lcairo -lpango-1.0 -lfontconfig -lfreetype -lgconf-2 -lgthread-2.0 -lgmodule-2.0 -lgobject-2.0 -lglib-2.0 -lSM -lICE -

lXpm -lXt -lX11 -lXdmcp -lSM -lICE -lm -ltinfo -lnsl -lselinux -lacl -lattr -lgpm -ldl -L/usr/lib -llua5.2 -Wl,-E -fstack-protector -L/usr/local/lib -L/usr/lib/perl/5.18/CORE -lperl -ldl -lm -lpthread -lcrypt -L/usr/lib/

python2.7/config-x86_64-linux-gnu -lpython2.7 -lpthread -ldl -lutil -lm -Xlinker -export-dynamic -Wl,-O1 -Wl,-Bsymbolic-functions -L/usr/lib/x86_64-linux-gnu -ltcl8.6 -ldl -lz -lpthread -lieee -lm -lruby-1.9.1 -lpthread -lrt -

ldl -lcrypt -lm -L/usr/lib

Tuesday, April 29, 2014

Monday, April 28, 2014

Sunday, April 27, 2014

Saturday, April 26, 2014

Friday, April 25, 2014

Thursday, April 24, 2014

Wednesday, April 23, 2014

Tuesday, April 22, 2014

Blog Archive

About Me