Re: Patch 7.4.1103

On Sat, Jan 16, 2016 at 3:45 PM, Bram Moolenaar wrote: > > Patch 7.4.1103 (after 7.4.1100) > Problem:Removed file still in distribution. > Solution: Remove Make_cyg.mak from the list of files. > Files: Filelist Somehow this patch hasn't found its way into the hg

Re: How to update with local changes

On Fri, Jan 15, 2016 at 4:06 PM, Bram Moolenaar wrote: > > I think most users will be in this situation: > > - Initially check out Vim from github: > > git clone https://github.com/vim/vim.git > > - Change a makefile to set some options, or change bigvim.bat to match >

Re: REGRESSION: Ctrl-A (and presumably Ctrl-X) forgotten in various repeats

On Tue, Jan 12, 2016 at 7:44 AM, h_east wrote: > Hi Tony and All, […] > > Please check the attached patch. > This patch would be fixed the above problem. > > -- > Best regards, > Hirohito Higashi (a.k.a h_east) I didn't make extensive tests, but my usecase problem is fixed.

REGRESSION: Ctrl-A (and presumably Ctrl-X) forgotten in various repeats

I have the following problem in gvim (Huge) 7.4.1087. My previous build was 7.4.1074 and IIRC it did not have this problem. Between them I notice several patches affecting Ctrl-A and Ctrl-X in Visual mode, or in RTL mode, or with '[ and '] marks, none of which seem to apply to my usecase. I am

Re: -Wmaybe-uninitialized in both Huge and Tiny after applying patches 7.4.1074 to 7.4.1087

On Mon, Jan 11, 2016 at 6:01 AM, h_east <h.east@gmail.com> wrote: > Hi Tony, > > 2016-1-11(Mon) 11:43:51 UTC+9 Tony Mechelynck: >> Here is what appears in the Tiny build (the Huge build has the same >> warning with a much longer gcc command-line): >> >

Re: REGRESSION: Ctrl-A (and presumably Ctrl-X) forgotten in various repeats

On Tue, Jan 12, 2016 at 4:19 AM, Gary Johnson <garyj...@spocom.com> wrote: > On 2016-01-11, KF Leong wrote: >> On Tuesday, 12 January 2016 11:00:17 UTC+8, Tony Mechelynck wrote: >> > I have the following problem in gvim (Huge) 7.4.1087. My previous >> > build was

-Wmaybe-uninitialized in both Huge and Tiny after applying patches 7.4.1074 to 7.4.1087

Here is what appears in the Tiny build (the Huge build has the same warning with a much longer gcc command-line): gcc -c -I. -Iproto -DHAVE_CONFIG_H -O2 -fno-strength-reduce -Wall -U_FORTIFY_SOURCE -D_FORTIFY_SOURCE=1 -o objects/ops.o ops.c ops.c: In function ‘op_addsub’: ops.c:5419:17:

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

This assumes 'nocompatible' if exists(':map') == 2 && exists(':smile') == 2 nnoremap :intexe "smi" endif Have fun! Even if instead of gold, frankincense and myrrh you got some dry sixth of puff pastry with maybe some vague idea of a frangipane taste, and broke a tooth on some bean to be

Re: warning during compilation

On Thu, Jan 7, 2016 at 10:08 PM, Charles Campbell wrote: > Hello: > > I just noticed that there's a warning when compiling with gcc under > scientific linux: > > misc2.c: In function 'put_time': > misc2.c:6312: warning: ignoring return value of 'fwrite', declared with

Re: Compile error: error: 'prep' undeclared

Please follow the rest of this conversation on the vim_dev list, where I am redirecting it. On Tue, Jan 5, 2016 at 12:27 AM, Bernd Eggink wrote: > When trying to compile vim on Linux (Crux) I get this error: > > - > gcc -c -I. -Iproto

Re: Patch 7.4.1044

On Sun, Jan 3, 2016 at 10:57 PM, Bram Moolenaar wrote: > > Patch 7.4.1044 (after 7.4.1042) > Problem:Can't build without the +eval feature. > Solution: Add #ifdef. > Files: src/ops.c […] After this change, the Tiny build goes to completion, but with one warning in

Re: Bug: Unable to set textwidth via vimrc

On Mon, Jan 4, 2016 at 12:37 AM, tot-to wrote: […] > :scriptnames gives the following list if started with no options: > > 1: /etc/vim/vimrc > 2: /usr/share/vim/vim74/syntax/syntax.vim > 3: /usr/share/vim/vim74/syntax/synload.vim > 4:

