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
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 wrote:
On Sa, 04 Mär 2017, Bram Moolenaar wrote:
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 "v
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" maill
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 bec
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'. I
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_
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 http://www.vim.org/maillis
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
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 "" or exec
Hello,
When running vim inside ConEmu, although lazyredraw is OFF (nolazydraw),
I still find the need to hit "" or execute ":redraw!" (with
shriek) to clear up the screen that has been messed-up by some bug with
using Vim inside ConEmu (
http://code.google.com/p/conemu-maximus5/issues/detail
Bug: Inconsistency in regard to titlestring and statusline.
Elaboration:
:help titlestring says:
When this option contains printf-style '%' items, they will
be expanded according to the rules used for 'statusline'.
However, my ingenuity does not enable me to see how the formatting
su
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
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 t
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
--- On Wed, 5/8/13, Christian J. Robinson wrote:
> From: Christian J. Robinson
> 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 Moolenaar wrote:
>
> > it's tim
On 4/18/2013 7:50 AM, Nazri Ramliy wrote:
Here's another attempt. This time we check if the expanded path ends
with a path separator then we replace it with forward slash, and we do
this only on windows/msdos.
Updated patch attached.
I tried the patch to src/misc1.c (but not the patches for t
On 4/14/2013 10:56 PM, Nazri Ramliy wrote:
> Hi Suresh!
> On Mon, Apr 15, 2013 at 10:22 AM, Suresh Govindachar
wrote:
>
>> Hitting after entering a partial argument to :find will
>> offer suggestions for completing the command line by searching
>> in
Hello,
Hitting 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 fol
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
Hello,
When a string is concealed, characters in the string along each line are
replaced by nothing; but any s in the string remain as s. Why is
the design this way? If it is possible to make conceal remove any s in
the string being concealed, please consider offering this feature.
Thanks,
-
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
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)
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
Around Sunday, December 13, 2009 2:53 PM, Tony Mechelynck wrote:
> On 13/12/09 23:07, Suresh Govindachar wrote:
>>
>> Hello,
>>
>> It would help if the items listed on the "vim-patches" page
>> mentioned any restrictions on OS
>&g
Hello,
It would help if the items listed on the "vim-patches" page mentioned any
restrictions on OS
http://groups.google.com/group/vim_dev/web/vim-patches
Thanks,
--Suresh
--
You received this message from the "vim_dev" maillist.
For more information, visit http://www.vim.org/maillist.php
Hello,
The following is a post by Brian Dessent on the MinGW-Users
mailing list. People thinking about vim and consoles/ptys on
Windows might find it interesting.
--Suresh
>> http://msdn2.microsoft.com/en-us/library/ms740141.aspx
>
> So how do I do a 'select' on stdin of the p
Hello,
Given below is information (uname -a, cat /proc/cpuinfo, vim
version) on two machines named crash_machine and recover_machine.
Bug: On recover_machine, vim refuses to read a swp file created
on crash_machine.
crash_machine>uname -a
Linux 2.6.18-1.2257.fc5 #1 SM
GI asked:
> Is it just me, or do others have a problem with the
> syntax/vim.vim file currently on the FTP server ftp.nluug.nl? I
> get a bunch of null characters at the end of the file, and
> syntax highlighting for Vim scripts is messed up.
>
> I found this problem because my cro
Igor wrote:
> Hello, I have used completion in vim a lot.
> Suggestion: can we have a option with string of characters which
> stops completion? for example:
> set completestop = '.;:-+()' etc...
> so every user can configure when builtin vim competion stops.
>
> For example -
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() t
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;
It is important to distinguish "keyboard accelerator keys"
interface with a keyboard interface.
To start slowly, note that a true graphical interface has elements
such as clickable icons and menus. To save a file using gvim's
graphical interface, one would use a mouse to pull dow
> I've been using VIM for the past three years and have seen my
> vocabulary of commands increase steadily. It's amazing how with
> three or four key strokes I can do stuff that would take me
> minutes in dumb text editors or smart editors that I am not
> fluent with. I was reminded
> Patch 7.1.110 (after 7.1.102)
> Problem:Win32: Still compilation problems with Perl.
> Solution: Change the #ifdefs. (Suresh Govindachar)
> Files: src/if_perl.xs
Not sure about the importance of the accuracy of the problem
statement but the problem is no
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
-~--~~~~--~~--~--~---
Patrick Texier
>
> I can add a test for vim compilation
> in [perl\lib\core\BuildInfo.h] file.
Don't modify perl files; I sent a patch for vim's
if_perl.xs -- try that, and let us know if it works.
Thanks,
--Suresh
--~--~-~--~~~---~--~~
You
*** if_perl.xs Fri Sep 14 09:31:10 2007
--- if_perl_patched.xs Fri Sep 14 09:47:38 2007
***
*** 50,63
*
* Jan Dubois suggested the following guarding scheme:
*/
! #if (ACTIVEPERL_VERSION >= 822)
! # define PERL589_OR_LATER
#endif
#if (PERL_REVISION == 5) && (PERL_V
Patrick Texier wrote:
> Hello,
>
> I'm compiling Vim CVS 7.1.107 (Huge version) using Borland C++ 5.5.1 on
> Windows 98. My Active Perl version is 5.8.6 build 811.
>
> I have the following messages (and some others warnings):
>
> = Output ===
> C:\vi
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) c:\opt\vim\vim71.
Hello,
I have noticed that the buffer-name handling routine
can identify different forms of a file name. For example,
I believe it knows that the following two are the same
when $HOME is /home/the_user
~the_user/the_file
/home/the_user/the_file
However, the name-
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 aft
Tony asked:
> Suresh Govindachar wrote:
>>
>> + #if (ACTIVEPERL_VERSION >= 822)
>> + # define PERL589_OR_LATER
>> + #endif
>> + #if (PERL_REVISION == 5) && (PERL_VERSION == 8) && (PERL_SUBVERSION >= 9)
>> + # define
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
+ /*
+ * Quoting
> There are open issues besides the need to extend the patch to
> make files other than Make_ming.mak:
>
> 1) The #if guards need to be improved -- this I can do.
>
> 2) I have no clue about is what happens when someone tries to
>build vim with non-AS perl or with AS perl on n
There are open issues besides the need to extend the patch to
make files other than Make_ming.mak:
1) The #if guards need to be improved -- this I can do.
2) I have no clue about is what happens when someone tries to
build vim with non-AS perl or with AS perl on non-Windows.
Finally,
Patch to account for two new symbols (Perl_sv_2iv_flags,
Perl_newXS_flags) introduced in ActiveState perl for
build 822 and later (these symbols were preventing the
building of vim with dynamic support for perl).
Has been tested with ActiveState perl build 822 and
older b
Attached one more Q/A with Jan Dubois:
(People who maintain notes on how to build vim with perl
might want to update their notes based on this post.)
>Jan Dubois of ActiveState points out an issue with if_perl.xs:
>
>> The src/if_perl.xs file contains code to redefine all Perl
Tony wrote:
>Suresh Govindachar wrote:
>>
>> Solved with help from Brian Dessent on the MinGW mailing list.
>>
>> Add -lperl58 at the very end (location matters) of the last command.
>>
>> --Suresh
>
> This is understandable b
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
The Make_ming.mak file for gvim has the lines:
ifdef PERL
ifeq (no, $(DYNAMIC_PERL))
LIB += -lperl$(PERL_VER)
endif
endif
So when building gvim with dynamic support for perl:
1) For older versions of ActivePerl, the build is
successful without any explicit -lperl58
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 http:/
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 i
.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
On the ActivePerl mailing group. Jan Dubois of ActiveState
commented that:
>On Fri, 24 Aug 2007, Suresh Govindachar wrote:
>> Building VIM with dynamic Perl support gives error messages
>> such as the following:
>>
>>gobj/if_per
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 M
[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 ne
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
-~--~~~~--~
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 OLE=ye
Hello,
Invoking he following command -- when is 0 or 1:
:echo synIDattr(synID(line("."), col("."), ), "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 BadSpel
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 statu
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
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-spe
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
Hello,
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, how is what [I does dif
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.
Per> [...]
Per>
Per> Most opensource packages are named like "-
Per> .tar.gz", or bz2 for that matter. After
Per> uncompress/untar, the top directory is similar to tarball
Per> without extensions "-".
Per>
Per> [...]
Per>
Per> Unfortunally, when uncompressing and untar'ing vim
67 matches
Mail list logo
