Re: Vim takes a lot of time opening buffers when opening a file for the first time

2013-08-20 Thread florian . wagner
SOLVED! Thank you all four your help! VIMs in-house profiling function (this was new to me) helped to identify the bottleneck: FUNCTIONS SORTED ON TOTAL TIME count total (s) self (s) function 1 1.911840 0.000174 sy#start() 1 1.911471 0.000904 sy#repo#detect() 2

Re: Certain commands undock shift window

2013-08-20 Thread AndyHancock
On Mon, Aug 19, 2013 at 12:42 PM, Dan Wierenga wrote: On Sat, Aug 17, 2013 at 6:18 PM, AndyHancock wrote: I Windows 7, when I have the gvim windows docked against the right or left half of the screen, the following commands always seem undock the window and shifts the position: * tab split

Re: Vim takes a lot of time opening buffers when opening a file for the first time

2013-08-20 Thread Florian M. Wagner
Hey Ben, I removed the .viminfo (1500 lines) and set viminfo=NONE but it did not change anything. I do not open any network files. Am 19.08.2013 23:58, schrieb Ben Fritz: On Monday, August 19, 2013 3:55:03 PM UTC-5, Christian Brabandt wrote: On Mo, 19 Aug 2013, florian.wag...@rwth-aachen.de

Re: Mapping *-CR

2013-08-20 Thread John Little
On Tuesday, August 20, 2013 9:14:56 AM UTC+12, Gautier DI FOLCO wrote: I should mention that terminals are strange beasts. Documentation can be confusing and can conflict with empirically determined behavior. A plug for xterm. xterm is well maintained by Thomas Dickey, who has been seen on

How to inspect command executed by system(expr, input)?

2013-08-20 Thread Andrew Stewart
Hello, I am using `system(expr, input)` to run an external command. However some users have reported a problem and I would like to see exactly what command `system()` is constructing and executing. The help docs for `system()` state that the command is constructed like this: 'shell'

Re: How to inspect command executed by system(expr, input)?

2013-08-20 Thread Christian Brabandt
On Tue, August 20, 2013 12:01, Andrew Stewart wrote: Hello, I am using `system(expr, input)` to run an external command. However some users have reported a problem and I would like to see exactly what command `system()` is constructing and executing. The help docs for `system()` state that

Re: How to inspect command executed by system(expr, input)?

2013-08-20 Thread Andrew Stewart
On 20 Aug 2013, at 14:46, Christian Brabandt cbli...@256bit.org wrote: If I recall correctly, simply set the verbose level to 5 and Vim will output the exact command it is executing. It does indeed. Thanks! -- -- You received this message from the vim_use maillist. Do not top-post! Type

Re: Stay in insert mode when using cursor keys

2013-08-20 Thread Ben Fritz
On Monday, August 19, 2013 7:57:37 PM UTC-5, Alan wrote: On Saturday, August 17, 2013 7:29:22 PM UTC-7, Tony Mechelynck wrote: On 08/18/13 00:31, Alan wrote: Very many thanks for all the detail! That's a great help and I'll be able to figure it out now (probably). There is no

Re: Vim takes a lot of time opening buffers when opening a file for the first time

2013-08-20 Thread Ben Fritz
On Tuesday, August 20, 2013 1:51:06 AM UTC-5, florian...@rwth-aachen.de wrote: SOLVED! Thank you all four your help! VIMs in-house profiling function (this was new to me) helped to identify the bottleneck: FUNCTIONS SORTED ON TOTAL TIME count total (s) self (s) function 1

Re: Vim takes a lot of time opening buffers when opening a file for the first time

2013-08-20 Thread Florian M. Wagner
Am 20.08.2013 16:24, schrieb Ben Fritz: On Tuesday, August 20, 2013 1:51:06 AM UTC-5, florian...@rwth-aachen.de wrote: SOLVED! Thank you all four your help! VIMs in-house profiling function (this was new to me) helped to identify the bottleneck: FUNCTIONS SORTED ON TOTAL TIME count total

LaTeX lstlisting.

2013-08-20 Thread srizzi
I'm a gVim user in Win 7. In gVim 7.3 LaTeX lstlisting was recognised and rendered the same as verbatim. In gVim 7.4 lstlisting is not recognised and it's rendered in various (more or less random) colors. This problem it's independent from the color theme. Where I was wrong? -- -- You

Re: LaTeX lstlisting.

2013-08-20 Thread Charles Campbell
srizzi wrote: I'm a gVim user in Win 7. In gVim 7.3 LaTeX lstlisting was recognised and rendered the same as verbatim. In gVim 7.4 lstlisting is not recognised and it's rendered in various (more or less random) colors. This problem it's independent from the color theme. Where I was wrong?

Basic calculation in Vim

