Re: How about a release?

On 3/18/2018 7:48 AM, Bram Moolenaar wrote: Justin M. Keyes wrote: I'm glad to give credits to developers who send me a patch that I can include and make Vim users happy. No matter where that code came from. Why give credit to NeoVim as a project, instead of its individual contributors? That

Re: [patch] neovim patches

On 3/7/2017 4:10 PM, Nikolay Aleksandrovich Pavlov wrote: 2017-03-08 1:14 GMT+03:00 Bram Moolenaar : Nikolay Pavlov wrote: 2017-03-05 16:56 GMT+03:00 Bram Moolenaar : Justin M. Keyes wrote: On Sat, Mar 4, 2017 at 10:10 PM, Christian Brabandt

Re: Patch for quickfix.txt

On 3/6/2017 2:02 PM, Bram Moolenaar wrote: Suresh Govindachar wrote: On 3/6/2017 6:17 AM, 'Suresh Govindachar' via vim_dev wrote: [...] Thanks. Let's use backticks for commands and add a few commas: [...] Attached. --Suresh -- -- You received this message from the "vim_dev" ma

Re: Patch for quickfix.txt

On 3/6/2017 6:17 AM, 'Suresh Govindachar' via vim_dev wrote: Attached patch to quickfix.txt is thanks to Tony Mechelynck. Updates to patch: minor wording changes; and now jumpable help tags are enclosed in ||. -- -- You received this message from the "vim_dev" maillist. Do no

Patch for quickfix.txt

Attached patch to quickfix.txt is thanks to Tony Mechelynck. --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 http://www.vim.org/maillist.php --- You received this message

Re: A nice mapping for the Kings' Day (or Old-Style Christmas, or whatever)

On 1/7/2016 2:06 PM, Tony Mechelynck wrote: This assumes 'nocompatible' if exists(':map') == 2 && exists(':smile') == 2 nnoremap :intexe "smi" endif Have fun! > ... I checked gvim/vim on Windows and Ubuntu (14.x), and while both had 'nocompatible' and ':map', neither has ':smile'.

Re: ENABLE_WINDOW_INPUT flag

On 2/3/2014 10:25 PM, John Little wrote: 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

Bug: vim can contract but not expand

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

ENABLE_WINDOW_INPUT flag

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: [Bulk] Re: NOlazyredraw and need for Ctrl-l (or :redraw!): provide any clue for bug with vim inside ConEmu?

On 1/16/2014 10:24 AM, Maximus ConEmu wrote: On Thursday, January 16, 2014 10:05:58 AM UTC+4, Suresh Govindachar wrote: When running vim inside ConEmu, although lazyredraw is OFF (nolazydraw), I still find the need to hit Ctrl-L or execute :redraw! (with shriek) to clear up the screen

NOlazyredraw and need for Ctrl-l (or :redraw!): provide any clue for bug with vim inside ConEmu?

