Friday, May 31, 2013

ANN: OutlookVim 10.0

OutlookVim is a plugin for Microsoft Windows Outlook users.

It simply adds a button in Outlook which will spawn Vim, allow you to
edit the body of the currently open email and when you :w, it will
update Outlook with the results.

There are more details, you can read about them here:
http://www.vim.org/scripts/script.php?script_id=3087

New to version 10.0

New Features
------------
- Editing HTML formated Outlook emails is now supported.  A new option has been added, g:outlook_supported_body_format, can have one of two values: plain or html.

NOTE: Outlook html contains a lot of markup tags.  It can make it difficult to find the body text within all the tags.

- A new option has been added, g:outlook_file_type, which defaults to 'mail'.  When opening the buffer within Vim, this file type is set for the buffer.   You may want to change this value if you are editig HTM emails.

- A new command has been added: OutlookNewEmail.  This will take the contents of the existing buffer and create a new Outlook email.  If the filetype is 'html' and g:outlook_supported_body_format = 'html', the email body will be html rather than plain text.  The command can be run as often as necessary, a new Outlook email will be created each time.
                                                                              
Bug Fixes
---------
- The additional changes to the VB code to support both 32-bit and 64-bit platforms does not work with Outlook 2007 32-bit (at least).  The new changes will work for either (Greg Dunn).

.

As usual, with all my plugins, feedback good and bad is always welcome.

Enjoy.
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/groups/opt_out.
 
 

Re: what about cscope

Hi wangjun850725!

On Fr, 31 Mai 2013, wangjun850725 wrote:

> I use cscope on windows, but I found an uncomfortable question.
>
> I use cscope find -g variable, it display three tags that are all same.


:h csqf

regards,
Christian
--
Dunkel ist des Glückes launenhafter Gang, ein unbegreifbar,
unergründlich Rätselspiel.
-- Euripides (Hekabe, 580-406 v. Chr.)

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

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

Re: Re: what about cscope

thanks a lot
I download 15.8a version, it is ok
https://code.google.com/p/cscope-win32/downloads/detail?name=cscope-15.8a-win32rev1-static.zip&can=2&q=
 

wangjun850725
 
From: Marc Weber
Date: 2013-06-01 00:03
To: vim_use
Subject: Re: what about cscope
https://github.com/MarcWeber/SmartTag/blob/master/doc/SmartTag.txt
resolves ambiguous tags.  No idea whether its useful. I Just put it on
my github account so that the patch doesn't get lost. Eventually
requires a python patch.
 
Maybe you'll get more helpful replies than this.
 
Marc Weber
 
-- 
-- 
You received this message from the "vim_use" maillist.
Do not top-post! Type your reply below the text you are replying to.
For more information, visit http://www.vim.org/maillist.php
 
--- 
You received this message because you are subscribed to the Google Groups "vim_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
 
 

Re: what about cscope

https://github.com/MarcWeber/SmartTag/blob/master/doc/SmartTag.txt
resolves ambiguous tags. No idea whether its useful. I Just put it on
my github account so that the patch doesn't get lost. Eventually
requires a python patch.

Maybe you'll get more helpful replies than this.

Marc Weber

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

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

what about cscope

I use cscope on windows, but I found an uncomfortable question.
 
I use cscope find -g variable, it display three tags that are all same.
 
How to solve this quesition?
thanks!

Re: which terminal


Now vim and allmost all terminal applications support terminal-native horizontal split scrolling, but terminal-native "vertical" split scrolling is not supported by them. So vim redraws all cells in the target region and it may annoy us.

Actually, there are two ways to realize it on VT-like terminals.
The first way is using DECLRMM and DECSLRM (left and right margins) sequence supported by recent xterm.
The second is pseudo-scrolling with DECCRA (Copy Rectangular Area) sequence which is supported by recent xterm and other few terminals.

Both of them certainly cut off I/O latency and makes vertical scrolling more faster, especially when the terminal screen has over 10,000 cells.

Now the problem for vim is that these terminal features are not provided widely yet. on the other hand, I think, if a major text editor like vim supports it, the circumstances will changed.

See also :

-- Hayaki



On 2013/05/31, at 20:47, Michael Hernandez <sequethin@gmail.com> wrote:

On May 31, 2013, at 2:05 AM, ZyX ZyX <zyx.vim@gmail.com> wrote:


On May 31, 2013 7:11 AM, "sinbad" <sinbad.sinbad@gmail.com> wrote:
>
> what is the best terminal to use.i currently use putty i find that
> the scrolling is dead slow when i open a diff window, i learnt
> that the xterm terminal doesn't have the native split scrolling,
> is there any terminal that is good at this. i googled and found
> fbterm is one of those, but the development of this project has
> stopped. have you been suffering from same problem and which terminal
> do you use ?
>
> -sinbad

Never saw problems with scrolling in xterm. I personally use konsole.

And WTF is "native split scrolling"?

If sinbad means to split a terminal window and let each portion have its own scroll buffer, I'd recommend tmux, regardless of terminal emulator. Splitting the "screen" is something tmux excels at.

--Mike H

By the way, AFAIK fbterm is a replacement for kernel built-in terminal. Xterm is an X11 terminal emulator.

> --
> --
> You received this message from the "vim_use" maillist.
> Do not top-post! Type your reply below the text you are replying to.
> For more information, visit http://www.vim.org/maillist.php
>
> ---
> You received this message because you are subscribed to the Google Groups "vim_use" group.
> To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
> For more options, visit https://groups.google.com/groups/opt_out.
>
>


--
--
You received this message from the "vim_use" maillist.
Do not top-post! Type your reply below the text you are replying to.
For more information, visit http://www.vim.org/maillist.php
 
---
You received this message because you are subscribed to the Google Groups "vim_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
 
 

--
--
You received this message from the "vim_use" maillist.
Do not top-post! Type your reply below the text you are replying to.
For more information, visit http://www.vim.org/maillist.php
 
---
You received this message because you are subscribed to the Google Groups "vim_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
 
 

Re: vim7.4

vim.sf.net -> download -> source compile latest patch level yourself.

Bram told that he'd accept patches till today - then bug fixing should
happen.

So be patient. 7.4 will happen - but I hope we get it right, rather than
fast.

Marc Weber

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

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

Re: gvim on XP truncates/destroys network files, removes permissions