2013-08-20 Thread tjg
I have written a small function which puts WIP statistics at the end of the file (pure text, no code) I am working on. It looks like this (ts = 7) Date NbCar NbWords NbSent NbLines 130813 21910 3640 310 180 130820 30310 5210 480 220 (NB : Date in the ymd format,

Re: Basic calculation in Vim

2013-08-20 Thread Tim Chase
On 2013-08-20 09:16, tjg wrote: Date NbCar NbWords NbSent NbLines 130813 21910 3640 310 180 130820 30310 5210 480 220 This function works. But I would like to add 2 columns : - one about the final output : divide the NbCar by 1500 (in France a journalistic

Re: Certain commands undock shift window

2013-08-20 Thread Dan Wierenga
On Tue, Aug 20, 2013 at 12:10 AM, AndyHancock andymhanc...@gmail.comwrote: The trick for docking a window from the keyboard is neat. Unfortunately (well, just for me, that is), I will still have use the mouse since I actually adjust the window after docking to be skinnier than half the width

Re: Basic calculation in Vim

2013-08-20 Thread tooth pik
On Tue, Aug 20, 2013 at 09:16:20AM -0700, tjg wrote: I have written a small function which puts WIP statistics at the end of the file (pure text, no code) I am working on. It looks like this (ts = 7) Date NbCar NbWords NbSent NbLines 130813 21910 3640 310 180 130820

Re: Basic calculation in Vim

2013-08-20 Thread tjg
@TimChase : thanks for your answer, but I run into an error E20 : Mark not set. I must have made a mistake (I put the cursor on the second data line and ran your command : was I supposed to do that, or must I insert something like :2,3','s etc...?). About the floating point, I will be very

Re: Basic calculation in Vim

2013-08-20 Thread tjg
@ToothPick : thanks for your answer, but I do not use awk, because I confess I do not have it on my device (Android, with only VimTouch, which can be quite efficient if you take into account that you can dictate your text and dictate it anywhere). Nevertheless, thank you very much for your

Re: Basic calculation in Vim

2013-08-20 Thread Ben Fritz
On Tuesday, August 20, 2013 11:16:20 AM UTC-5, tjg wrote: - one about the final output : divide the NbCar by 1500 (in France a journalistic feuillet/page, I do not know if there is an equivalent elsewhere) ; here it would indicate that a week ago I had written 15 feuillets (rounded

Re: Basic calculation in Vim

2013-08-20 Thread Tim Chase
On 2013-08-20 12:19, tjg wrote: @TimChase : thanks for your answer, but I run into an error E20 : Mark not set. I must have made a mistake (I put the cursor on the second data line and ran your command : was I supposed to do that, or must I insert something like :2,3','s etc...?). I'd

Re: Basic calculation in Vim

2013-08-20 Thread tjg
@TimChase : it works perfectly, of course (I use visual mode very seldom, as you can guess...). Thanks you very much. -- View this message in context: http://vim.1045645.n5.nabble.com/Basic-text-statistics-calculation-in-Vim-tp5717021p5717029.html Sent from the Vim - General mailing list

Re: Basic calculation in Vim

2013-08-20 Thread tjg
@BenFritz : thank you for your answer, but I face a problem : I proceeded as you told me, but ended - in insert mode - with 30310.0/1500 ... Sorry, but I must have misunderstood part of the process. -- View this message in context:

Re: Basic calculation in Vim

2013-08-20 Thread Christian Brabandt
On Di, 20 Aug 2013, tjg wrote: I have written a small function which puts WIP statistics at the end of the file (pure text, no code) I am working on. It looks like this (ts = 7) Date NbCar NbWords NbSent NbLines 130813 21910 3640 310 180 130820 30310 5210 480

Disable swap file for large files?

2013-08-20 Thread skeept
Is there a way of enabling swap files for files say less than 10Mb but disabling swap files for files or larger sizes? 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

Re: Basic calculation in Vim

2013-08-20 Thread Ben Fritz
On Tuesday, August 20, 2013 3:21:33 PM UTC-5, tjg wrote: @BenFritz : thank you for your answer, but I face a problem : I proceeded as you told me, but ended - in insert mode - with 30310.0/1500 ... Sorry, but I must have misunderstood part of the process. Nope, I accidentally omitted a

Re: Disable swap file for large files?

2013-08-20 Thread Ben Fritz
On Tuesday, August 20, 2013 4:27:51 PM UTC-5, skeept wrote: Is there a way of enabling swap files for files say less than 10Mb but disabling swap files for files or larger sizes? Thanks, Jorge Start with them globally disabled. On a BufRead autocmd, set it to enabled (locally), if

Disable swap file for large files?

2013-08-20 Thread John Little
Use the LargeFile plugin, it does exactly that. One can set a variable in your.vimrc to set the threshold; it defaults to 20 MB. Regards, John Little -- -- You received this message from the vim_use maillist. Do not top-post! Type your reply below the text you are replying to. For more

strange behavior: :w only writes new buffers to disk, not open them.

2013-08-20 Thread leo
Hello all, I have changed my .vimrc quite a bit recently. I do not know exactly when, but when a create new buffer, for instance :w test.txt, vim only writes/creates the file test, but it no longer opens it by default. Is there any option that controls that? I'm using macvim Thanks in

Re: strange behavior: :w only writes new buffers to disk, not open them.

2013-08-20 Thread Tim Chase
On 2013-08-20 18:16, leo wrote: when a create new buffer, for instance :w test.txt, vim only writes/creates the file test, but it no longer opens it by default. Is there any option that controls that? I'm not quite sure I understand what you mean by no longer opens it by default. Based on my

Re: strange behavior: :w only writes new buffers to disk, not open them.

2013-08-20 Thread Leonardo Barbosa
Thanks Tim, a) I'm talking about the first one. b) :version VIM - Vi IMproved 7.3 (2010 Aug 15, compiled Jul 27 2011 19:46:24) MacOS X (unix) version c) vim -u NONE makes vim works as expected. what do you think? Leo On Tue, Aug 20, 2013 at 10:34 PM, Tim Chase v...@tim.thechases.com wrote:

Re: strange behavior: :w only writes new buffers to disk, not open them.

2013-08-20 Thread Tim Chase
On 2013-08-20 23:02, Leonardo Barbosa wrote: c) vim -u NONE makes vim works as expected. then I'd start binary-searching your vimrc by putting finish halfway through. If it still works, move it to 75% of the way through; otherwise, move it to 25% of the way through. By cutting your vimrc