Hello, When running vim inside ConEmu, although lazyredraw is OFF (nolazydraw), I still find the need to hit Ctrl-L or execute :redraw! (with shriek) to clear up the screen that has been messed-up by some bug with using Vim inside ConEmu (

Re: Feature request: flag to 'complete' so that i_Ctrl-N ignores remote buffers

On 11/13/2013 6:03 AM, Christian Brabandt wrote: On Tue, November 12, 2013 16:53, Ben Fritz wrote: On Monday, November 11, 2013 10:45:15 PM UTC-6, Suresh Govindachar wrote: Hello, Please consider providing the feature whereby i_Ctrl-N would ignore buffers whose name begins

Feature request: flag to 'complete' so that i_Ctrl-N ignores remote buffers

Hello, Please consider providing the feature whereby i_Ctrl-N would ignore buffers whose name begins with \\machine_name\ and machine_name is a remote machine (Microsoft Uniform Naming Convention (UNC)). Thanks, --Suresh -- -- You received this message from the vim_dev maillist. Do not

Re: Patch 7.3.1209

On 6/16/2013 7:14 AM, Bram Moolenaar wrote: Patch 7.3.1209 Problem:No completion for :tabdo. Solution: Add tabdo to the list of modifiers. (Dominique Pelle) Files:src/ex_docmd.c In April 2013, I had reported a bug in command line completion: Command line completion doesn't

Re: Plans for Vim 7.4

--- On Wed, 5/8/13, Christian J. Robinson hept...@gmail.com wrote: From: Christian J. Robinson hept...@gmail.com Subject: Re: Plans for Vim 7.4 To: vim_dev@googlegroups.com Date: Wednesday, May 8, 2013, 9:01 PM [Replied only to the Vim Developers' list.] On Thu, 9 May 2013, Bram

Re: Command line completion doesn't use . and ,, in path: Bug?

On 4/14/2013 10:56 PM, Nazri Ramliy wrote: Hi Suresh! On Mon, Apr 15, 2013 at 10:22 AM, Suresh Govindachar sgovindac...@yahoo.com wrote: Hitting tab after entering a partial argument to :find will offer suggestions for completing the command line by searching inside non

Command line completion doesn't use . and ,, in path: Bug?

Hello, Hitting tab after entering a partial argument to :find will offer suggestions for completing the command line by searching inside non-trivial components of the 'path' -- but it does not search in . and in ,, components of the path. Here's what I see: On vim's command line, the

vimgrep and Vim's connection with google

Hello, Tools such as tags, cscope, global, idutils etc. for spelunking code essentially involve creating an index of the files in the project and using this index. Tools like vim's :vimgrep work harder without the benefit of an index. Some of the tools are restricted to C code only (with maybe

Why can't CR be eaten while concealing?

Hello, When a string is concealed, characters in the string along each line are replaced by nothing; but any CRs in the string remain as CRs. Why is the design this way? If it is possible to make conceal remove any CRs in the string being concealed, please consider offering this feature.

RE: Building for Windows 7 64 bit with 64 bit dynamic perl

A short time ago, I wrote: At present, I am downloading vim sources (using mercurial) with the view to using MinGW 64 to build for Windows 7 64 bit, huge version with OLE and with support for dynamic perl 64 bit version 5.12. I am planning to use Make_ming.mak. Are there any

Build error about --with-tlib

Hello, How would I fix the following error message I get when tying to build vim on fedora core 8 linux (#1 SMP Thu Dec 18 19:19:45 EST 2008 i686 i686 i386 GNU/Linux), using the vim72 sources?: checking whether time.h and sys/time.h may both be included... yes checking for ino_t... yes

RE: Build error about --with-tlib

On the vim user mailing list, Benjamin R. Haskell explained the issue: On Sat, 27 Feb 2010, Suresh Govindachar wrote: [...] I tried 3 ways to install vim-with-everything on Fedora Core 8, but failed: Attempt 1) vim-7.2.tar.bz2 - typing make resulted in the following

RE: Installing Vim on Vista (Was: )

There is a known issue with things working on Vista having to do the _access() function. For example, the application gcc uses _access() to find other tools such as cc1.exe and the usual gcc fails on Vista -- the usual gcc needs to be patched to work on Vista. If VIM uses _access()

How to tell vim about new shell and new console (terminal)?

Here's what MicroSoft is up to for console/terminal: http://www.powershell.com/plus/ Weird that that thing seems to still have only 16 colors! It is possible to try out PowerShell (a shell, not a console/terminal) today. Commands in PowerShell do not move text data via pipes;

RE: patch to if_perl.xs

The terser version looks OK to me. --Suresh --~--~-~--~~~---~--~~ You received this message from the vim_dev maillist. For more information, visit http://www.vim.org/maillist.php -~--~~~~--~~--~--~---

RE: Buffer names -- efficiency (or inefficiency bug)

Bram asked for a reproduciable example: Version: VIM - Vi IMproved 7.1 (2007 May 12, compiled May 12 2007 14:19:39) MS-Windows 32 bit GUI version with OLE support Compiled by [EMAIL PROTECTED] Big version with GUI. Features included (+) or not (-): Steps: a)

RE: svn/cvs checkout hangs

Edward L. Fox wrote: svn co https://vim.svn.sourceforge.net/svnroot/vim/vim7 vim7_svn Well, although Bram recommended to checkout from /svnroot/vim/vim7, I'm regretful to say, you may encounter a circumstance that all files in your svn working directory being deleted after

Patch for if_perl.xs

Patch for if_perl.xs attached below. --Suresh *** vim7\src\if_perl.xs Tue Sep 04 17:12:39 2007 --- patched\if_perl.xsTue Sep 04 16:28:12 2007 *** *** 40,45 --- 40,67 #define PERL_SUBVERSION SUBVERSION #endif + /* + *

RE: Build broken -- Undefined references -- MinGW, vim with perl

.dll gurus, Latest response from Jan Dubois of ActiveState: On Fri, 24 Aug 2007, Suresh Govindachar wrote: Sisyphus suggested linking with C:/opt/perl/lib/CORE/perl58.lib (which does have the symbols in it) in the command that creates if_perl.o and/or in the command that builds

RE: Build broken -- Undefined references -- MinGW, vim with perl

Earlier, I asked the dll gurus, Latest response from Jan Dubois of ActiveState: On Fri, 24 Aug 2007, Suresh Govindachar wrote: Sisyphus suggested linking with C:/opt/perl/lib/CORE/perl58.lib (which does have the symbols in it) in the command that creates if_perl.o

RE: Build broken -- Undefined references -- MinGW, vim with perl

Solved with help from Brian Dessent on the MinGW mailing list. Add -lperl58 at the very end (location matters) of the last command. --Suresh --~--~-~--~~~---~--~~ You received this message from the vim_dev maillist. For more information, visit

Shortcoming of if_perl.xs

cc: Sven Verdoolaege -- where are you? Jan Dubois of ActiveState points out an issue with if_perl.xs: Jan Dubois wrote: On Mon, 27 Aug 2007, Suresh Govindachar wrote: So ActiveState is exporting Perl_sv_2iv_flags and Perl_newXS_flags in a way that is different from the way

Build broken -- Undefined references -- MinGW, vim with perl

Hello, Attached below is the result of issuing the following command (command has been written in multiple lines to make it easy to read): C:\home\suresh\develop\vim\vim7\src c:\opt\mingw\bin\mingw32-make.exe -f Make_ming.mak FEATURES=HUGE DEBUG=no GUI=yes

Make clean does not remove if_perl.c

Hello, make -f Make_ming.mak clean does not remove if_perl.c Thanks, --Suresh --~--~-~--~~~---~--~~ You received this message from the vim_dev maillist. For more information, visit http://www.vim.org/maillist.php

Re: Build broken -- Undefined references -- MinGW, vim with perl

[Yongwei Wu drew attention to if_perl.c] Make clean was not removing an earlier, bad if_perl.c. In the output I reported, if_perl.c was size 0. I manually deleted if_perl.c, and now get other errors. Before telling what the errors were, here's more background info: It is a

RE: Build broken -- Undefined references -- MinGW, vim with perl

Tony suggested looking at other builds -- however, I have been getting sources and building by own vim for over a year. My hard-drive crashed; have a new hard-drive. I am doing the exact same thing I used to do -- expcept I now have the latest release of ActiveState perl and

BadSpell not grouped properly?

Hello, Invoking he following command -- when N is 0 or 1: :echo synIDattr(synID(line(.), col(.), N), name) when the cursor is on the badly spelled word ontiger int foo; /* this is an ontiger */ results in the same answer cComment. Should it not respond as BadSpell?

RE: dynamic programming for gq formatting

Ismo Puustinen mentioned: I recently wrote an implementation of the optimal line breaking algorithm (in Ruby). If you are interested, the file is located here, with a small piece of test code at the end: http://lissujaismo.net/rbpar/rbpar_engine.rb You can run the test

Pseudo-verbosity of was set in error handler

Hello, The following response to :verbose set foo? was set in error handler is not informative. To be informative, the message should mention something to indicate who/what/when/where was trying to set the illegal value. For example, I have been using a valid

RE: there's undojoin -- how about dotjoin?

Tony asked: Bram Moolenaar wrote: How about using CTRL-G CTRL-O for going to Normal mode without breaking the current Insert in two? It would only work when the cursor didn't move and the text isn't changed. I don't find Ctrl-G Ctrl-O under :help ins-special-special

RE: Working of [I

Earlier, I asked: I am not curious about how [I finds the files to look into. What I would like to know is what [I does inside each file it decides to look into. Am I correct that the [I does not use the tags file? If it uses the tags file, how? Once inside a file,

RE: patch 7.1.068

Bram Moolenaar wrote: The 'equalalways' option has the intention to spread out the available space, so that when you :split you can use the space from other windows. But when the space from the current window is sufficient that is not needed. That is what this patch fixes.

RE: tarball and unpacked top directory name syncronization

Per [...] Per Per Most opensource packages are named like proj- Per version.tar.gz, or bz2 for that matter. After Per uncompress/untar, the top directory is similar to tarball Per without extensions proj-version. Per Per [...] Per Per Unfortunally, when uncompressing and