Re: [vim] syntax: "\a" does not include characters like "ä" and that breaks syntax highlighting (#545)

On Sun, Jan 3, 2016 at 3:53 PM, Nikolay Aleksandrovich Pavlov wrote: > Unlike some other languages in VimL range always meant range in current > encoding’s codepoints. So in UTF-8 [a-zA-Z] is literally “from U+0061 to > U+007a (inclusive) or from U+0041 to U+005A (inclusive)”

Re: Bug: Unable to set textwidth via vimrc

On Sat, Jan 2, 2016 at 7:06 AM, tot-to wrote: > Hi Ken, > > Thanks, it says "Last set from /etc/vim/vimrc" > > I've found the place in that file, where it sets the variable. This is > apparently distribution (Gentoo) specific settings: Many Linux distributions, when they

Re: Patch 7.4.995

On Sun, Jan 3, 2016 at 5:26 AM, John Little wrote: > Tony > > I have used git checkout to back out my change, as patch 1038 does it now. > > Regards, John Little > Yeah, I applied it temporarily by means of the Mercurial mq (queue management) extension so I could pop it

Re: Patch 7.4.995

On Sat, Jan 2, 2016 at 1:48 PM, John Little <john.b.lit...@gmail.com> wrote: > On Saturday, January 2, 2016 at 7:09:58 PM UTC+13, Tony Mechelynck wrote: >> the compiler warning in question is still there at the current patchlevel. > > What does > >pkg-config --modver

Re: Patch 7.4.995

On Sat, Jan 2, 2016 at 9:29 AM, Kazunobu Kuriyama wrote: > Hi Tony, > > The following sequence of commands: > > $ cd src > $ make shadow > $ cd shadow > $ CONF_OPT_DARWIN='--disable-darwin' CONF_OPT_GUI="--enable-gui=gtk2" make > > works fine for me (The 'darwin'

Re: Patch 7.4.995

On Sat, Jan 2, 2016 at 6:24 PM, Kazunobu Kuriyama wrote: > 2.31 is the first version that deprecates gdk_pixbuf_new_from_inline(). > > Its reference manual: > https://developer.gnome.org/gdk-pixbuf/2.31/gdk-pixbuf-Image-Data-in-Memory.html#gdk-pixbuf-new-from-inline,

Re: Patch 7.4.995

On Sat, Jan 2, 2016 at 10:46 PM, Bram Moolenaar <b...@moolenaar.net> wrote: > > John Little wrote: > >> On Sunday, January 3, 2016 at 2:13:42 AM UTC+13, Tony Mechelynck wrote: >> > > What does >> > > >> > >pkg-config --modvers

Re: Patch 7.4.995

On Sun, Jan 3, 2016 at 12:14 AM, Tony Mechelynck <antoine.mechely...@gmail.com> wrote: > On Sat, Jan 2, 2016 at 10:46 PM, Bram Moolenaar <b...@moolenaar.net> wrote: >> >> John Little wrote: >>> My Ubuntu 15.04 install says 2.31.3, so I think you could do what

Re: Patch 7.4.995

I found this email still waiting as an unsent "draft" — and the compiler warning in question is still there at the current patchlevel. Sorry. On Tue, Dec 29, 2015 at 6:56 PM, Bram Moolenaar wrote: > > Patch 7.4.995 > Problem:gdk_pixbuf_new_from_inline() is deprecated. >

Re: patch: more smily

On Thu, Dec 31, 2015 at 7:39 PM, Bram Moolenaar wrote: > > Yasuhiro Matsumoto wrote: > >> https://i.gyazo.com/4b7219eee71af32831e4f3662075bea7.png > > Unfortunately color schemes can make this look ugly. > Like the idea though. > The version in the current Vim is just the

Re: patch: more smily

On Thu, Dec 31, 2015 at 6:41 PM, Tony Mechelynck <antoine.mechely...@gmail.com> wrote: > On Thu, Dec 31, 2015 at 5:05 PM, mattn <mattn...@gmail.com> wrote: >> https://i.gyazo.com/4b7219eee71af32831e4f3662075bea7.png >> >> diff --git a/src/ex_cmds.c b/src/ex_cmds.c

Obsolete paragraph in doc/scroll.txt

In the scroll.txt helpfile, the last paragraph above the tag for and (i.e. at lines 289-294) mentions XFree86, a project whose last release was in 2008 and whose last CVS update was in May 2009. Its successor is the X.org project, a fork which in its current versions doesn't use XF86Config

Re: Patch 7.4.1005

On Thu, Dec 31, 2015 at 4:10 PM, Bram Moolenaar wrote: > > Patch 7.4.1005 > Problem:Vim users are not always happy. > Solution: Make them happy. > Files: src/ex_cmds.h, src/ex_cmds.c, src/proto/ex_cmds.pro Inderdaad, deze nieuwe, euh, nee, 't is geen paasei, laten

Re: Patch 7.4.1005

On Thu, Dec 31, 2015 at 5:30 PM, Ken Takata wrote: > Hi, > > 2016/1/1 Fri 0:11:02 UTC+9 Bram Moolenaar wrote: >> Patch 7.4.1005 >> Problem:Vim users are not always happy. >> Solution: Make them happy. >> Files: src/ex_cmds.h, src/ex_cmds.c, src/proto/ex_cmds.pro

Re: patch: more smily

On Thu, Dec 31, 2015 at 5:05 PM, mattn wrote: > https://i.gyazo.com/4b7219eee71af32831e4f3662075bea7.png > > diff --git a/src/ex_cmds.c b/src/ex_cmds.c > index 73a5564..7fef594 100644 > --- a/src/ex_cmds.c > +++ b/src/ex_cmds.c Aha, so there's where patch 7.4.1005 came from.

Re: build fail since .997

On Thu, Dec 31, 2015 at 5:47 PM, Steve Hall wrote: > Since patch 997, something has broken in the cygwin build process, I now > see: > > gobji386/if_ruby.o:if_ruby.c:(.text+0x749): undefined reference to > `rb_data_typed_object_alloc' >

Re: [vim] allow KEYMAP with @a (#543)

On Wed, Dec 30, 2015 at 9:10 PM, Bram Moolenaar wrote: > > > Roland Puntaier wrote: > > > I've debugged into vim and found the location, in which normal keymap > > application diverges when playing a register macro (@a). > > > > It is in getchar.c: 2189 > > > > if

Re: Patch 7.4.1000

On Thu, Dec 31, 2015 at 12:42 AM, Mats Tegner wrote: > Den onsdag 30 december 2015 kl. 15:49:30 UTC+1 skrev Bram Moolenaar: > Patches 7.4.1000 to 7.4.1004 are listed in the README-file but aren't > available on ftp://ftp.vim.org/pub/vim/patches/7.4/ Sounds like the

Re: [vim] allow KEYMAP with @a (#543)

On Thu, Dec 31, 2015 at 12:30 AM, Roland Puntaier <roland.punta...@chello.at> wrote: > On 12/30/2015 9:59 PM, Tony Mechelynck wrote: > >> The help for i_CTRL-R says "The text is inserted as if you typed it, but >> mappings and abbreviations are not used.

Re: [vim] Rebuild the autoconf files during CI testing (#510)

IMHO configure should not be rebuilt systematically, not even "on every Huge build". The distributed auto/configure should be good enough for most users, and certainly for me who prefer not even to modify the Makefile (I pass the configure arguments to make by means of environment variables). If

Re: [vim] Rebuild the autoconf files during CI testing (#510)

On Wed, Dec 30, 2015 at 1:08 PM, James McCoy wrote: > I'm not suggesting it should be rebuilt as part of the normal build that > users perform. > > I'm suggesting that the CI infrastructure rebuilds it for a couple > reasons. > > 1. Make it easier for pull requests which

Broken link after "make shadow"

After "make shadow", the "testdir" subdirectory of the shadow directory (which is created below src/) contains a broken softlink vimrc.unix -> ../../testdir/vimrc.unix (i.e. the destination file doesn't exist). Unless this file is created by "make test", this looks suspicious. My (Mercurial)

Proposed patch to doc/pattern.txt

I am proposing the attached patch to doc/pattern.txt because the fact that the helptags for /~ and /\~ are synonymous seems to be confusing to newbies. See the thread "New in VIM" in vim_use, https://groups.google.com/forum/#!topic/vim_use/oCrKyKp0KVY Best regards, Tony. -- -- You received

Re: [vim] 7.4.979 duplication file in autocomplete wildmenu (#539)

On Sat, Dec 26, 2015 at 5:11 PM, Julien Pivard wrote: > > I started Vim start with vim -u NONE (to be sure it's a bug, and not caused > by my config) and set nocompatible, set wildmenu > > When press tab after typed :!/ suggestion are duplicate like this : > > and this

Re: [vim] 7.4.979 duplication file in autocomplete wildmenu (#539)

On Sat, Dec 26, 2015 at 10:14 PM, Gary Johnson <garyj...@spocom.com> wrote: > On 2015-12-26, Tony Mechelynck wrote: >> On Sat, Dec 26, 2015 at 5:11 PM, Julien Pivard wrote: >> > >> > I started Vim start with vim -u NONE (to be sure it's a bug, and >> > not

Re: Updating runtime files without version control

On Wed, Dec 23, 2015 at 4:10 AM, Christian J. Robinson wrote: > On Tue, 22 Dec 2015, James McCoy wrote: > >> On Tue, Dec 22, 2015 at 08:09:47PM -0500, Jonathan Newton wrote: >>> >>> I guess the use case for :RuntimeUpdate is not clear to me. Do you really >>> want a user

Re: Updating runtime files without version control

On Mon, Dec 21, 2015 at 9:44 PM, Bram Moolenaar wrote: > > Since Vim is very stable, it does not happen often that a new version is > released. Mostly it's fine to run an older version. Unless you run into > a bug there is no pressing reason to update. With the result that

Re: Updating runtime files without version control

P.S. Vim without Cream is 8.6 MB. My Huge gvim with GTK2 and is only 2.7 MB. I can't believe the difference is only due to the difference between W32 and L64, especially since "Vim without Cream" has +gettext/dyn +lua/dyn +multi_byte_ime/dyn +perl/dyn +python/dyn +python3/dyn +ruby/dyn -tcl while

Re: [vim] :move command closes all folds (#536)

On Tue, Dec 22, 2015 at 12:19 AM, Steven Hall wrote: > I have 2 versions of vim. Both the exact same configuration, but whenever I > do a :m command in one of them, it closes all open folds. > > I ran vim -N -u NONE to open vim with no configs or plugins. > > Then in

Re: [vim] :move command closes all folds (#536)

P.S. Switching two lines by ddp doesn't close the fold; OTOH the do-nothing move ":m ." does. Best regards, Tony. On Tue, Dec 22, 2015 at 4:29 AM, Tony Mechelynck <antoine.mechely...@gmail.com> wrote: > On Tue, Dec 22, 2015 at 12:19 AM, Steven Hall <vim-dev-git...@256bit.or

Re: Updating runtime files without version control

On Mon, Dec 21, 2015 at 10:51 PM, Nikolay Aleksandrovich Pavlov wrote: > 1. This is completely useless idea for *nix (both linux and mac) users […] > 2. I think this is useless idea for Windows users as well [...] On Linux, I think most users indeed either use their distro's

Re: Updating runtime files without version control

On Tue, Dec 22, 2015 at 3:41 AM, Jonathan Newton wrote: […] > > I think perhaps some confusion is due to users trying to get the latest exe > via the "vim without cream" link which only provides the binary and not RT > files. Perhaps the download page at vim.org should be

Tag v7.4.977 missing in the Mercurial mirror repository

Running hg tags | more lists the tags from newest to oldest. Tag v7.4.977 is missing near the top. OTOH, hg log -l 10 displays the 10 most recent changesets. Patch 7.4.977 itself is present (hg commit 68f2cac6b0db, github commit 9bc01ebb957d2b30d57bd30d7aee6f1df2a336b0), but it is

Re: Sort corruption

On Wed, Dec 16, 2015 at 11:17 PM, Christian Brabandt wrote: > On Mi, 16 Dez 2015, Mike Williams wrote: > >> On 16/12/2015 19:14, Christian Brabandt wrote: >> >[HAVE_AVAIL_MEM] >> >>However, it does throw out the setting of maxmem/maxmemtot with it. >> >>The setting of

Re: Sort corruption

On Wed, Dec 16, 2015 at 11:57 PM, Mike Williams wrote: > How about on Windows running a 32bit process on 64bit OS with 8GiB of RAM? > Max mem usable is 4GiB, the limit for the virtual address space. Windows can > report available virtual address for the process,

Re: [patch] fix asin()

I confirm the bug: In gvim 7.4.970 (Huge): :echo asin(1.0) E117: unknown function: asin E15: Invalid expression: asin(1.0) Command-line completion _does_ complete asi to asin( Best regards, Tony. On Sun, Dec 13, 2015 at 10:46 AM, watiko wrote: > Hi lists. > > The

Re: [patch] Fix the error message spacing for assert_false/true

The same double space applies to assert_true() but not to assert_equal(), for instance: :let v:errors = [] :call assert_equal(1,2) :echo v:errors [' line 0: expected 1 but got 2'] with an unexpected space at the very start but only one space between 1 and but, and none after 2. IMHO this whole

Re: Patch 7.4.970

On Sun, Dec 13, 2015 at 12:24 AM, tux. wrote: > Bram Moolenaar schrob am Samstag, 12. Dezember 2015 um 21:32 Zeit: > >> I'm thinking about it. Especially for MS-Windows, the version provided >> from the ftp site is quite old. > > Why not just add a link to up-to-date

Re: Why I don't have conceal* options in my build?

On Tue, Dec 8, 2015 at 10:29 AM, Viacheslav Lotsmanov wrote: > Hi there. I built vim v7.4.963 from git with this configure flags: > > --enable-luainterp --enable-perlinterp --enable-python3interp > --enable-tclinterp --enable-rubyinterp --enable-cscope --with-gnome > > For

Re: [vim] doesn't work in insert mode (#519)

On Mon, Dec 7, 2015 at 10:53 AM, Viacheslav Lotsmanov wrote: > @chrisbra actually I tried this config at first: > https://github.com/unclechu/vimrc2/blob/master/.vimrc where I have > nocompatible flag and I have this bug in this mode too. > > In v7.4.827 (from Fedora 22

Re: [vim] Add use of “make shadow” to CI (#520)

FWIW on my own (home) install of openSUSE Linux I use two shadow directories, generated as follows: cd src SHADOWDIR='shadow-huge' make -e shadow SHADOWDIR='shadow-tiny' make -e shadow cd .. The -e switch is not used after that: by descending into the proper shadowdir (where appropriate config

Re: Odd result for sort([ '1', '5', '48', '25', '5', '28', '6'], 'n')

After applying the recent patches (up to 7.4.960) I notice a duplication in the help, as follows (eval.txt lines 5818 to 5828): The sort is stable, items which compare equal (as number or as string) will keep their relative position. E.g., when sorting on numbers, text

Re: $TMPDIR bug

On Thu, Dec 3, 2015 at 12:39 AM, Jörn Engel wrote: > Retry after subscribing to the list. I hope this works and I can > unsubscribe again. > [...] Indeed, messages can only make it to the list if they are from subscribed authors, but in addition, the first time a given

Compilation warning: gdk_pixbuf_new_from_inline is deprecated (@ gui_gtk.c line 152)

When compiling 7.4.944, huge, with GTK2/Gnome2 GUI (i don't know exactly at which changeset it appeared): gcc -c -I. [...] -o objects/gui_gtk.o gui_gtk.c gui_gtk.c: In function ‘add_stock_icon’: gui_gtk.c:152:5: warning: ‘gdk_pixbuf_new_from_inline’ is deprecated (declared at

Re: Patch 7.4.944

I'm not going to take sides here, just compare with some other project: In Mozilla code (Firefox, Thunderbird, SeaMonkey), preferences (which are user-visible, at least for technical-minded users who dare use the about:config interface) are named with camelCase in some parts of the code and with

Re: Compilation warning: gdk_pixbuf_new_from_inline is deprecated (@ gui_gtk.c line 152)

On Mon, Nov 30, 2015 at 8:02 AM, Marius Gedminas <mar...@gedmin.as> wrote: > On Mon, Nov 30, 2015 at 12:01:07AM +0100, Tony Mechelynck wrote: >> When compiling 7.4.944, huge, with GTK2/Gnome2 GUI (i don't know >> exactly at which changeset it appeared): >> >> gcc

Re: Vim's make reorders the output of stderr and stdout (in some cases)

On Wed, Nov 25, 2015 at 5:13 PM, Gary Johnson wrote: > On 2015-11-25, B. Wilson wrote: >> When running :make and there is output to both stderr and stdout, >> I'm seeing a degree of reordering in the displayed output. >> >> I didn't notice any similar issues when searching

Re: [DOC? BUG] Documentation regarding viminfo-% is incorrect

On Mon, Nov 23, 2015 at 1:12 PM, Nikolay Pavlov wrote: > Consider the following script: > > vim -u NONE -i /tmp/foo.viminfo -c 'help :command' -c 'setlocal > buflisted' -c 'set viminfo='\''0,%' -c 'qa' > > This will result in the following contents in foo.viminfo: > > #

Re: [vim] Vim removes last newline (#488)

On Fri, Nov 20, 2015 at 4:44 PM, Ben Fritz wrote: > Somebody mentioned it in passing; and I agree this isn't a bug, so the issue > should remain closed, however: > > The user has a problem. The problem can be fixed with different user settings. > > You need to set noeol

Re: [vim] Vim removes last newline (#488)

On Fri, Nov 20, 2015 at 9:14 PM, Laurent Lyaudet wrote: > > Personally, I just see a file as a string and it's weird if the empty string > is displayed the same as the string "\n". Vim shows 1 line when there is > none, 1 line when there is 1, etc. Other editors show

Re: [vim] Yanking into the same registry slot as the macro's currently being recorded cause macro to be yanked instead. (#470)

On Tue, Nov 17, 2015 at 9:21 AM, Jeff Felchner wrote: > Tony, I definitely don't think there should be a prompt, but I think maybe a > status line warning would be appropriate? That's what I said in my reply to Christian. Best regards, Tony. -- -- You received

Re: [vim] Yanking into the same registry slot as the macro's currently being recorded cause macro to be yanked instead. (#470)

On Mon, Nov 16, 2015 at 12:41 PM, Christian Brabandt wrote: > > So how about adding some warning into the documentation that putting from the > same register that is used for recording won't likely work as one would > expect and perhaps also mention in the status line

Re: [vim] Yanking into the same registry slot as the macro's currently being recorded cause macro to be yanked instead. (#470)

On Mon, Nov 16, 2015 at 2:33 AM, Jeff Felchner wrote: > > If one is looking at weighing the benefits of allowing such a thing, and the > downsides of allowing such a thing, I think it's pretty clear that the > current behavior is: > > a) not very useful even if it's

Re: Patch 7.4.909

The published .desktop files are nice as far as they go but they miss a number of MIME types I may want to edit with Vim. Here is the mimeinfo.cache generated manually by running update-desktop-database as Kuriyama Kazuniobu said earlier in this thread: [MIME Cache]

Re: Patch 7.4.909

On Wed, Nov 4, 2015 at 12:23 PM, Kuriyama Kazunobu wrote: > Hi, > > There remains one thing to complete the installation. > > After installing `*.desktop` files into the destination directory, someones > has to update a cache file, called `mimeinfo.cache`, in that

Re: [patch] Substring and variable is parsed more smart

On Wed, Nov 4, 2015 at 5:33 AM, h_east wrote: > Hi Bram and List! > > How to reproduce: > - Start pure vim with new file a.vim > $ vim -N -u NONE a.vim > > (1) > :let str='abcde' > :let nn=3 > :echo str[nn:] > E121: Undefined variable: nn: > E15: Invalid expression:

Re: Installation failure

On Tue, Nov 3, 2015 at 8:06 AM, lilydjwg <lilyd...@gmail.com> wrote: > On Tue, Nov 03, 2015 at 07:37:33AM +0100, Tony Mechelynck wrote: >> [...] >> /opt/*/share is among the places where my shells will look at startup >> for an applications/ subdirectory, see above.

Re: [PATCH] utf-8 encoding support for FEAT_HANGULIN

On Tue, Nov 3, 2015 at 9:34 AM, SungHyun Nam wrote: [...] > Just curious. Why do you think it is not compatible with GTK2? > I use "gtk2-vim + hangul_input" and didn't notice compatible problem. > > Thanks, > namsh Ah, sorry. I thought that was the reason it was disabled in my

Re: Compiler warings after patches 7.4.904 to 7.4.908

On Wed, Nov 4, 2015 at 7:55 AM, Tony Mechelynck <antoine.mechely...@gmail.com> wrote: > On Tue, Nov 3, 2015 at 10:03 PM, Bram Moolenaar <b...@moolenaar.net> wrote: >> >> Tony wrote: >> >>> After patches 7.4.904 to .908 I get the following compil

Re: Compiler warings after patches 7.4.904 to 7.4.908

On Tue, Nov 3, 2015 at 10:03 PM, Bram Moolenaar wrote: > > Tony wrote: > >> After patches 7.4.904 to .908 I get the following compile warnings: >> the first one is for using a deprecated declaration defined in a GDK >> include file, so possibly unavoidable; the other two are

Re: Installation failure

On Tue, Nov 3, 2015 at 6:53 AM, lilydjwg wrote: > [...] > If $prefix/share/applications doesn't exist, just create it. > > A XDG_DATA_DIRS setting specifies where to search for > applications/*.desktop files[1], and it defaults to ~/.local/share, > /usr/local/share and

Re: [PATCH] utf-8 encoding support for FEAT_HANGULIN

On Tue, Nov 3, 2015 at 8:22 AM, SungHyun Nam wrote: > Hello, > > I used hangulin feature nowadays, because it does not support > utf-8 encoding, I always ran vim with 'set encoding=cp949'. > But it gave me a pain whenever I open utf-8 encoded file. > > So that, today I made a

Re: [patch][Win32] Vim crashes when opening very long filename

Oops: ... two words are needed for codepoints 1 to 10... Best regards, Tony. On Sun, Nov 1, 2015 at 12:45 AM, Tony Mechelynck <antoine.mechely...@gmail.com> wrote: > On Sat, Oct 31, 2015 at 11:46 PM, Andre Sihera > <andre.sih...@hotmail.co.jp> wrote: >> On 01/

Re: [patch][Win32] Vim crashes when opening very long filename

On Sat, Oct 31, 2015 at 11:46 PM, Andre Sihera wrote: > On 01/11/15 00:01, mattn wrote: >>> >>> Thanks. Is there any corner case where we would need a few more bytes >>> than MAXPATHL? >> >> In utf-8, max bytes of letter should be 4. So MAXPATHL * 4. >> > No, the

Re: perl regex

On Mon, Oct 26, 2015 at 4:33 PM, Ben Fritz wrote: > It doesn't exist and it probably won't (the regular expression code is HUGE), > but did you know about the :perldo command? If your Vim is compiled with Perl > support (many major distributions are) you can run

Re: [vim] Include a .desktop file (#454)

Note: My HD crashed this summer, so I lost my address book. I added Steve Hall's address from memory but I'm not sure it is his current address. If he has a newer address, please let him and me know. On Sun, Oct 18, 2015 at 5:25 PM, Thomas G. wrote: > Hey, > > Is it

Re: Feature Request: Formal support for Ligatures.

On Sun, Oct 18, 2015 at 11:02 PM, Kevin Lozandier wrote: > I & many are expect true ligature support by enabling them to be used JIT > rather than add anything to vimrc other than to turn them off for those who > are *not* using monospace typefaces for whatever reason &

Re: [vim] javascript script support? (#450)

No, there isn't. The only language which is guaranteed to be accepted for scripting in all versions of Vim is vimscript. Some other languages (perl, python, python3, ruby, tcl, mzscheme, lua) can be embedded in vimscript but they won't be recognized unless the corresponding feature is

Re: [vim] Add support for backtrace on vim debug sessions (#433)

On Thu, Oct 15, 2015 at 9:40 PM, Alberto Fanjul wrote: > Here is all implemented. Just a note about frame (there are collisions): > >- f issues file >- fi[nish] >- fr[ame] > > I wil change frame layout to mimic gdb in no time > When several ex-commands

Re: what the real order of vim loading? I know there was a after-directory which can set some after-operation.But I cannot find a before-diretory, how to implement it?

On Wed, Oct 14, 2015 at 10:15 AM, Peng Dai wrote: > I used vundle.vim to manage my plugin now. And I write my own conf in the > vimrc. > > I now want to write all my own-conf tobe a vim-plugin, which will be hosted > on the github and be installed by Vundle.vim. > > I

Re: what the real order of vim loading? I know there was a after-directory which can set some after-operation.But I cannot find a before-diretory, how to implement it?

On Wed, Oct 14, 2015 at 6:20 PM, Gary Johnson wrote: > On 2015-10-14, Peng Dai wrote: >> I used vundle.vim to manage my plugin now. And I write my own conf >> in the vimrc. >> >> I now want to write all my own-conf tobe a vim-plugin, which will >> be hosted on the github and

Re: [vim] isfname+=32 breaks escaping for space in options (#447)

On Wed, Oct 14, 2015 at 8:59 PM, andrey-starodubtsev < vim-dev-git...@256bit.org> wrote: vim -u NUL -c"set isfname+=32 | filetype plugin on | e 1.pl" > > causes following error > > Error detected while processing C:\Program Files > (x86)\Vim\vim74\ftplugin\perl.vim: > line 18: > E518: Unknown

Re: netrw sorts symbolic links to directories as regular files

On Wed, Oct 14, 2015 at 5:54 PM, Gary Johnson wrote: [...] > 'ls -lF' does add a / to the names of directories referenced by > symbolic links. Ah yes, sorry. Without -l links get @ added but with it they get ' -> ' (space, tash, greater-than, space), the name of the end

Re: netrw sorts symbolic links to directories as regular files

On Tue, Oct 13, 2015 at 6:36 PM, Gary Johnson wrote: > When I open a directory containing symbolic links to other > directories, those symbolic links appear among the regular files, > not among the directories. I think it would be better to group the > symbolic links to

Re: fixendofline isn't copied from global variable

On Tue, Oct 13, 2015 at 5:06 PM, mattn wrote: > > 1. add set nofixendofline into vimrc > 2. :e ~/.vimrc > 3. :verbose set fixendofline Step 3 above does not display the value, it sets it to true. In order to display the value of a boolean option, you must use a question mark,

Re: [bug] broken English dictionary introduced by recent checkin

On Thu, Oct 15, 2015 at 6:50 AM, Dominique Pellé wrote: > Hi > > Something looks wrong with Vim English spelling dictionary. > > If I put the cursor on the D in "Director's" and press z= > in command mode, I get those spelling suggestions: > > 1 "Directors'" > 2

Re: MzScheme support on Windows is broken

On Fri, Oct 9, 2015 at 9:46 AM, KF Leong wrote: > On Friday, September 25, 2015 at 7:20:40 AM UTC+8, tux. wrote: >> I tried to compile Vim with Racket (Make_mvc.mak) and Visual Studio >> 2010. However, it seems that somewhere the path is not properly >> escaped. >> >> Racket

Re: [vim] Double quote is not interpreted as comment (#441)

On Wed, Oct 7, 2015 at 8:30 AM, Nguyen Tien Thanh wrote: > @Tanjoodo The two lines above are my .vimrc > file . To reproduce, do > > source ~/.vimrc > > Actually it happens with any .vimrc that has a comment line. > Normally, Vim itself

Re: remove feature xterm-save

On Wed, Oct 7, 2015 at 12:28 PM, Christian Brabandt wrote: > Bram, > I just found out, that the xterm-save feature needs to be enabled > specifically. But even after enabling it explicitly and do not see a > difference and switching screens has been working for me for a long >

Re: Updates to vhdl.vim

On Mon, Oct 5, 2015 at 3:00 PM, Daniel Kho wrote: > Thanks Tony. I (finally) cloned the Mercurial project on my new laptop and > noticed that the source files reflected the latest changes. I guess it's the > Ubuntu package manager that is not updated yet (I installed with

Re: [vim] VIM unable to find iconv dll in windows (+iconv/dyn option) (#440)

On Wed, Oct 7, 2015 at 2:06 AM, louarr wrote: > The latest iconv dll from gnuwin32 is named libiconv2.dll. Should vim also > try to load this dll instead of the old libiconv.dll? For the time being I > was able to solve the problem by copying libiconv2.dll to

Re: Updates to vhdl.vim

On Mon, Oct 5, 2015 at 11:41 AM, Daniel Kho wrote: > Hi Bram, > Just wondering if the file has been committed yet? I didn't see the changes > from a clean install of vim on a new laptop, so I'm asking. AFAICT the latest syntax/vhdl.vim is the one has a "Last Changed date"

Re: [vim] Vim bug about term true transparency (#436)

On Thu, Oct 1, 2015 at 1:59 AM, h_east wrote: > Hi, > > 2015-10-1 (Thu) 7:51:32 UTC+9 h_east: >> Hi, >> >> 2015-10-1 (Thu) 7:11:19 UTC+9 Celes-Eternal: >> > Hello, >> > >> > >> > I have a problem with my vim since some times. >> > >> > I'm using compton + urxvt + vim with

Re: Mistake found in one of the manpage examples for ''xxd''

On Sun, Sep 27, 2015 at 12:29 PM, Kwan Fong wrote: > Hi, > For lack of an ''xxd'' mailing list I will report a mistake in one of the > manpage examples, under the CAVEAT section, here. > > The following is an excerpt from the CAVEAT section: > > The following examples

Re: c2tags plugin

On Sun, Sep 27, 2015 at 9:21 AM, Bas van den Berg wrote: > Hi, > > I'm developing a C-like language, called C2 (c2lang.org). Now the compiler is > roughly working, I am working on a vim plugin called c2tags. The 'tags' file > is generated by a compiler plugin, so is

Re: [bug] use of uninitialized memory in regexp_nfa.c with invalid back reference

On Sun, Sep 27, 2015 at 1:21 AM, Dominique Pellé wrote: > Hi > > Valgrind detects use of uninitialized memory when doing: > > $ valgrind --track-origins=yes \ > vim -u NONE -c '/\(\&\|\1\)\(x\)' 2> vg.log > > Vim gives: > > Error detected while processing

Re: [vim] Qt interface (#429)

On Tue, Sep 22, 2015 at 6:35 PM, Tux- wrote: > Why is that so much work at all? I thought such a GUI would easily be > possible by just adding buttons which send keystrokes to the underlying > unmodified Vim...? > > […] Well, I don't know, but I know that it has been tried in

Re: [vim] Rendering issues with ligatures (#418)

On Fri, Sep 18, 2015 at 1:09 PM, Giuseppe wrote: > Not really, I've briefly tested the patched vim with the PragmataPro font > and it's still unusable [1]. > I don't use the ligatures myself but I just stumbled across this problem > this morning, when I mistakenly set

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