Re: Patch 7.4.873

> Article in the first Free Software Magazine: "Bram Moolenaar studied > electrical > engineering at the Technical University of Delft and graduated in 1985 on a > multi-processor Unix architecture." > Response by "dimator": Could the school not afford a proper stage for the > ceremony? :-DD --

Warning in Huge build after applying patches 866 to 872

The following warnings are seen in Huge build after applying patches 7.4.866 to 7.4.872. No warnings in Tiny build (with no X11 and of course no GUI): [...] gcc -c -I. -Iproto -DHAVE_CONFIG_H -DFEAT_GUI_GTK -pthread -I/usr/include/gtk-2.0 -I/usr/lib64/gtk-2.0/include -I/usr/include/pango-1.0

Re: [vim] Block-mode replace works characterwise instead of blockwise after column 147 (#422)

On Wed, Sep 16, 2015 at 7:42 PM, Christian Brabandt wrote: > Hi Ben! [...] > It happens on any column after the wrap. 147 should be great enough for > standard 80 column terminal (I suspect, the tests won't be run in much > larger terminals). > > > Best, > Christian > -- FYI:

Re: Patch 7.4.856

On Wednesday, September 9, 2015 at 9:16:00 AM UTC+2, Ike wrote: > tiny build breaks with this patch, I've opened a pull request on github > that only uses plines_nofill when FEAT_DIFF or PROTO is defined. > > https://github.com/vim/vim/pull/416 > > -- > Ike I think "FEAT_DIFF or PROTO" isn't

Re: VIM now crashes when opening large file:

On Wed, Sep 9, 2015 at 12:30 PM, Josh G wrote: > I keep getting crashes now when opening large file (4GB, 9GB). > > here was the last crash message details: > Problem signature: > Problem Event Name: APPCRASH > Application Name: gvim.exe > Application

Re: tags problem has followed us from hg

Under Mercurial, I simply tell Mercurial not to track runtime/doc/tags (add runtime/doc/tags to .hgignore and run "hg forget runtime/doc/tags" followed by "hg commit -m 'do not track the tags file'"); then when there is a change to it on the remote server Mercurial (hg fetch --switch-parent) asks

Warnings and errors after adding patches 855 to 861 (incl. fatal error in Tiny build)

After adding patches 855 to 861, plus runtime files changeset after patch 861 (from Mercurial mirror https://bitbucket.org/vim-mirror/vim): In Huge build: [...] gcc -c -I. -Iproto -DHAVE_CONFIG_H -DFEAT_GUI_GTK -pthread -I/usr/include/gtk-2.0 -I/usr/lib64/gtk-2.0/include

Re: Patch 7.4.860

On Tuesday, September 8, 2015 at 11:45:08 PM UTC+2, Manuel Ortega wrote: > On Tue, Sep 8, 2015 at 2:04 PM, Manuel Ortega wrote: > > > > On Tue, Sep 8, 2015 at 1:14 PM, Bram Moolenaar wrote: > > > > > Patch 7.4.860 > > Problem:    Filetype

Re: Patch 7.4.858

On Tuesday, September 8, 2015 at 11:30:29 PM UTC+2, Christian Wellenbrock wrote: > Really happy to see those new commands being added! After updating Vim I > tried :h :cdo, but no help was found. I checked my repository and indeed, the > added documentation is nowhere to be found. As you can see

Re: Warnings and errors after adding patches 855 to 861 (incl. fatal error in Tiny build)

On Wednesday, September 9, 2015 at 3:48:26 AM UTC+2, yegapp...@gmail.com wrote: > Hi, > > The patch to fix the build problems with the tiny build is attached. > > - Yegappan > With this patch, the tiny build succeeds, with the following warning: gcc -c -I. -Iproto -DHAVE_CONFIG_H -O2

Re: RFE: Allow defining digraphs by hex value

On Mon, Sep 7, 2015 at 8:14 PM, Christian Brabandt wrote: > On Mo, 07 Sep 2015, LCD 47 wrote: > >> +NU ^@ 10SH ^A 1SX ^B 2EX ^C 3ET ^D 4EQ ^E 5 > [… digraph list] > > Isn't this list different on different systems? At least, IIRC, for > EBCDIC

RFE: Allow defining digraphs by hex value

Let's say I want to define ,, (two commas) as a digraph for … (U+2026 HORIZONTAL ELLIPSIS). At the moment, in [g]vim 7.4.854 (with +multi_byte and 'encoding' set to utf-8), :dig ,, 8230 does it, but :dig ,, 0x2026 doesn't (AFAICT, it fails silently). The only way to use the hex

Re: Feature Request: Formal support for Ligatures.

On Monday, August 31, 2015 at 11:13:03 AM UTC+2, Kevin Lozandier wrote: > Ligature support being added to Vim I highly recommend being pursued more > than ever. > > Mainstream monospace fonts are now supporting ligatures that add sensible & > rational value to everyday programmers. > >

Re: RFE: Allow defining digraphs by hex value

On Sat, Sep 5, 2015 at 9:33 PM, Yegappan Lakshmanan wrote: > Welcome back Tony. Haven't seen your e-mails to the vim mailing lists > for a while. > > - Yegappan It's only on the evening of the last Sunday of August that I succeeded to get an Internet connection again.

Re: (Intentional?) off-by-one error in vimrc_example.vim

On 17/03/15 23:03, Bram Moolenaar wrote: Tony Mechelynck wrote: In the current $VIMRUNTIME/vimrc_example.vim (Last change: 2014 Nov 05) the following autocommand is defined at lines 73 to 81: When editing a file, always jump to the last known cursor position. Don't do it when

(Intentional?) off-by-one error in vimrc_example.vim

In the current $VIMRUNTIME/vimrc_example.vim (Last change: 2014 Nov 05) the following autocommand is defined at lines 73 to 81: When editing a file, always jump to the last known cursor position. Don't do it when the position is invalid or when inside an event handler (happens when

Warning in huge compile of eval.c

Sorry if this has already been reported, I'm very far behind reading mail due to computer slowness (computer won't stay up unless I set Fan: silent (but may reduce CPU performance) in the BIOS, and this makes it *very* slow indeed). At 7.4.617 (but after updating the Mercurial source up

Re: Correct behaviour for 's/\n//'?

On 28/11/14 09:53, Eliseo Martínez wrote: Since patch 7.4.232 (http://markmail.org/message/vo7ruair5raccawp), vim recognizes 's/\n//' as a special case, and transforms it into a join command. The generated join command involves lines in command line-range. Thus, '1,3s/\n//' joins lines 1, 2,

Re: Open file at particular line and column location?

On 26/11/14 22:16, Yuri Vic wrote: I need to open the file at the particular line and column. This command $ vim '+call cursor($line,$column)' '$file' does it, however it treats 'column' as byte offset, and not character offset, which in case of utf-8 causes cursor to be placed to the left of

Re: Hindi (Indic Language) Support in Vim

On 02/11/14 17:58, samcoolase...@gmail.com wrote: Respected Sir, We are a team of students trying to render Hindi fonts in VIM. We have been reading the forums and it seems that multibyte characters can be handled in VIM. We would be very happy if you could give us some pointers on how to

Re: [patch] support +tcl/dyn on Unix

On 20/09/14 16:13, Ken Takata wrote: Hi, Currently, +tcl/dyn is only supported on Windows. Attached patch enables dynamic loading of Tcl on Unix (including Cygwin). I'm not sure that this feature is really needed, but I hope this is useful especially for Cygwin. [...] For people like me, who

Re: Patch 7.4.457

On 25/09/14 10:24, mattn wrote: I don't see what you mean with breakable. Sorry, I was confused. Until Patch 7.4.457, getchar() doesn't return \CursorHold. (However 0x80 0xFD was returned) I meant getchar() return only when it used with expr. augroup hogehoge autocmd! autocmd

Re: Patch 7.4.449

On 19/09/14 19:39, Bram Moolenaar wrote: Patch 7.4.449 Problem:Can't easily close the help window. (Chris Gaal) Solution: Add :helpclose. (Christian Brabandt) Files: runtime/doc/helphelp.txt, runtime/doc/index.txt, src/ex_cmds.c, src/ex_cmds.h, src/proto/ex_cmds.pro

Re: Typo: a typo in compiler/msvc.vim

On 20/09/14 04:28, luozhiya wrote: Hello, I find a little typo in compiler/msvc.vim :-) Regards, Zhiya Luo This is indeed a typo, and you were right to correct it, but happily, it was only in a comment, so it shouldn't cause improper behaviour in the executable. ;-) Best regards, Tony.

Re: [Patch] Add go filetype with syntax

On 22/08/14 18:34, 'David Barnett' via vim_dev wrote: +dsymonds Good question. I can't tell if there are actual godoc files or just cli output from the godoc tool is sometimes passed to a vim buffer. I wouldn't mind keeping that file out for a later patch if there's no quick ftdetect rule. I

Re: Patch 7.4.414

On 22/08/14 23:06, Bram Moolenaar wrote: Patch 7.4.414 Problem:Cannot define a command only when it's used. Solution: Add the CmdUndefined autocommand event. (partly by Yasuhiro Matsumoto) Files: runtime/doc/autocmd.txt, src/ex_docmd.c, src/fileio.c,

Re: Patch 7.4.414

On 22/08/14 23:43, Tony Mechelynck wrote: On 22/08/14 23:06, Bram Moolenaar wrote: Patch 7.4.414 Problem:Cannot define a command only when it's used. Solution: Add the CmdUndefined autocommand event. (partly by Yasuhiro Matsumoto) Files:runtime/doc/autocmd.txt, src

Re: Patch 7.4.410

On 19/08/14 16:17, Tux wrote: Am 19. August 2014 16:13:36 MESZ, schrieb Bram Moolenaar b...@moolenaar.net: Those numbers are for major and minor releases, not patchlevels. Why does 7.4.410 still identify as 7.4.280 then? I guess in most OSs it doesn't matter, but Windows (for example)

Manual action neded if you compile in a shadow directory

Two new source files have been added at patchlevel 7.4.399, therefore if you compile in a shadow directory you need to link them. For Linux, and with the shadow dir being current (the default is src/shadow ; I use src/shadow-huge and src/shadow-tiny): ln -sv ../crypt.c ln -sv ../crypt_zip.c

Re: Windows incorrect rendering of international characters

On 04/08/14 14:34, Christian Brabandt wrote: Hi Tony! Hi Christian [...] And since this seems to work with the GTK2 build (I didn't test it), I see no reason, why this behaviour should not be also enabled on other GUIs. The reason, IIUC, is that searching other fonts is how Pango and Cairo

Re: Windows incorrect rendering of international characters

On 03/08/14 07:58, Paul Moore wrote: [...] Thanks for the explanation, but with all due respect, it doesn't seem unreasonable to me for a user to expect that if they specify a commonly-used monospace font like Consolas, Lucida Console, or even Courier New, they should get behaviour that is

Re: Windows incorrect rendering of international characters

On 31/07/14 20:50, Paul Moore wrote: On 31 July 2014 19:38, Bram Moolenaar b...@moolenaar.net wrote: Paul Moore wrote: On Windows, Vim does not correctly display international characters. To demonstrate this, create a file in UTF-8 encoding with the Unicode characters \x5000 \x5001 \x5002 in

Re: 7.4.356 - bad patch on ftp

On 22/07/14 14:27, Bram Moolenaar wrote: Tony wrote: On 22/07/14 10:57, Bram Moolenaar wrote: Arkadiusz Miśkiewicz wrote: Could someone fix 7.4.356 patch that sits on vim ftp? It tries to patch .hgignore file which doesn't exist in released tarballs. OK, let's do the same as for the

Re: 7.4.356 - bad patch on ftp

On 22/07/14 10:57, Bram Moolenaar wrote: Arkadiusz Miśkiewicz wrote: Could someone fix 7.4.356 patch that sits on vim ftp? It tries to patch .hgignore file which doesn't exist in released tarballs. OK, let's do the same as for the other patch that changes .hgignore. Thanks! ps. would be

Re: odd character drawing problem

On 18/07/14 15:56, Charles Campbell wrote: Tony Mechelynck wrote: On 17/07/14 21:55, Bram Moolenaar wrote: Charles Campbell wrote: The following line, when in a buffer that vim is displaying: m=⎣ℜ(b-a)⎦=1~1026 has the script R displayed correctly when the cursor is swept over it from

Re: how to install vim-x11 on redhat 6.5

On 06/06/14 16:57, Li Xue wrote: Hello, I want to add x-clipboard support to vim on redhat 6.5. I searched the web and found that I need to install vim-x11 to do that. I downloaded vim-x11.rpm and tried to install it using rpm. But there is a long list of dependencies. Do I need to install

Re: Why does Vim still have vi-compatibility mode?

On 29/05/14 11:50, Dmitry Frank wrote: Could anyone explain why does Vim still have vi-compatibility mode? Why would one use it? As a consequence, we have to keep |set nocompatible| in our |.vimrc|; there is much noise in docs like |{not in Vi}|, |{Vi: no ++opt}|, etc. and I can't really

Re: :help does not correctly handle partial abbreviations

On 02/06/14 17:49, Bram Moolenaar wrote: Matthew Martin wrote: On Monday, June 2, 2014 3:50:23 AM UTC-5, Bram Moolenaar wrote: Matthew Martin wrote: :help :nor should go to the tag for :noremap or :no not :norm as it does now. Similarly :help :nore incorrectly goes to :norea :help :norem

Compile error in Tiny build after patchlevels 7.4.296 to 305

After pulling the changesets for patchlevels 7.4.296 to 7.4.305 and updating to the new head of the default repository branch, the following errors happen in the Tiny build only (Huge build compiles and links fine): gcc -c -I. -Iproto -DHAVE_CONFIG_H -O2 -fno-strength-reduce -Wall

Re: Compile error in Tiny build after patchlevels 7.4.296 to 305

On 22/05/14 20:30, Bram Moolenaar wrote: [...] My tests also caught this, but they take a long time to run... I'll make a patch. The only tests I run consist of building (or trying to build ;-) ) a Tiny build in addition to my Huge build. This doesn't catch all misplaced and missing #ifdef

Re: getchar(0)/getchar(1) doesn't return 27(ESC)

On 15/05/14 13:15, mattn wrote: Thanks. Did you check that it still works to obtain a special key? For example, the cursor-up key Up. It seems that getchar(0)/getchar(1) doesn't work with cursor-up before this change. I get the following with gvim 7.4.295 (GTK2/GNOME2), testing all three

Re: E227: mapping already exists for ~@�SSpecChangelog

On 12/05/14 17:10, Vít Ondruch wrote: Hi, Edditing .spec file, going into some file using gt and return back by b#, I always get this annoying error: ruby.spec 1551L, 54263C Error detected while processing /usr/share/vim/vim74/ftplugin/spec.vim: line 20: E227: mapping already exists for

Error under :help has-patch

Under :help has-patch, the new §4 says: 4. Beyond a certain version or at a certain version and including a specific patch. The patch-7.4.123 feature means that the Vim version is 7.5 or later, or it is version 7.4 and patch 123 was included. The example above can be simplified

Re: Bug: Misinterpretation of key sequence

On 14/04/14 12:29, Dominic Humphries wrote: Entering the commands to leave insert mode insert a new line above the current one, beginning with certain letters, results in punctuation on the current line instead. To reproduce: Start vim, *quickly* type the keys: iEscOm Expected result: New

Re: Need help with understanding vimscript code snippet

On 29/03/14 11:40, Bruno Sutic wrote: Hi, I'm posting this to vim_dev because it is related to plugin development (apologies if it should go to vim_use). Recently, I discovered Tim Pope's vim-rsi plugin (https://github.com/tpope/vim-rsi). I was mind-blown to discover you can actually use Meta

Re: Updated Esperanto translation

On 25/03/14 22:25, Dominique Pellé wrote: Hi Please find attached the updated Esperanto translation vim/src/po/eo.po Regards Dominique To say that some test failed (i.e. didn't succeed), wouldn't malsukcesis be a better translation than fiaskis? Fiaskis (was a fiasco) could IMHO mean that

Compiler warnings

I've been noticing some compiler warnings recently, so I did a make reconfig (with logging of course) to catch any of them as there are in what I compile. My Huge build is made with the following settings (on 64-bit Linux): export CONF_OPT_GUI='--enable-gnome-check' export

Re: Is there any way to get the vim executable path from within vim?

On 14/03/14 08:20, Jürgen Krämer wrote: Hi, Viktor Kojouharov wrote: To easily use the remote-expr feature. You need to start a new instance of vim and point it to the current running vim server. And I need the full executable path in order to start the remote-expr. Vim is usually in the path

Re: RFE: :noswapfile prefix

On 13/03/14 23:22, Christian Brabandt wrote: On Do, 13 Mär 2014, Bram Moolenaar wrote: Tony Mechelynck wrote: RFE: I propose a :noswapfile (or something) prefix, working in similar fashion to the :verbose, :vertical, :top, :tab, etc. prefixes in front of another ex-command

RFE: :noswapfile prefix

RFE: I propose a :noswapfile (or something) prefix, working in similar fashion to the :verbose, :vertical, :top, :tab, etc. prefixes in front of another ex-command, and with the meaning: If that _subordinate_ ex-command opens a new buffer, we want 'noswapfile' set on that buffer. (If it

Error when opening file over ftp

The command abo sv ftp://ftp.vim.org/pub/vim/patches/7.4/README (in a script, at a point where another buffer is displayed in a window), or even :view (at the Vim command-line, when looking at that README file, to see if it has been modified), both give me **error**

Re: Problem with Python 3.4

On 20/02/14 10:45, İsmail Dönmez wrote: Any ideas on this one? This is blocking Python 3.4 update for openSUSE 13.2. On Thursday, February 13, 2014 11:44:24 AM UTC+2, İsmail Dönmez wrote: Hi, When compiled against Python 3.4, vim (7.4.178) test87 fails with: There have been several

Re: Patch 7.4.183

On 15/02/14 19:48, Bram Moolenaar wrote: Patch 7.4.183 Problem:MSVC Visual Studio update not supported. Solution: Add version number. (Mike William) Files: src/Make_mvc.mak This patch is missing in the README file, see http://ftp.vim.org/pub/vim/patches/7.4/README Best

Re: [patch] Prevent delete part of multi-byte character

On 18/02/14 13:23, Cade Foster wrote: This patch prevent delete part of multi-byte character. Steps to reproduce bug: 1) start vim (console or GUI): vim -u NONE -U NONE --noplugin -i NONE -n Note: LANG is en_US.UTF-8 TERM is linux vim version 7.4 with patches 1-183 2) type any multi-byte

Re: Patch 7.4.174

On 11/02/14 16:00, Bram Moolenaar wrote: Patch 7.4.174 Problem:Compiler warnings for Python interface. (Tony Mechelynck) Solution: Add type casts, initialize variable. Files: src/if_py_both.h In incremental build for patches 173-175 I get the following: - In tiny build

Re: Patch 7.4.174

On 11/02/14 20:54, ZyX wrote: PyErr_Format(%ld) is supported since python 2.5. Officially we support python 2.4 and older. Thus you should either drop support for python 2.4 or cast to (int). I was using the latter, though I cannot recall whether I just forgot to add type casts when

Re: Patch 7.4.174

On 11/02/14 18:42, Bram Moolenaar wrote: Tony Mechelynck wrote: On 11/02/14 16:00, Bram Moolenaar wrote: Patch 7.4.174 Problem:Compiler warnings for Python interface. (Tony Mechelynck) Solution: Add type casts, initialize variable. Files: src/if_py_both.h In incremental build

7.4.175 email missing?

For some reason I didn't get the email about patch 7.4.175, and it is not in my Gmail spam folder either. Not a big deal since the corresponding Mercurial changeset was downloaded in time, so I can produce an equivalent patch with the help of hg diff (attached). Note that the changeset in the

Re: 7.4.175 email missing?

On 12/02/14 02:55, Christian J. Robinson wrote: On Wed, 12 Feb 2014, Tony Mechelynck wrote: For some reason I didn't get the email about patch 7.4.175, and it is not in my Gmail spam folder either. I have a copy of it in my inbox, and a copy can be found in the mailing list archive: https

Re: Fwd: XXD ftplugin

On 09/02/14 16:13, Lech Lorens wrote: This should have gone to the list, not only to Bram. On 5 February 2014 20:44, Lech Lorens lech.lor...@gmail.com wrote: On 05-Feb-2014 Bram Moolenaar b...@moolenaar.net wrote: Looks useful. How much does this slow down moving the cursor around? Would

Re: [patch] Add s/\= tag

On 23/01/14 04:27, Matthew Martin wrote: Problem: sub-replace-\= is not consistent with other substitute tags Solution: Add s/\= tag Files: runtime/doc/change.txt *** 826,828 *** Substitute with an expression *sub-replace-expression* -

Re: Documenting VIM's internals

Tony Mechelynck was very helpful in this instance, I'm just sensitive to his / core developer's time. I feel left out of the loop, I know others do too. They feel they will be greeted with Why's. Centralized, Internal docs, even in a broad sense, would be tremendously constructive. blush / I'm

Re: Documenting VIM's internals

On 16/01/14 17:01, Ben Fritz wrote: On Thursday, January 16, 2014 9:14:31 AM UTC-6, MarcWeber wrote: [...] I even think about 'what would happen splitting runtime from Vim, and upload it to bitbucket / github' ? I like this idea and it's been discussed in the past. If I recall, Bram was

Re: vim 7.3(.547) and 7.4(.135) regex bug

On 15/01/14 11:10, Aidan Marlin wrote: Vim devs, I have discovered a bug which affects at least 7.4.135 and (likely) 7.3.547. Example file is available at https://mega.co.nz/#!ndVjXZTY!aMX_9ll-0ce861tQwNZBaFveb_kONCJxvAT2GZOvzlc (1.2MB in size) which will crash vim when attempting the

Re: Documenting VIM's internals

On 16/01/14 17:56, Marc Weber wrote: @Sergey Avseyev I've granted github access to you (github.com/MarcWeber/vim-git-wiki). Syncing with the web frontend is only done once every 10min. See contributing page: http://vim-wiki.mawercer.de/wiki//this-wiki/contributing.html C may be the wrong

Re: Patch 7.4.153

On 14/01/14 19:36, Bram Moolenaar wrote: Patch 7.4.153 Problem:Compiler warning for pointer type. Solution: Add type cast. Files: src/if_py_both.h, src/if_python.c, src/if_python3.c I get the following warnings when compiling Vim 7.4.155 (Huge, +python -python3) (7.4.153 to 155

Error messages opening a .txt.gz file from netrw (didn't try opening locally).

Using gvim 7.4.141 (Huge) for GTK2/GNOME2, changeset 2ca470c6096e g:loaded_netrw == g:loaded_netrwPlugin == 'v149' $VIMRUNTIME/plugin/gzip.vim dated 2010 Mar 10 While viewing ftp://ftp.mozilla.org/pub/mozilla.org/seamonkey/tinderbox-builds/comm-central-trunk-linux64/1389382240/ hit Enter

Re: Creating $HOME/_vimrc turns off syntax highlighting

On 27/12/13 21:36, Rob Owens wrote: On Fri, Dec 27, 2013 at 2:34 PM, Gary Johnson garyj...@spocom.com mailto:garyj...@spocom.com wrote: On 2013-12-27, Rob Owens wrote: My apologies if this has been reported already. I follow this list, but not as closely as I'd like to.

Re: Feature request: version-independent exe on Windows

On 27/12/13 00:39, Adrian wrote: The versioned install path ($INSTALLDIR/vim74/[g]vim.exe) is a major annoyance on Windows. People are likely to assign file types to be opened with vim. However, all those assignments break once a new Vim version is installed (because the path changes, e.g.

Re: Crash while deleting directory

On 26/12/13 10:44, François Ingelrest wrote: Hi all, I don't know whether this is caused by Vim or Netrw, but here's a way to crash both: 1. cd /tmp mkdir foo 2. vim 3. :e foo/ 4. rmdir foo touch foo 5. In Netrw choose .. to go up to /tmp 6. Open foo Vim crashes at this point with a

Re: Automatic user defined types syntax highlighting

On 24/12/13 22:28, Ben Fritz wrote: On Tuesday, December 24, 2013 1:31:30 PM UTC-6, riemann wrote: I would like to have automatic user defined types syntax highlighting in Vim. So that if I have for example a syntax match group for classes and have this in the buffer 1 class mytype { 2

Re: v:oldfiles won't be initialized when vim -u NONE

On 17/12/13 08:27, mattn wrote: On Tuesday, December 17, 2013 1:43:20 PM UTC+9, Tony Mechelynck wrote: On 16/12/13 12:33, mattn wrote: You can use no-compatible mode but you can do :echo v:oldfiles. And it refer NULL pointer. When I start Vim (the current Huge version 7.4.131, without

Re: v:oldfiles won't be initialized when vim -u NONE

On 16/12/13 12:33, mattn wrote: You can use no-compatible mode but you can do :echo v:oldfiles. And it refer NULL pointer. When I start Vim (the current Huge version 7.4.131, without applying your patch) with vim -N -u NONE then :echo v:oldfiles gives me a fully populated List of files.

Re: esckeys affect font

On 15/12/13 16:39, Alex Efros wrote: Hi! I'm not sure which application has this bug - vim or urxvt. I'm using urxvt with custom font which doesn't have all unicode symbols, but AFAIK urxvt somehow magically load symbols absent in current font from some other fonts. I've no idea how urxvt

Re: esckeys affect font

On 16/12/13 03:24, James McCoy wrote: On Sun, Dec 15, 2013 at 08:00:32PM +0100, Tony Mechelynck wrote: On 15/12/13 16:39, Alex Efros wrote: Hi! I'm not sure which application has this bug - vim or urxvt. I'm using urxvt with custom font which doesn't have all unicode symbols, but AFAIK urxvt

Re: v:oldfiles won't be initialized when vim -u NONE

On 16/12/13 04:12, mattn wrote: Hi. $ vim :echo v:oldfiles ['/path/to/oldfile.txt', snip] $ vim -u NONE $ echo v:oldfiles This return empty because VV_OLDFILES isn't initialized with allocated list. Isn't this intentional? With -u NONE, Vim starts in 'nocompatible' mode, thus the

Re: v:oldfiles won't be initialized when vim -u NONE

On 16/12/13 05:05, Tony Mechelynck wrote: On 16/12/13 04:12, mattn wrote: Hi. $ vim :echo v:oldfiles ['/path/to/oldfile.txt', snip] $ vim -u NONE $ echo v:oldfiles This return empty because VV_OLDFILES isn't initialized with allocated list. Isn't this intentional? With -u NONE, Vim

Re: New digraph

On 12/12/13 20:26, Bram Moolenaar wrote: Daily Lama wrote: As per helpfile, = is meant to be cyrillic, while '=e' is euro. = _after_ a letter means Cyrillic. It is only when no digraph is defined for what the user has typed (after Ctrl-K, or, with 'digraph' set [which I don't recommend]

Re: [patch] uppercase marks don't work after bwiping a buffer

On 11/12/13 14:38, Bram Moolenaar wrote: Christian Brabandt wrote: On Mo, 09 Dez 2013, Bram Moolenaar wrote: Christian Brabandt wrote: Bram, I use an uppercase mark to access a blowfish encrypted file. I therefore :bwipe that buffer when I'm done with this file. Unfortunately, I can't use

Re: Pattern matching broken with re=2 and ignorecase

On 11/12/13 18:25, Axel Bender wrote: @LCD 47 Well, that's a good question. However, the behavior should be consistent between the two RE engines and should not depend on a setting like ignorecase. @Bram Lazy, hmm. Wouldn't believe that given the speed you deliver updates ;-) The test file

Re: Windows console version doesn't switch to alternate-file with CTRL-^.

On 11/12/13 02:21, Andre Sihera wrote: On 10/12/13 19:01, mattn wrote: Windows console version doesn't switch to alternate-file with CTRL-^. Currently, os_win32.c has workaround for this. But it's not correct way. diff -r 79df7d17b859 src/os_win32.c --- a/src/os_win32.cSat Dec 07 14:48:10

Re: [issue][win32]vim console version can not use the system input method under windows 8

On 08/12/13 19:20, LiTuX wrote: (Seems that the one I send from gmail is blocked...) Hi all,I may meet a bug about the windows console version of vim. I've post to vim_use (https://groups.google.com/forum/#!topic/vim_use/DfrUutlmDoM) and was suggested to post here. Details are in the link

Re: [patch] uppercase marks don't work after bwiping a buffer

On 08/12/13 20:20, Christian Brabandt wrote: Bram, I use an uppercase mark to access a blowfish encrypted file. I therefore :bwipe that buffer when I'm done with this file. Unfortunately, I can't use the uppercase mark again, to reload that file, Vim throws E92 error. This is intentional (or

Re: [Suggestion] add {lhs} to mapclear so that only the key mappings starting with {lhs} are cleared

On 07/12/13 15:41, Bram Moolenaar wrote: Brook Hong wrote: Could we add {lhs} to mapclear so that only the key mappings starting with {lhs} are cleared? Just like map, :map{lhs} |mapmode-nvo| *:map_l* List the key mappings for the key

Re: Patch to utilize undefined text-objects

On 14/11/13 04:00, Ben Fritz wrote: On Wednesday, November 13, 2013 8:27:22 PM UTC-6, Tony Mechelynck wrote: […] It looks like something that ought to apply with -p1 starting at the top of your Vim source directory tree (with the parent of src/ runtime/ etc. being the current directory

Re: Patch to utilize undefined text-objects

On 14/11/13 17:39, Jürgen Krämer wrote: […] the @@ lines look suspicious to me. I thought they should start with @@, contain the old and new range of the hunk and end with @@. But in this patch @@ does not end the line; the line still contains some text that might be the line from before the

Re: Dead key problem + possible solution

On 13/11/13 17:37, Marc Thevenet wrote: Hi, I've been having problems with dead key behavior under Windows since Vim v7.3 (gVim only, the console version does not seem to be affected). In insert mode, when I type ' followed by space, it's supposed to insert a ', but since 7.3 it just seems to

Re: ^[[2;2R printed in messages area on BufEnter autocommand

On 12/11/13 23:50, Patrick Brisbin wrote: Hello, When I launch vim, I see [[^2;2R in the message area. Any form of redraw clears it and beginning to type an exe command will type over it. From some googling, it may have something to do with vim requesting the terminal's cursor position and

Re: Main Window Bug

On 13/11/13 01:48, Alexander Shukaev wrote: Hello, I want to report a bug which I found quite some time ago, but lately it became particularly annoying as one of my plugins depends on the bugged functionality. I don't know if it's present on other platforms, but it is definitely present on

Re: ^[[2;2R printed in messages area on BufEnter autocommand

On 13/11/13 04:07, Patrick Brisbin wrote: Thank you very much for your thorough response. My pleasure. [...] Thank you for those resources. I believe I'm well capable of compiling my own software; I just usually prefer not to. As far as I can tell, nothing between 86 and 91 looks like it may

Re: xxd patches

On 11/11/13 21:12, Vadim Vygonets wrote: Hello vimers, I needed a couple of features that no hexdump utility had, so I patched xxd. The added features are: * -e little endian * -o add offset to the displayed address * change address width to 8 digits You can view the patches here:

Re: Patch 7.4.069

On 05/11/13 07:13, Bram Moolenaar wrote: Patch 7.4.069 Problem:Cannot right shift lines starting with #. Solution: Allow the right shift when 'cino' contains #N with N 0. (Christian Brabandt) Refactor parsing 'cino', store the values in the buffer. Files:

Re: Problem with Corel copyright

On 02/11/13 05:07, John Beckett wrote: Bram Moolenaar wrote: I got pointed at a copyright notice in the $VIMRUNTIME/vimlogo.eps file. That's because the file was generated by Corel Draw and includes some stuff apparently written by Corel. To avoid a discussion about whether distribution is OK,

Re: What is the logic behind limiting the diff buffer count to 4?

On 02/11/13 14:26, Marius Gedminas wrote: On Fri, Nov 01, 2013 at 07:50:58AM -0700, ZyX wrote: I recompiled vim with a DB_COUNT of 5, and that successfully worked to diff five files. I suspect that the DB_COUNT limit can be raised without difficulty. I suspect that with a bit of coding that

Re: Patch 7.4.055

On 02/11/13 21:05, Bram Moolenaar wrote: Patch 7.4.055 Problem:Mac: Where availability macros are defined depends on the system. Solution: Add a configure check. (Felix Bünemann) Files: src/config.h.in, src/configure.in, src/auto/configure, src/os_mac.h Of course,

Re: [RFC] Lambdas

On 14/10/13 22:09, ZyX wrote: Since request for comments in thread with extended-funcref branch patches has gone unnoticed I will repost it here. I currently have somewhat working implementation of lambda functions in this branch and want to discuss where to move on since any implementation I

Re: [Suggestion] Allow gvim to start with no file name after --remote-silent

On 26/09/13 18:04, Axel Bender wrote: At the moment, when starting gvim --remote-silent gvim would display an error message, indicating that no file name was provided. This is quite a nasty behavior if you - like me - at times just start gvim (using a macro including --remote-silent) w/o a

Re: [RFC] Lambdas

On 19/10/13 12:01, Nikolay Pavlov wrote: On Oct 19, 2013 10:05 AM, Tony Mechelynck antoine.mechely...@gmail.com mailto:antoine.mechely...@gmail.com wrote: On 14/10/13 22:09, ZyX wrote: Since request for comments in thread with extended-funcref branch patches has gone unnoticed I

Re: [question] filetype name with dot (example included)

On 08/10/13 15:37, Bruno Sutic wrote: Hello vimers! I'm using vim-handlebars filetype plugin, link to source: https://github.com/nono/vim-handlebars I noticed the plugin is setting filetype with a dot in the name. Link to the relevant line in the source code:

Re: [BUG?] Statusline bg turns black on sy on

On 07/10/13 12:24, Marius Gedminas wrote: On Wed, Oct 02, 2013 at 05:54:21PM +0200, Florian Bruhin wrote: I discovered something that might be a bug, using vim 7.4. It isn't: After trying to simplify my vimrc first I was able to reproduce it with this .vimrc and no .vim folder: --- set

<    5   6   7   8   9   10   11   12   13   14   >