[bug] NFA regexp engine: grouping, back references

2014-02-03 Fir de Conversatie Lech Lorens
Might be related to the other NFA bug reported today. The below script creates a file with 40 lines of the following format: This is line 3 of block 2. (there are 10 blocks numbered from 0 to 9 with lines from 0 to 3). It also tries to find all the last lines of the blocks (i.e. lines where

Issue 197 in vim: ]P does not paste over visually selected line

2014-02-03 Fir de Conversatie vim
Status: New Owner: Labels: Type-Defect Priority-Medium New issue 197 by chr...@coosto.nl: ]P does not paste over visually selected line http://code.google.com/p/vim/issues/detail?id=197 What steps will reproduce the problem? 1. Start up vim vim --noplugin -u NONE Execute the

How to see exactly what system() command Vim executes?

2014-02-03 Fir de Conversatie boss
Hello! I've been researching how best to escape system() commands. So far, in order to find out what string Vim constructs and passes to the shell, I've been setting `verbose` to 4 and looking at the 'Calling shell to execute: ...' output in `:messages`. However I'm beginning to wonder

Re: [BUG] :unlet $ENV does not work

2014-02-03 Fir de Conversatie LCD 47
On 2 February 2014, Gary Johnson garyj...@spocom.com wrote: I've been frustrated by Vim's inability to unset environment variables on occasion, too. I don't know what systems would not support this. IIRC, SysV had putenv(3), while BSD had setenv(3). The latter had a corresponding

Re: [BUG] :unlet $ENV does not work

2014-02-03 Fir de Conversatie ZyX
You mean SysV does not have C function for unsetting environment? I guess this is why zsh has coded direct environ global manipulations (controlled by USE_SET_UNSET_ENV). We can probably borrow code from there. I cannot say though in which systems **environ is supported, but both bash and

Re: Sleep mispositions cursor when there are splits

2014-02-03 Fir de Conversatie Charles Cooper
On Saturday, February 1, 2014 9:11:51 AM UTC-5, Christian Brabandt wrote: Can you see, if this patch fixes it for you? Yes, in patched vim the cursor does not jump with :sleep. I am trying to come up with a script that would better show the original problem of having the cursor be restored

Re: [BUG] :unlet $ENV does not work

2014-02-03 Fir de Conversatie LCD 47
On 3 February 2014, ZyX zyx@gmail.com wrote: IIRC, SysV had putenv(3), while BSD had setenv(3). The latter had a corresponding unsetenv(3), while the former didn't. On my Ubuntu Linux system, the unsetenv(3) man page says that it conforms to 4.3BSD and POSIX.1-2001.

vim RHEL 5.9

2014-02-03 Fir de Conversatie nag
Hi, I am working on RHEL 5.9 systems. The default installed vim editor is not working fully. My problems: No syntax highlighting. No cursor position display No column and row numbers. No visual selection (visual block, ctrl+v) cursor is not appearing at last saved position. Unable to open

Re: [BUG] :unlet $ENV does not work

2014-02-03 Fir de Conversatie LCD 47
On 3 February 2014, LCD 47 lcd...@gmail.com wrote: On 3 February 2014, ZyX zyx@gmail.com wrote: IIRC, SysV had putenv(3), while BSD had setenv(3). The latter had a corresponding unsetenv(3), while the former didn't. On my Ubuntu Linux system, the unsetenv(3) man page says

Bug: vim can contract but not expand

2014-02-03 Fir de Conversatie Suresh Govindachar
Hello, Steps to reproduce bug on Windows 7, 64 bit, Official big version of vim.exe: 1) Create a file, foo.vim, as follows: set laststatus=2 augroup ReSizingReporter autocmd VimResized * echomsg c: columns l: lines augroup END 2) Start cmd.exe. Right-click on top bar

Re: Bug: vim can contract but not expand

2014-02-03 Fir de Conversatie LCD 47
On 3 February 2014, Suresh Govindachar sgovindac...@yahoo.com wrote: Hello, Steps to reproduce bug on Windows 7, 64 bit, Official big version of vim.exe: 1) Create a file, foo.vim, as follows: set laststatus=2 augroup ReSizingReporter autocmd VimResized * echomsg c:

Re: [BUG] :unlet $ENV does not work

2014-02-03 Fir de Conversatie ZyX
A quick search reveals this: http://www.greenend.org.uk/rjk/tech/putenv.html According to this guy unsetenv() was added in Solaris 5.10, which is now ~10 years old. On Solaris you could modify *environment directly, but IIRC on OSF/1 that was explicitly forbidden. Then I

Re: [BUG] :unlet $ENV does not work

2014-02-03 Fir de Conversatie LCD 47
On 3 February 2014, ZyX zyx@gmail.com wrote: There are some questions about memory: do I read correctly that not to leak memory you must keep track which environment variables you have set with putenv() and run `vim_free((getenv(VAR)[-STRLEN(VAR)-1]));` just before you are about to use

Re: vim RHEL 5.9

2014-02-03 Fir de Conversatie Gary Johnson
On 2014-02-03, nag wrote: Hi, I am working on RHEL 5.9 systems. The default installed vim editor is not working fully. My problems: No syntax highlighting. No cursor position display No column and row numbers. No visual selection (visual block, ctrl+v) cursor is not appearing at last

argisglobal patch

2014-02-03 Fir de Conversatie Marcin Szamotulski
Hello, I wrote a small patch which adds argisglobal() function which returns 1 if the current buffer has global arglist otherwise, if there is a local arg list it return 0. I haven't found any other way to test if the arglist is gobal/local. I've been using this patch for some time already (I

Re: argisglobal patch

2014-02-03 Fir de Conversatie Marcin Szamotulski
On 18:48 Mon 03 Feb , Marcin Szamotulski wrote: Hello, I wrote a small patch which adds argisglobal() function which returns 1 if the current buffer has global arglist otherwise, if there is a local arg list it return 0. I haven't found any other way to test if the arglist is

Window-local options and hidden buffers

2014-02-03 Fir de Conversatie parcs
Hi, I'm observing an inconsistency with the way changes window-local options are propagated to buffers, depending on whether the particular buffers are marked 'hidden' or not. Specifically, the inconsistency is that changes to window-local options such as 'list' and 'nolist' do not affect

Re: [bug] NFA regexp engine: grouping, back references

2014-02-03 Fir de Conversatie Bram Moolenaar
Lech Lorens wrote: Might be related to the other NFA bug reported today. The below script creates a file with 40 lines of the following format: This is line 3 of block 2. (there are 10 blocks numbered from 0 to 9 with lines from 0 to 3). It also tries to find all the last lines of the

ENABLE_WINDOW_INPUT flag

2014-02-03 Fir de Conversatie Suresh Govindachar
Hello, I am told that ENABLE_WINDOW_INPUT is disabled for xterm. Why is this being done? Thanks, --Suresh -- -- You received this message from the vim_dev maillist. Do not top-post! Type your reply below the text you are replying to. For more information, visit

Re: ENABLE_WINDOW_INPUT flag

2014-02-03 Fir de Conversatie John Little
On Tuesday, February 4, 2014 4:26:07 PM UTC+13, Suresh Govindachar wrote: I am told that ENABLE_WINDOW_INPUT is disabled for xterm. Why is this being done? Is that the question you meant to ask? ENABLE_WINDOW_INPUT is some win32 API flag; it's not used with xterm. Or are you bumping your