On Friday, May 31, 2013 8:44:07 AM UTC-5, Joseph Pietras wrote:
> Hello,
>
> I have googled to find a solution for this problem which only recently started to occur after my desktop was relocated within the company. I work at a mostly WINDOWS shop and 'gvim" is definitely a non-supported product so I have to have details of the problem before I can ask Help Desk for support, should that be necessary. Hope someone has seen this. My desktop is XP and I am using
>
> VIM - Vi IMproved 7.3 (2010 Aug 15, compiled Oct 27 2010 17:59:02)
>
> (full givm --version output available if needed)
>
>
>
>
>
> If I open a file with gvim (right click, open with vim) my first attempt to write the file truncates it to zero bytes, for example:
>
> -rwx------+ 1 jpietras Domain Users 505 May 31 08:27 SomeProgram.ini
>
>
>
> Exit and writ
>
> -r-x------+ 1 jpietras Domain Users 0 May 31 08:27 SomeProgram.ini
>
>
>
> But only on network shared drives, my C: drive works as expected.
>

I'm not sure why you'd be seeing this. Maybe try experimenting with the 'backupcopy' and 'writebackup' options.

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

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

vim7.4

[2013-05-17] 7.3 has more than 950 patches, that's too many! Time for a new (minor) release. The plan is to (1) improve Python support, (2) include a faster regexp engine and (3) include pending patches and fix bugs. A test version should be available end of May. The release happens when it appears to work well. (Bram Moolenaar)
 
 
Now where it is ?

gvim on XP truncates/destroys network files, removes permissions

Hello,
I have googled to find a solution for this problem which only recently started to occur after my desktop was relocated within the company. I work at a mostly WINDOWS shop and 'gvim" is definitely a non-supported product so I have to have details of the problem before I can ask Help Desk for support, should that be necessary. Hope someone has seen this. My desktop is XP and I am using
VIM - Vi IMproved 7.3 (2010 Aug 15, compiled Oct 27 2010 17:59:02)
(full givm --version output available if needed)


If I open a file with gvim (right click, open with vim) my first attempt to write the file truncates it to zero bytes, for example:
-rwx------+ 1 jpietras Domain Users 505 May 31 08:27 SomeProgram.ini

Exit and writ
-r-x------+ 1 jpietras Domain Users 0 May 31 08:27 SomeProgram.ini

But only on network shared drives, my C: drive works as expected.

Thanks for your help!
Joseph Pietras


This e-mail and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you have received this e-mail in error please notify the originator of the message. This footer also confirms that this e-mail message has been scanned for the presence of computer viruses. Any views expressed in this message are those of the individual sender, except where the sender specifies and with authority, states them to be the views of Iowa Student Loan.





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

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

Re: which terminal

On May 31, 2013, at 2:05 AM, ZyX ZyX <zyx.vim@gmail.com> wrote:


On May 31, 2013 7:11 AM, "sinbad" <sinbad.sinbad@gmail.com> wrote:
>
> what is the best terminal to use.i currently use putty i find that
> the scrolling is dead slow when i open a diff window, i learnt
> that the xterm terminal doesn't have the native split scrolling,
> is there any terminal that is good at this. i googled and found
> fbterm is one of those, but the development of this project has
> stopped. have you been suffering from same problem and which terminal
> do you use ?
>
> -sinbad

Never saw problems with scrolling in xterm. I personally use konsole.

And WTF is "native split scrolling"?

If sinbad means to split a terminal window and let each portion have its own scroll buffer, I'd recommend tmux, regardless of terminal emulator. Splitting the "screen" is something tmux excels at.

--Mike H

By the way, AFAIK fbterm is a replacement for kernel built-in terminal. Xterm is an X11 terminal emulator.

> --
> --
> You received this message from the "vim_use" maillist.
> Do not top-post! Type your reply below the text you are replying to.
> For more information, visit http://www.vim.org/maillist.php
>
> ---
> You received this message because you are subscribed to the Google Groups "vim_use" group.
> To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
> For more options, visit https://groups.google.com/groups/opt_out.
>
>

--
--
You received this message from the "vim_use" maillist.
Do not top-post! Type your reply below the text you are replying to.
For more information, visit http://www.vim.org/maillist.php
 
---
You received this message because you are subscribed to the Google Groups "vim_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
 
 

Re: screen (and vim-r) tmp files problem

That is a good tip indeed.
Thank you.



On Fri, May 31, 2013 at 10:35 AM, Matt Bray <mattjbray@gmail.com> wrote:
> I had the same problem when I tried fish out as my default shell a couple of weeks ago. Most of my plugins crashed out with this error. I went back to zsh in the end.
>
> If you want to stick with fish try giving vim a POSIX shell to work with by adding this to your vimrc:
>
> set shell=/usr/bin/sh
>
> (Or wherever your sh is located - " which sh")
>
> Matt
>
> --
> --
> You received this message from the "vim_use" maillist.
> Do not top-post! Type your reply below the text you are replying to.
> For more information, visit http://www.vim.org/maillist.php
>
> ---
> You received this message because you are subscribed to a topic in the Google Groups "vim_use" group.
> To unsubscribe from this topic, visit https://groups.google.com/d/topic/vim_use/yipDHXNrNzg/unsubscribe?hl=en.
> To unsubscribe from this group and all its topics, send an email to vim_use+unsubscribe@googlegroups.com.
> For more options, visit https://groups.google.com/groups/opt_out.
>
>



--
Jonathan Rosenblatt
www.john-ros.com

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

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

Re: Best possible plugin/tool for multiple files search/replace in gVim (windows)

Thanks Folks.

Your suggestions have helped me, to understand new thing  in vim about args.

For the reference of others, this is what I am settled with now.

Find pattern recursively: vimgrep

:vim /SEARCHTEXT/ *.c *.h
:vim /SEARCHTEXT/ **/*.c

Replace in multiple files: :argdo is there but I found DirDo.vim plugin more useful. Because with single command it achievable, no need to set the args before that.

:DDF.  *.c %s/Foo/Bar/gce 



On Thu, May 30, 2013 at 8:26 PM, LCD 47 <lcd047@gmail.com> wrote:
On 30 May 2013, Asis Hallab <asis.hallab@gmail.com> wrote:
[...]
> There could be no better explanation for this than the one Drew Neil
> gives here:
> http://vimcasts.org/episodes/project-wide-find-and-replace/
>
> Take 6 and a half minutes of your time and enjoy his excellent
> screencast.
[...]

    Screencasts #41-#44 are relevant too:

        http://vimcasts.org/episodes/archive

    You might want to bookmark that page, it's one of the best resources
around for Vim.

    /lcd

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

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





--
Swapnil

--
--
You received this message from the "vim_use" maillist.
Do not top-post! Type your reply below the text you are replying to.
For more information, visit http://www.vim.org/maillist.php
 
---
You received this message because you are subscribed to the Google Groups "vim_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
 
 

Re: screen (and vim-r) tmp files problem

I had the same problem when I tried fish out as my default shell a couple of weeks ago. Most of my plugins crashed out with this error. I went back to zsh in the end.

If you want to stick with fish try giving vim a POSIX shell to work with by adding this to your vimrc:

set shell=/usr/bin/sh

(Or wherever your sh is located - " which sh")

Matt

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

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

Thursday, May 30, 2013

Re: which terminal


On May 31, 2013 7:11 AM, "sinbad" <sinbad.sinbad@gmail.com> wrote:
>
> what is the best terminal to use.i currently use putty i find that
> the scrolling is dead slow when i open a diff window, i learnt
> that the xterm terminal doesn't have the native split scrolling,
> is there any terminal that is good at this. i googled and found
> fbterm is one of those, but the development of this project has
> stopped. have you been suffering from same problem and which terminal
> do you use ?
>
> -sinbad

Never saw problems with scrolling in xterm. I personally use konsole.

And WTF is "native split scrolling"?

By the way, AFAIK fbterm is a replacement for kernel built-in terminal. Xterm is an X11 terminal emulator.

> --
> --
> You received this message from the "vim_use" maillist.
> Do not top-post! Type your reply below the text you are replying to.
> For more information, visit http://www.vim.org/maillist.php
>
> ---
> You received this message because you are subscribed to the Google Groups "vim_use" group.
> To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
> For more options, visit https://groups.google.com/groups/opt_out.
>
>

--
--
You received this message from the "vim_use" maillist.
Do not top-post! Type your reply below the text you are replying to.
For more information, visit http://www.vim.org/maillist.php
 
---
You received this message because you are subscribed to the Google Groups "vim_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
 
 

which terminal

what is the best terminal to use.i currently use putty i find that
the scrolling is dead slow when i open a diff window, i learnt
that the xterm terminal doesn't have the native split scrolling,
is there any terminal that is good at this. i googled and found
fbterm is one of those, but the development of this project has
stopped. have you been suffering from same problem and which terminal
do you use ?

-sinbad

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

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

Re: screen (and vim-r) tmp files problem

I have good reason to believe the problem is in the fish shell + screen.vba combo.

Sourcing screen.vba under bash seems to work.

Does this sound reasonable?




On Thursday, May 30, 2013 10:08:41 PM UTC+3, Jonathan Rosenblatt wrote:
> After a mail exchange with Jakson Alves de Aquino, and some trial and error, I have reason to believe this is not a vim-r problem but rather a screen.vba problem.
>
> I try to run :ScreenShell on an arbitrary (non R) file, and get:
>
>
>
> Error detected while processing function screen#ScreenShell..<SNR>31_ScreenInit..9..15:
>
> line 16:
>
> E484: Can't open file /tmp/vNHCyWH/0
>
>
>
> Thank you
>
>
>
> I will report the bug. Any ideas in the meanwhile?
>
>
>
>
>
>
>
> On Thursday, May 30, 2013 10:01:31 PM UTC+3, Christian Brabandt wrote:
>
> > Hi Jonathan!
>
> >
>
> >
>
> >
>
> > On Do, 30 Mai 2013, Jonathan Rosenblatt wrote:
>
> >
>
> >
>
> >
>
> > > Error detected while processing /home/johnros/.vim/r-plugin/common_global.vim:
>
> >
>
> > > line 3106:
>
> >
>
> > > E484: Can't open file /tmp/vAfShCu/0
>
> >
>
> > > line 3327:
>
> >
>
> > > E484: Can't open file /tmp/vAfShCu/1
>
> >
>
> >
>
> >
>
> > You should report this bug at the plugin page, e.g. here:
>
> >
>
> >
>
> >
>
> > https://github.com/jcfaria/Vim-R-plugin/issues
>
> >
>
> >
>
> >
>
> > regards,
>
> >
>
> > Christian
>
> >
>
> > --
>
> >
>
> > Der Bach ist dem M�ller befreundet, dem er nutzt, und er st�rzt
>
> >
>
> > gern �ber die R�der; was hilft es ihm, gleichg�ltig durchs Tal
>
> >
>
> > hinzuschleichen?
>
> >
>
> > -- Goethe, Maximen und Reflektionen, Nr. 77

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

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

Re: screen (and vim-r) tmp files problem

After a mail exchange with Jakson Alves de Aquino, and some trial and error, I have reason to believe this is not a vim-r problem but rather a screen.vba problem.
I try to run :ScreenShell on an arbitrary (non R) file, and get:

Error detected while processing function screen#ScreenShell..<SNR>31_ScreenInit..9..15:
line 16:
E484: Can't open file /tmp/vNHCyWH/0

Thank you

I will report the bug. Any ideas in the meanwhile?



On Thursday, May 30, 2013 10:01:31 PM UTC+3, Christian Brabandt wrote:
> Hi Jonathan!
>
>
>
> On Do, 30 Mai 2013, Jonathan Rosenblatt wrote:
>
>
>
> > Error detected while processing /home/johnros/.vim/r-plugin/common_global.vim:
>
> > line 3106:
>
> > E484: Can't open file /tmp/vAfShCu/0
>
> > line 3327:
>
> > E484: Can't open file /tmp/vAfShCu/1
>
>
>
> You should report this bug at the plugin page, e.g. here:
>
>
>
> https://github.com/jcfaria/Vim-R-plugin/issues
>
>
>
> regards,
>
> Christian
>
> --
>
> Der Bach ist dem M�ller befreundet, dem er nutzt, und er st�rzt
>
> gern �ber die R�der; was hilft es ihm, gleichg�ltig durchs Tal
>
> hinzuschleichen?
>
> -- Goethe, Maximen und Reflektionen, Nr. 77

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

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

Re: vim-r tmp files problem

Hi Jonathan!

On Do, 30 Mai 2013, Jonathan Rosenblatt wrote:

> Error detected while processing /home/johnros/.vim/r-plugin/common_global.vim:
> line 3106:
> E484: Can't open file /tmp/vAfShCu/0
> line 3327:
> E484: Can't open file /tmp/vAfShCu/1

You should report this bug at the plugin page, e.g. here:

https://github.com/jcfaria/Vim-R-plugin/issues

regards,
Christian
--
Der Bach ist dem Müller befreundet, dem er nutzt, und er stürzt
gern über die Räder; was hilft es ihm, gleichgültig durchs Tal
hinzuschleichen?
-- Goethe, Maximen und Reflektionen, Nr. 77

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

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

Re: Best possible plugin/tool for multiple files search/replace in gVim (windows)

On 30 May 2013, Asis Hallab <asis.hallab@gmail.com> wrote:
[...]
> There could be no better explanation for this than the one Drew Neil
> gives here:
> http://vimcasts.org/episodes/project-wide-find-and-replace/
>
> Take 6 and a half minutes of your time and enjoy his excellent
> screencast.
[...]

Screencasts #41-#44 are relevant too:

http://vimcasts.org/episodes/archive

You might want to bookmark that page, it's one of the best resources
around for Vim.

/lcd

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

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

vim-r tmp files problem

Hello everyone.

Looking for help with vim-r.

I am getting the following error:

Error detected while processing /home/johnros/.vim/r-plugin/common_global.vim:
line 3106:
E484: Can't open file /tmp/vAfShCu/0
line 3327:
E484: Can't open file /tmp/vAfShCu/1


Interestingly, this happened on my laptop and PC at different times.

Thank you in advance



Some technical details:

Ubuntu Linux 11.10 (but also on 13.04)

VIM - Vi IMproved 7.3 (2010 Aug 15, compiled Feb 28 2012 13:49:48)

Happens with or without tmux

Screen 1.5

R 2.15.3 with vimcom, setwidth and colorout

I recently removed the .profile file as it was causing x-session problems.

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

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

Re: Best possible plugin/tool for multiple files search/replace in gVim (windows)

On Thursday, May 30, 2013 3:49:14 AM UTC-5, swapnil wrote:
> Hi All,
> I am gVim user on windows. I want suggestion from folks for search/replace recursively in multiple file use case. There are few tools like EasyGrep,Grep on windows. Searching in multiple files they work, but I keep facing issue for recursive search.
>
> Can someone guide the best tool which works on gVim for windows, which they are using already ?
>

For searching multiple files, especially recursive directory searches, I usually use the :vimgrep command.

Sometimes I might use the :grep command instead (using Windows' "findstr" utility) and pass the /S flag for a recursive search. I haven't done this in a long time.

To replace, now that stuff is in the quickfix list, I usually do a :%s command on the first file, do :cnfile, and repeat until all files are visited. That's more efficient in a macro or a chained command using |.

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

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

Re: Best possible plugin/tool for multiple files search/replace in gVim (windows)

Dear Swapnil,

as with some things in Vim,
accomplishing this task with standard Vim functions seems at first
somewhat tricky.
But Vim actually has everything you need to do a project wide search
and replace.
Once you'll have understood how to accomplish this you'll see,
that actually can do many more fancy things in the same manner.

Basically you just make use of the
:args and :argdo commands.

There could be no better explanation for this than the one Drew Neil gives here:
http://vimcasts.org/episodes/project-wide-find-and-replace/

Take 6 and a half minutes of your time and enjoy his excellent screencast.

Kind regards and Cheers!

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

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

Best possible plugin/tool for multiple files search/replace in gVim (windows)

Hi All,
I am gVim user on windows. I want suggestion from folks for search/replace recursively in multiple file use case. There are few tools like EasyGrep,Grep on windows. Searching in multiple files they work, but I keep facing issue for recursive search.

Can someone guide the best tool which works on gVim for windows, which they are using already ?

Thanks in advance.

Regards
Swapnil

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

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

Re: vim not finding the end of the sql statement

Hi David

I'm new to vim and open source software so still feeling around about where to post questions and find answers - Stack Overflow has been a real revelation for me over the past 18 mths so I sort of live my coding life through that portal but I will switch my vim questions to this group.

I'll use one of the visual modes for the time-being.

WhyTheQ (Jason)


On Thursday, May 30, 2013 2:49:09 AM UTC+1, David Fishburn wrote:
> On Wed, May 29, 2013 at 5:36 PM, whytheq <why...@gmail.com> wrote:
>
> In `gvim` if I put the cursor (normal mode) in the word SELECT and then hit `\se` then it runs ok:
>
>
>
>     SELECT GETDATE();
>
>
>
> If I do exactly the same but for a query over two lines then it errors.
>
>
>
>     SELECT
>
>     GETDATE();
>
>
>
> I have the lastest version of dbext installed.
>
>
>
>
> Another user (Jason) just reported this to me as well.
>
>
> I will look into it in a couple of days.
>
>
> As a work around and a more reliable option, I would use linewise visual mode (capital V) and visually select what you want executed and hit \se to execute that selection.
>
>
>
> So when your cursor is on the line SELECT, use this combination:
> V/;<cr>\se
>
>
> Where <cr> is when you hit enter on the keyboard.
>
>
>
>
>
> BTW, why post these questions on stackoverflow?  This is the Vim list and this is generally where all the plugin authors monitor.
>
>
> 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/groups/opt_out.

Wednesday, May 29, 2013

Re: Why use relative line numbers?

On Do, 30 Mai 2013, Marc Weber wrote:

> Well - relative line numbers were introduced to solve a problem (navigating).
>
> What do relative line numbers do?
> + they show you where the cursor is (you could miss this)
> + they allow to navigate using less keys
>
> issues:
> - they slow you down. If I open :h having 'relativenumbers' set on 9k is
> signifcantly slower ! (at least for me having 230 lines)

Of course it is, because Vim needs to redraw more often, since the
numbers change on almost every move of the cursor. This is also true for
'cursorline'/'cursorcolumn' option.

> I hope that this is a somewhat accurate description about pro/cons of
> relativenumbers feature.
>
> The alternative I proposed does not suffer from the slowness, and G j k
> like movements could be made understanding 'lasts digits' only.

No, because it doesn't work for each use case as has been pointed out,
plus it doesn't work reliably (as you also state in your snippet). So it
is no complete alternative.

> Anyway if you love it and already have a solution - then go for it.

In the thread I mentioned, Bram already said, he doesn't like to remove
or deprecate options.

regards,
Christian
--
Wie viele Jahre Gefängnis entfallen auf die
tausendneunhundertsiebenundfünfzig Jahre nach Christus?
-- Stanislaw Jerzy Lec (eig. S. J. de Tusch-Letz)

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

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

Re: insert mode mapping to move to a column

On Wednesday, May 29, 2013 8:31:09 PM UTC+5:30, Ben Fritz wrote:
> I think (if as Christian suggests you have 'virtualedit' set to "all") this will work: <Up><C-Right><Down>

This works, thanks Ben and toothpik.

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

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

Re: How to Install Powerline on windows

在 2013年4月28日星期日UTC+8下午2时33分37秒,Hunger写道:
> Hi all
>
> I'm a noob of vim.
>
> I tried to install powerline (Lokaltog/powerline) these days, but
> still failed.
>
> There is no doc about intallation on windows,so I want to know the
> steps of install it on windows.
>
>
>
> Thanks for your sight and appriciate for any anyhelp.
>
>
>
>
>
> For now, I download the git zip.  Use "setup.py install" or
> "setup.py install"
>
> add vimrc"set
> rtp+=C:\Python33\Lib\site-
>
> packages\Powerline-beta-py3.3.egg\powerline\bindings\vim"
>
>
> or "set
> rtp+=~/.vim/bundle/powerline/powerline/bindings/vim"
>
> both get error message when run vim.
>
> Error detected while processing function Powerline:
>
> line 3:
>
> Traceback (most recent call last):
>
> File "<string>",line 1,in <module>
>
> Error detected while processing function Powerline:
>
> File"c:\Python33\lib\site-packages\poerline\beta\py3.3
> XXXXX" line 371,in render
>
> My vim is 7.7.905 with python3 and vundle

Thanks for your help, I don't know how to got the full message before...
It has been so long after this post.
I can't reappear the previous error.
Now all the things I did with powerline is
1.add "NeoBundle 'Lokaltog/powerline',{'rtp':'powerline/bindings/vim'}" in vimrc
2.NeoBundleInstall

This is the new whole error:
Error detected while processing VimEnter Auto commands for "*":
Traceback (most recent call last):
Error detected while processing VimEnter Auto commands for "*":
File "C:\Users\kk\.vim\bundle\powerline\powerline\lib\config.py", line 107, in load
Error detected while processing VimEnter Auto commands for "*":
return deepcopy(self.loaded[path])
Error detected while processing VimEnter Auto commands for "*":
KeyError: 'C:\\Users\\kk\\.vim\\bundle\\powerline\\powerline\\config_files\\config.json'
Error detected while processing VimEnter Auto commands for "*":

Error detected while processing VimEnter Auto commands for "*":
During handling of the above exception, another exception occurred:
Error detected while processing VimEnter Auto commands for "*":

Error detected while processing VimEnter Auto commands for "*":
Traceback (most recent call last):
Error detected while processing VimEnter Auto commands for "*":
File "C:\Users\kk\.vim\bundle\powerline\powerline\__init__.py", line 361, in update_renderer
Error detected while processing VimEnter Auto commands for "*":
self.create_renderer(**create_renderer_kwargs)
Error detected while processing VimEnter Auto commands for "*":
File "C:\Users\kk\.vim\bundle\powerline\powerline\__init__.py", line 156, in create_renderer
Error detected while processing VimEnter Auto commands for "*":
config = self.load_main_config()
Error detected while processing VimEnter Auto commands for "*":
File "C:\Users\kk\.vim\bundle\powerline\powerline\vim.py", line 60, in load_main_config
Error detected while processing VimEnter Auto commands for "*":
return _override_from(super(VimPowerline, self).load_main_config(), 'powerline_config_overrides')
Error detected while processing VimEnter Auto commands for "*":
File "C:\Users\kk\.vim\bundle\powerline\powerline\__init__.py", line 316, in load_main_config
Error detected while processing VimEnter Auto commands for "*":
return self._load_config('config', 'main')
Error detected while processing VimEnter Auto commands for "*":
File "C:\Users\kk\.vim\bundle\powerline\powerline\__init__.py", line 294, in _load_config
Error detected while processing VimEnter Auto commands for "*":
return self.config_loader.load(path)
Error detected while processing VimEnter Auto commands for "*":
File "C:\Users\kk\.vim\bundle\powerline\powerline\lib\config.py", line 109, in load
Error detected while processing VimEnter Auto commands for "*":
r = self._load(path)
Error detected while processing VimEnter Auto commands for "*":
File "C:\Users\kk\.vim\bundle\powerline\powerline\lib\config.py", line 19, in load_json_config
Error detected while processing VimEnter Auto commands for "*":
return load(config_file_fp)
Error detected while processing VimEnter Auto commands for "*":
File "C:\Python33\Lib\json\__init__.py", line 271, in load
Error detected while processing VimEnter Auto commands for "*":
return loads(fp.read(),
Error detected while processing VimEnter Auto commands for "*":
UnicodeDecodeError: 'gbk' codec can't decode byte 0xb0 in position 91: illegal multibyte sequence
Error detected while processing VimEnter Auto commands for "*":

Error detected while processing VimEnter Auto commands for "*":
During handling of the above exception, another exception occurred:
Error detected while processing VimEnter Auto commands for "*":

Error detected while processing VimEnter Auto commands for "*":
Traceback (most recent call last):
Error detected while processing VimEnter Auto commands for "*":
File "<string>", line 1, in <module>
Error detected while processing VimEnter Auto commands for "*":
File "C:\Users\kk\.vim\bundle\powerline\powerline\vim.py", line 145, in new_window
Error detected while processing VimEnter Auto commands for "*":
return self.render(window, window_id, winnr)
Error detected while processing VimEnter Auto commands for "*":
File "C:\Users\kk\.vim\bundle\powerline\powerline\__init__.py", line 371, in render
Error detected while processing VimEnter Auto commands for "*":
self.update_renderer()
Error detected while processing VimEnter Auto commands for "*":
File "C:\Users\kk\.vim\bundle\powerline\powerline\__init__.py", line 363, in update_renderer
Error detected while processing VimEnter Auto commands for "*":
self.pl.exception('Failed to create renderer: {0}', str(e))
Error detected while processing VimEnter Auto commands for "*":
AttributeError: 'NoneType' object has no attribute 'exception'
Error detected while processing VimEnter Auto commands for "*":
E860: Eval did not return a valid python 3 object
E475: Invalid argument:
Traceback (most recent call last):
File "<string>", line 1, in <module>
File "C:\Users\kk\.vim\bundle\powerline\powerline\vim.py", line 145, in new_window
return self.render(window, window_id, winnr)
File "C:\Users\kk\.vim\bundle\powerline\powerline\__init__.py", line 372, in render
return self.renderer.render(*args, **kwargs)
AttributeError: 'VimPowerline' object has no attribute 'renderer'
E860: Eval did not return a valid python 3 object
Traceback (most recent call last):
File "<string>", line 1, in <module>
File "C:\Users\kk\.vim\bundle\powerline\powerline\vim.py", line 145, in new_window
return self.render(window, window_id, winnr)
File "C:\Users\kk\.vim\bundle\powerline\powerline\__init__.py", line 372, in render
return self.renderer.render(*args, **kwargs)
AttributeError: 'VimPowerline' object has no attribute 'renderer'
E860: Eval did not return a valid python 3 object
Traceback (most recent call last):
File "<string>", line 1, in <module>
File "C:\Users\kk\.vim\bundle\powerline\powerline\vim.py", line 145, in new_window
return self.render(window, window_id, winnr)
File "C:\Users\kk\.vim\bundle\powerline\powerline\__init__.py", line 372, in render
return self.renderer.render(*args, **kwargs)
AttributeError: 'VimPowerline' object has no attribute 'renderer'
E860: Eval did not return a valid python 3 object

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

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

Re: vim not finding the end of the sql statement

As alternative you may want to give http://github.com/MarcWeber/vim-addon-sql a
try. Its minimalistic, simple. You either select sql statements
visually, or it will try to find the start/end automatically based on
empty lines or ;.

Marc Weber

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

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

Re: vim not finding the end of the sql statement




On Wed, May 29, 2013 at 5:36 PM, whytheq <whytheq@gmail.com> wrote:
In `gvim` if I put the cursor (normal mode) in the word SELECT and then hit `\se` then it runs ok:

    SELECT GETDATE();

If I do exactly the same but for a query over two lines then it errors.

    SELECT
    GETDATE();

I have the lastest version of dbext installed.


Another user (Jason) just reported this to me as well.

I will look into it in a couple of days.

As a work around and a more reliable option, I would use linewise visual mode (capital V) and visually select what you want executed and hit \se to execute that selection.

So when your cursor is on the line SELECT, use this combination:
V/;<cr>\se

Where <cr> is when you hit enter on the keyboard.


BTW, why post these questions on stackoverflow?  This is the Vim list and this is generally where all the plugin authors monitor.

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

Re: Why use relative line numbers?

Well - relative line numbers were introduced to solve a problem (navigating).

What do relative line numbers do?
+ they show you where the cursor is (you could miss this)
+ they allow to navigate using less keys

issues:
- they slow you down. If I open :h having 'relativenumbers' set on 9k is
signifcantly slower ! (at least for me having 230 lines)

I hope that this is a somewhat accurate description about pro/cons of
relativenumbers feature.

The alternative I proposed does not suffer from the slowness, and G j k
like movements could be made understanding 'lasts digits' only.

Anyway if you love it and already have a solution - then go for it.

Marc Weber

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

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

Re: Why use relative line numbers?

Hi Marc!

On Mi, 29 Mai 2013, Marc Weber wrote:

> If this would work nicely, would there be a reason to keep relative line
> numbers ?

Yes. We already have that option and functionality. I don't think, we
want to give it away again.

regards,
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/groups/opt_out.

Re: use of vim signs

diff --git a/runtime/doc/options.txt b/runtime/doc/options.txt
--- a/runtime/doc/options.txt
+++ b/runtime/doc/options.txt
@@ -5132,7 +5132,18 @@
characters are put before the number.
See |hl-LineNr| and |hl-CursorLineNr| for the highlighting used for
the number.
- When setting this option, 'relativenumber' is reset.
+ *number_relativenumber*
+ The number in front of the cursor line depends on the values of the
+ 'rnu' and 'nu' setting:
+
+ Option: 'nonu' 'nu' 'nonu' 'nu'
+ 'nornu' 'nornu' 'rnu' 'rnu'
+
+ Text:
+ |apple | 1 apple | 2 apple | 2 apple
+ |pear | 2 pear | 1 pear | 1 pear
+ |nobod[y] | 3 nobod[y] | 0 nobod[y] |3 nobod[y]
+ |there | 4 there | 1 there | 1 there

*'numberwidth'* *'nuw'*
'numberwidth' 'nuw' number (Vim default: 4 Vi default: 8)
@@ -5547,7 +5558,9 @@
characters are put before the number.
See |hl-LineNr| and |hl-CursorLineNr| for the highlighting used for
the number.
- When setting this option, 'number' is reset.
+
+ The number in front of the cursor line depends on the value of
+ 'number' and 'relativenumber' |number_relativenumber|.

*'remap'* *'noremap'*
'remap' boolean (default on)
diff --git a/src/option.c b/src/option.c
--- a/src/option.c
+++ b/src/option.c
@@ -7647,35 +7647,6 @@
}
#endif

- /* If 'number' is set, reset 'relativenumber'. */
- /* If 'relativenumber' is set, reset 'number'. */
- else if ((int *)varp == &curwin->w_p_nu && curwin->w_p_nu)
- {
- curwin->w_p_rnu = FALSE;
-
- /* Only reset the global value if the own value is set globally. */
- if (((opt_flags & (OPT_LOCAL | OPT_GLOBAL)) == 0))
- curwin->w_allbuf_opt.wo_rnu = FALSE;
- }
- else if ((int *)varp == &curwin->w_p_rnu && curwin->w_p_rnu)
- {
- curwin->w_p_nu = FALSE;
-
- /* Only reset the global value if the own value is set globally. */
- if (((opt_flags & (OPT_LOCAL | OPT_GLOBAL)) == 0))
- curwin->w_allbuf_opt.wo_nu = FALSE;
- }
- else if ((int *)varp == &curwin->w_allbuf_opt.wo_nu
- && curwin->w_allbuf_opt.wo_nu)
- {
- curwin->w_allbuf_opt.wo_rnu = FALSE;
- }
- else if ((int *)varp == &curwin->w_allbuf_opt.wo_rnu
- && curwin->w_allbuf_opt.wo_rnu)
- {
- curwin->w_allbuf_opt.wo_nu = FALSE;
- }
-
else if ((int *)varp == &curbuf->b_p_ro)
{
/* when 'readonly' is reset globally, also reset readonlymode */
diff --git a/src/screen.c b/src/screen.c
--- a/src/screen.c
+++ b/src/screen.c
@@ -2329,14 +2329,14 @@
if (len > w + 1)
len = w + 1;

- if (wp->w_p_nu)
+ if (wp->w_p_nu && !wp->w_p_rnu)
/* 'number' */
num = (long)lnum;
else
{
/* 'relativenumber', don't use negative numbers */
num = labs((long)get_cursor_rel_lnum(wp, lnum));
- if (num == 0)
+ if (num == 0 && wp->w_p_nu && wp->w_p_rnu)
{
num = lnum;
fmt = "%-*ld ";
@@ -3499,14 +3499,14 @@
long num;
char *fmt = "%*ld ";

- if (wp->w_p_nu)
+ if (wp->w_p_nu && !wp->w_p_rnu)
/* 'number' */
num = (long)lnum;
else
{
/* 'relativenumber', don't use negative numbers */
num = labs((long)get_cursor_rel_lnum(wp, lnum));
- if (num == 0)
+ if (num == 0 && wp->w_p_nu && wp->w_p_rnu)
{
num = lnum;
fmt = "%-*ld ";
@@ -10260,7 +10260,10 @@
int n;
linenr_T lnum;

- lnum = wp->w_buffer->b_ml.ml_line_count;
+ if (wp->w_p_rnu && !wp->w_p_nu)
+ lnum = wp->w_height;
+ else
+ lnum = wp->w_buffer->b_ml.ml_line_count;

if (lnum == wp->w_nrwidth_line_count)
return wp->w_nrwidth_width;
diff --git a/src/testdir/test89.ok b/src/testdir/test89.ok
--- a/src/testdir/test89.ok
+++ b/src/testdir/test89.ok
@@ -1,9 +1,9 @@
results:

-nonumber
+ number
relativenumber

-nonumber
+ number
relativenumber
:setlocal must NOT reset the other global value

@@ -12,11 +12,11 @@
relativenumber
:setglobal MUST reset the other global value

-nonumber
+ number

-norelativenumber
+ relativenumber
:set MUST reset the other global value

-nonumber
+ number

-norelativenumber
+ relativenumber
On Mi, 29 Mai 2013, Ben Fritz wrote:

> I like the proposal by "glts" myself:
>
> > - ":set nonu nornu" means: I don't want any line numbers;
> > - ":set nu nornu" means: I want to see only absolute numbers;
> > - ":set nonu rnu" means: I want to see only relative numbers;
> > - ":set nu rnu" means: I want to have the best of both worlds.
>
> Christian, what is the problem you have with this approach?

I think, this is confusing. But as I said, I don't have a strong opinion
on that, so here is a patch to try out:

regards,
Christian
--
Wie man sein Kind nicht nennen sollte:
Bill Jard

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

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

Re: Why use relative line numbers?

On Wednesday, May 29, 2013 4:46:30 PM UTC-5, MarcWeber wrote:
> ben, tim,
>
>
>
> Can you give this a try again:
>
> http://vim-wiki.mawercer.de/wiki/tips/goto-line-by-last-digits.html
>
>
>
> would using normal line numbers be fine this way if it was possible to
>
> pass 05?
>
>
>
> eg d3\G works now.
>
>
>
> not having relative line numbers is less confusing, because the numbers
>
> on the left don't change.
>
>
>
> If this would work nicely, would there be a reason to keep relative line
>
> numbers ?
>

As I mentioned before, J and _ and some other commands are much more useful to me with relative line numbers. And I like using them with dd, cc, yy, etc. these days, although I could change that to instead use the absolute numbers if I wanted.

In the beginning, relative line numbers also frequently took up less space than the absolute line numbers. That's no longer the case (as noted by much recent discussion).

I like the idea of your plugin and if relative line numbers were not around I'd probably use it. But as it stands now I don't mind sticking with relative numbering.

The other situation I use relative numbers a lot is when I'm recording macros to do a lot of stuff in a small range of lines. :set rnu can make it easier to get this right on the first try faster.

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

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

Re: Why use relative line numbers?

ben, tim,

Can you give this a try again:
http://vim-wiki.mawercer.de/wiki/tips/goto-line-by-last-digits.html

would using normal line numbers be fine this way if it was possible to
pass 05?

eg d3\G works now.

not having relative line numbers is less confusing, because the numbers
on the left don't change.

If this would work nicely, would there be a reason to keep relative line
numbers ?

Marc Weber

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

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

vim not finding the end of the sql statement

In `gvim` if I put the cursor (normal mode) in the word SELECT and then hit `\se` then it runs ok:

SELECT GETDATE();

If I do exactly the same but for a query over two lines then it errors.

SELECT
GETDATE();

I have the lastest version of dbext installed.

Why ?

Further discussion is here:
http://stackoverflow.com/questions/16802259/vim-not-finding-the-end-of-the-sql-statement

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

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

Re: Why use relative line numbers?

On 2013-05-29 12:29, Chris Lott wrote:
> But if I am on line 7 and see something on another line, I can just
> use 12gg or 12G to get there. And if I have relative numbering on,
> it messes with specifying ranges (as far as I can tell). Does
> relative numbering offer other efficiencies?

In small files, the differences are somewhat minor. However if
you're down in the bottom of a large file,

d5k

is considerably shorter than

d14159G

you can pretty much be guaranteed that your relative jump will be
capped at 2 digits (possibly 3 if your cursor line is at the
top/bottom of the screen you have a wide-screen monitor in portrait
mode, giving you more than 100 lines of text).

It's also just a matter of how your mind thinks.

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

Re: Why use relative line numbers?

On Wednesday, May 29, 2013 3:29:59 PM UTC-5, Chris Lott wrote:
> The discussion about relative line numbers raises the question (for
> me): why use relative line numbers at all?
>
> The main reason I keep reading is that instead of having to calculate
> how many lines one wants to move and then use, say, 5j to move there
> (or pressing j five times, yuck), one can immediately see that the
> desired line is 5 lines away.
>

Yes, also it's useful for things like 5dd (or d4j if you want no math at all).

> But if I am on line 7 and see something on another line, I can just
> use 12gg or 12G to get there.

It's more distracting if you get to 4 or more digits in the absolute line
number. I'd much rather do 3j than 54892G. And sometimes the linewise G/gg
command doesn't work for what I want anyway (but I can't think of any specific
examples).

> And if I have relative numbering on, it
> messes with specifying ranges (as far as I can tell). Does relative
> numbering offer other efficiencies?
>

You can use relative line numbers in ranges, so no problems there. E.g. replace
"foo" with "bar" from here to 5 lines down:

:.,.+5s/foo/bar/g

You can technically omit the . in most cases for efficiency but it's clearer
with in my opinion.

Some commands only work with relative numbers. For example, _ is mostly
synonymous with ^, but you can give it a count to also move to a different line
(at the beginning of the line). This count is (mostly) relative.

Other commands like J which take a count referring to number of lines, but don't
take motions at all, are more efficient with relative line numbering.

One unexpected use that I found is that Vim error messages give a line number
relative to the beginning of a function when a function throws the error.
Instead of counting lines I can cursor to the top of the function and see
exactly which line is at fault.

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

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

Why use relative line numbers?

The discussion about relative line numbers raises the question (for
me): why use relative line numbers at all?

The main reason I keep reading is that instead of having to calculate
how many lines one wants to move and then use, say, 5j to move there
(or pressing j five times, yuck), one can immediately see that the
desired line is 5 lines away.

But if I am on line 7 and see something on another line, I can just
use 12gg or 12G to get there. And if I have relative numbering on, it
messes with specifying ranges (as far as I can tell). Does relative
numbering offer other efficiencies?

c
--
Chris Lott <chris@chrislott.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/groups/opt_out.

Re: use of vim signs

On Wednesday, May 29, 2013 2:45:51 PM UTC-5, toothpik wrote:
> On Wed, May 29, 2013 at 11:48:05AM -0700, Ben Fritz wrote:
> > There are plenty of use cases where an absolute line number in the
> > relative column is very useful, and currently the only complaint is "it
> > makes my number column a few characters wider and I don't like that".
>
> I guess my 'redundant and distracting and mis-aligned' is chopped
> liver
>

No, it's useful feedback, but there are constraints on the solution:

1. Don't remove support for the line number in place of zero entirely
2. No new options specifically to control this feature

Personally I thought Bram pulled the trigger on than absolute line number thing before consensus was reached on how it should work. But patches speak louder than words either way.

I like the proposal by "glts" myself:

> - ":set nonu nornu" means: I don't want any line numbers;
> - ":set nu nornu" means: I want to see only absolute numbers;
> - ":set nonu rnu" means: I want to see only relative numbers;
> - ":set nu rnu" means: I want to have the best of both worlds.

Christian, what is the problem you have with this approach?

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

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

Re: use of vim signs

On Wed, May 29, 2013 at 11:48:05AM -0700, Ben Fritz wrote:
> On Wednesday, May 29, 2013 10:31:20 AM UTC-5, toothpik wrote:
> >
> > ok, looking at the code it's a simple change in two places in screen.c
> > (lines 2339 and 3509) to get the current line number back to zero when
> > in relativity mode

> Maybe, but this was specifically added as a feature so I doubt it will get
> reverted.

> I certainly prefer the line number instead of zero.

> > my personal opinion would be to have the default for rnu0 to be on, but
> > we should vote on that, with Bram as the decider since most people won't
> > care or vote

> In the vim_dev thread Christian mentioned (
> https://groups.google.com/group/vim_dev/msg/194c62c57ddf9ee9 ) Bram
> already said explicitly that he didn't want another option for this.

well that's a show-stopper for me -- I was trying to share the "best"
solution with the community

going forward, I will keep my screen.c with my own mods for my taste,
along with my changes to feature.h -- the extent of my gift to the
community will have to be those line numbers in screen.c -- if you
feel as I do, go there and whack or comment those 5 lines (followed by
a commit, a merge to the previous head, and another commit)

> > (when I first expressed enthusiasm for relative numbers they showed the
> > zero, not some misaligned line number that's repeated in the ruler -- it
> > looks suspiciously like something that was snuck in my someone just
> > showing off (looky what I can do!))

> It wasn't. It was a "the zero is useless; let's display some useful
> information there instead" argument with lots of discussion.

I must have been asleep or distracted -- my bad -- to me the zero is
simply what belongs there

> Not everybody shows the line number in their status line or ruler, or
> shows either of those things at all, and they may want to be able to see a
> line number still. Or in my case, I may have so many open windows that the
> line number in the status line is much harder to pick out than if I just
> scan over to the left on my current line. Or maybe the statusline setting
> is such that line numbers get truncated on narrow windows. Additionally,
> when Vim doesn't have input focus (for referring to line numbers in an
> email or something), you can't even ":set number" easily to see line
> numbers in your window. My solution to this is a FocusLost autocmd but
> that pre-dated the line number at the cursor line in relativenumber mode.
> Perhaps I would have just used that (and mentally added or subtracted the
> line number) were it available before I made my FocusGained/FocusLost
> autocmds.

> There are plenty of use cases where an absolute line number in the
> relative column is very useful, and currently the only complaint is "it
> makes my number column a few characters wider and I don't like that".

I guess my 'redundant and distracting and mis-aligned' is chopped
liver

> How about a different solution? We could modify the behavior of that
> absolute number, to make it so that one absolute numbered line isn't
> allowed to expand the line number column. If it won't fit, show zero or
> truncate it with < like in the statusline or something. If a user wants to
> show it anyway they can increase their 'numberwidth' option.

my problem isn't with the width, and I think the code is complicated
enough -- if we're going to show the number, I think we should show
all of it

> I was going to see what happens to the normal line number column when the
> limit of width 10 is reached, but Vim has been chugging away for almost an
> hour trying to load a 3GB file (I let a cmd.exe "for" loop run for a while
> to create a huge file with nothing but DOS-style line endings); even with
> no plugins, eventignore set to "all", undolevels set to -1, and using the
> :view command to avoid a swap file. So I think I'll give up on waiting for
> that.

and I also will give up on my misguided attempt to modify vim for
everybody -- I will simply modify it for me

I apologize for the noise

--
_|_ _ __|_|_ ._ 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/groups/opt_out.

Re: Thread safety not mentioned for python bindings


On May 19, 2013 5:01 PM, "Zhao Cai" <zhaocai@gmx.com> wrote:
>
> I tried to make some vim function calls from python thread. Some of the functions like `taglist()` are working but I am not sure if it is safe. Can anyone who knows this part of code give an "official" answer? Thanks!

This code is not thread-safe. Vim is using globals for a large variety of purposes and it is better not to run any code from non-main thread. User-defined functions are the worst candidates for such call; with built-in ones you will be lucky more more often, but still it is better to avoid calling vim from the separate thread.

In if_py_both there are some functions which as far as I see are a placeholders for Vim GIL, but they are only the placeholders lacking actual implementation in vim core (and if there was GIL if_py_both.h is a wrong place to define such functions). And they are not used in code I added.

> On Oct 24, 2012, at 4:57 PM, Timothy Madden <terminatorul@gmail.com> wrote:
>
> > Hello
> >
> > I read the python bindings help file (if_python.txt) and I found nothing about thread safety. Although Vim itself does not use threads, the invoked python code can create them and than the main thread can return control to Vim normally. I would like to write a plug-in that listens to a TCP connection in the background, and somehow notifies Vim when new data arrives on the socket.
> >
> > Now, since the documentation says nothing about it, I would assume the python language bindings are not thread-safe, or even if they are thread-safe, that is still an undocumented feature. But does anyone have more specific information please ? Has anyone tried working with treads from python code in Vim ? Can the help file be updated to mention this aspect ?
> >
> > Thank you,
> > Timothy Madden
> >
> > --
> > You received this message from the "vim_use" maillist.
> > Do not top-post! Type your reply below the text you are replying to.
> > For more information, visit http://www.vim.org/maillist.php
>
> --
> --
> You received this message from the "vim_use" maillist.
> Do not top-post! Type your reply below the text you are replying to.
> For more information, visit http://www.vim.org/maillist.php
>
> ---
> You received this message because you are subscribed to the Google Groups "vim_use" group.
> To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
> For more options, visit https://groups.google.com/groups/opt_out.
>
>

--
--
You received this message from the "vim_use" maillist.
Do not top-post! Type your reply below the text you are replying to.
For more information, visit http://www.vim.org/maillist.php
 
---
You received this message because you are subscribed to the Google Groups "vim_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.