wrong highlight for *floating-point-precision* in help

In the eval.txt helpfile (last change 2018 Dec 09) at line 1108, with default GUI colors, the helptag *floating-point-precision* is highlighted in blue rather than pink. I suppose that some hidden control character is missing after the example functions to compute pi and e. This tag is correctly

Re: [vim/vim] New search is horrible and difficult to disable (MINT19) (#3663)

On Fri, Dec 7, 2018 at 5:28 AM James McCoy wrote: > Setting aside the actual details of what options/settings are provided > by defaults.vim, the mechanism used to provide newer defaults to users > is faulty. > > The fairly standard precedence for configuration at large is: > > user config

Re: Patch 8.1.0565

On Wed, Dec 5, 2018 at 7:46 PM Bram Moolenaar wrote: > > > Patch 8.1.0565 > Problem:Asan complains about reading before allocated block. > Solution: Workaround: Avoid offset from becoming negative. > Files: src/gui.c [...] > ! // FIXME: how can the first character ever be

Re: [Question] Stripping of Vim binaries

On Wed, Dec 5, 2018 at 6:28 PM wrote: > > Hi, > > I looked into Vim's Makefile and I found out binary stripping happens during > the built, which causes missing debuginfo data in the end of the build. > Would someone mind telling me if there a reason why stripping is done? Is > there a way how

Re: Invalid locale example at the end of :help digraphs-use

On Mon, Dec 3, 2018 at 8:50 PM Bram Moolenaar wrote: > > > Tony wrote: > > > The example locale at line 118 of helpfile digraph.txt is invalid. I > > suggest the attached patch. > > Thanks, I'll include it. > > Hmm, I think the remark about "fmt" is outdated. And it confuses me. > So let's just

Invalid locale example at the end of :help digraphs-use

e.com/d/optout. # HG changeset patch # User Tony Mechelynck # Parent bb2696c9ed5eecf995dd51d383ea3b6f585e558c Correct invalid locale example in digraph.txt diff --git a/runtime/doc/digraph.txt b/runtime/doc/digraph.txt --- a/runtime/doc/digraph.txt +++ b/runtime/doc/digraph.txt @@ -110,17 +110,21 @@

Re: RFE: Help about computing e and pi by functions rather than literals

Oops, d/dx(atan x) is slightly less than 1 for x=1 but it is still much better-behaved than "infinity". Best regards, Tony. On Mon, Nov 26, 2018 at 3:30 AM Tony Mechelynck wrote: > > On Mon, Nov 26, 2018 at 2:10 AM Bram Moolenaar wrote: > > Makes sense. It is prob

Re: RFE: Help about computing e and pi by functions rather than literals

On Mon, Nov 26, 2018 at 2:10 AM Bram Moolenaar wrote: > Makes sense. It is probably also more precise. However, I think we > only need to give one alternative for "pi", let's use the shortest one. If the compiler (or the floating-point hardware) specialcases acos(-1) — as IMHO every scientific

RFE: Help about computing e and pi by functions rather than literals

See the attached diff. Bram, this is an RFE, if you don't like it, don't take it (these are formulas I would use to compute e and pi). This also moves |float-pi| and |float-e| down by a few lines to put the paragraph headed "Rationale" where IMHO it belongs. Best regards, Tony. -- -- You

Re: Gdk-CRITICAL when I use -geometry with offset

On Wed, Nov 14, 2018 at 9:34 PM Mun wrote: > > Hi all, > > I'm not sure when this started, but it was sometime after v8.1 patch > 119 . I'm on v8.1 patch 524 now, and when I start vim thusly (e.g.): > $ vim -u NONE -U NONE --noplugin -g -geometry 80x40+100 .vimrc > > I get the following error on

Re: Patch 8.1.0519

On Linux64, even with that #ifdef in place, evalfunc.c compiles with no error, even in my Tiny and Small builds compiled with -quickfix and -eval (using gcc 7.3.1). All my other builds (Normal, Big and Huge) have +quickfix and +eval. Here are my configure options for the Normal build:

Re: Patch 8.1.0512

On Thu, Nov 8, 2018 at 6:22 AM Nazri Ramliy wrote: > > On Tue, Nov 6, 2018 at 3:26 AM Bram Moolenaar wrote: > > + static int > > + is_valid_mess_lang(char_u *lang) > > + { > > + return lang != NULL && ASCII_ISALPHA(lang[0]) && > > ASCII_ISALPHA(lang[1]); > > Any chance of segfault due

Re: Documentation bug report - "j" format option

On Mon, Nov 5, 2018 at 4:50 PM Edward McGuire wrote: > > This is a documentation bug report. The "j" format option is missing from the > table *fo-table* of the current HTML documentation, retrieved 5 November 2018. > > URL: > > http://vimdoc.sourceforge.net/htmldoc/change.html#fo-table > >

Re: Patch 8.1.0510

>if (lang == NULL || STRLEN(lang) < 2)/* safety check */ >return; ... >// any C like setting, such as C.UTF-8, becomes "en" >else if (STRLEN(p_hlg) >= 1 && *p_hlg == 'C') >{ >p_hlg[0] = 'e'; >p_hlg[1] = 'n'; >} This sets

Re: [vim/vim] Hard-coded 2 pixel border in GTK gVim (#3575)

On Tue, Oct 30, 2018 at 11:58 AM John Little wrote: > > On Tuesday, October 30, 2018 at 2:05:04 PM UTC+13, Kazunobu Kuriyama wrote: > > Vim on xterm has the 2px-width border > > Not on my xterm on KDE. ovk's mod now makes gvim consistent with vim in an > xterm, and vim in a konsole, when I use

Re: Can gvim take up the whole GUI screen (with no window decorations)

On Mon, Oct 29, 2018 at 4:31 AM Kazunobu Kuriyama wrote: > > On Mon, Oct 29, 2018 at 11:25 AM Tony Mechelynck > wrote: >> >> On Mon, Oct 29, 2018 at 2:26 AM Kazunobu Kuriyama >> wrote: >> > As far as X11 is concerned, whether or not attaching th

Re: Can gvim take up the whole GUI screen (with no window decorations)

On Mon, Oct 29, 2018 at 2:26 AM Kazunobu Kuriyama wrote: > As far as X11 is concerned, whether or not attaching the task bar or the > title window to the window dedicated to gvim proper is determined by the > window manager in use with that gvim. Accordingly, if the window manager is > able

Can gvim take up the whole GUI screen (with no window decorations)

>From github issue 3573: @prabirshrestha said: > @tonymec by full screen I don’t mean maximize. Full screen as in no task bar > and title window. I want my vim to be in one monitor and take all the pixels > there similar to watching a movie. This kind of thing would (I expect) have to be

Re: linebreak, showbreak, and visual block yank problem

On Wed, Oct 24, 2018 at 1:57 PM John Little wrote: > > I noticed a problem today when editing a paragraph that was wrapped to > several lines on screen. To reproduce, use a file with a line with normal > prose text that wraps to several screen lines, say x.txt, then > > vim -u NONE -c "set

Re: Patch 8.1.0487

On Fri, Oct 19, 2018 at 10:37 PM Bram Moolenaar wrote: > > > Patch 8.1.0487 > Problem:No menus specifically for the terminal window. > Solution: Add :tlmenu. (Yee Cheng Chin, closes #3439) Add a menu test. > Files: runtime/delmenu.vim, runtime/doc/autocmd.txt, runtime/doc/gui.txt, >

Re: MATLAB indent script

On Wed, Oct 17, 2018 at 9:08 PM Axel Forsman wrote: > > Hello everyone: > > I wrote to Christophe Poucet at christophe.pou...@pandora.be, the > listed maintainer on the MATLAB language indent file about an improved > indent script I made. Unfortunately, I got back that the email was not > listed

Re: [patch][win32] MinGW makefile deletes too much .exe files

On Wed, Oct 17, 2018 at 1:48 AM Ken Takata wrote: > > Hi, > > When running make clean with the MinGW makefile, it deletes all *.exe files. > It's too much. It should delete only created files like Make_mvc.mak does. > Please check the attached patch. > > Regards, > Ken Takata After the recent

Re: Patch 8.1.0474

On Mon, Oct 15, 2018 at 8:11 PM Bram Moolenaar wrote: > Ken Takata wrote: > > Is it better to remove -I. from CFLAGS in Make_mvc.mak and add it only where > > needed like Make_cyg_ming.mak? > > I think it doesn't hurt. Perhaps it's also needed for the xdiff files? On Linux, at least (where

Re: Testing the GUI code

On Sat, Oct 13, 2018 at 8:06 PM Bram Moolenaar wrote: > > > We have made great progress increasing test coverage, thanks for > everybody helping out! > > There is one big gap: The GUI code. We usually test by putting text in > the input buffer, which means we totally bypass all the GUI event >

Re: When started as "vim-huge --clean -? |less" the Gnome version tries (and fails) to start a GUI, then seems to hang

On Thu, Oct 11, 2018 at 5:25 PM Bram Moolenaar wrote: > > > Christ van Willegen wrote: > > > On Wed, Oct 10, 2018 at 12:44 AM Tony Mechelynck > > wrote: > > > Could it be because the g near the end of "vim-huge" is mistakenly > > > interpre

When started as "vim-huge --clean -? |less" the Gnome version tries (and fails) to start a GUI, then seems to hang

Invoke "vim --clean -? |less" at bash prompt in konsole. Yes, vim, not gvim; or as qualified to get to the proper binary (on my system, vim-huge for Gnome2, vim for Big GTK2 without Gnome, vim-small for Motif, or vi for no GUI; all these are the names of ELF executables [not symlinks] in

Re: [win32][patch] executable() may fail on very long filename

On Mon, Oct 8, 2018 at 3:50 AM Ken Takata wrote: > [...] > I have updated the patch for 8.1.0453: > > * Fixed conflicts. > * Fixed a typo in a comment which was added in 8.1.0453. > > Regards, > Ken Takata In UTF-8, characters outside the BMP (i.e. characters in the range U+1 to U+10FFFD),

Re: Convert C style comments into C++ style comments in quickfix.c

On Sun, Oct 7, 2018 at 7:39 PM Yegappan Lakshmanan wrote: > > Hi, > > The attached patch changes all the C style comments (except for > the function/data type headers) into C++ style comments in > the quickfix.c file. > > - Yegappan > Are all these changes really useful? Isn't it a little like

Fwd: CLA for contributing to Vim

-- Forwarded message - From: Tony Mechelynck Date: Sat, Oct 6, 2018 at 7:24 PM Subject: Re: CLA for contributing to Vim To: Cc: On Sat, Oct 6, 2018 at 7:12 PM wrote: > > Bram: > > As I understand it, Vim doesn't require a CLA—that is, a document that > any gi

Re: [patch] Fix modeline of some documents

On Fri, Oct 5, 2018 at 6:58 AM h_east wrote: > > Hi Bram and list, > > The following documents sets 'formatoptions' in modeline. > > runtime/doc/help.txt > runtime/doc/os_390.txt > runtime/doc/os_win32.txt > > "fo=tcq2:" > > Even if write "set fo+=mM" in my .vimrc, it will be

Re: [Proposal] Updated defaults.vim. (Add "mM" to 'formatoptions')

On Fri, Oct 5, 2018 at 4:19 AM h_east wrote: > > Hi Bram, > > By default, 'm' is not contained in 'formatoptions', so automatic wrapping > not work when multi-byte characters are continuously input. > Of course, I should set it up with my .vimrc, but I saw some people in > trouble with this

Fwd: potential user interface issue with Swap file dialog

Google blocked my previous post, saying it was "spam", so I'm posting it again with a different "To:" list. -- Forwarded message - From: Tony Mechelynck Date: Thu, Oct 4, 2018 at 10:35 PM Subject: Re: potential user interface issue with Swap file dialog To:

Re: potential user interface issue with Swap file dialog

On Thu, Oct 4, 2018 at 8:51 PM Christian Brabandt wrote: > [...] > -- > Mit jedem Tag den ich älter werde steigt die Zahl derer, > die jünger sind als ich. (Translation out of the German): Every day as I get older, the number of those younger than me increases. Whether this is true or not

Re: Remove function prototypes for static functions

On Mon, Oct 1, 2018 at 7:17 AM Dominique Pellé wrote: > > Tony Mechelynck wrote: > > > Oh, I thought we had (automatically generated) prototypes in > > src/proto/*.pro for all functions in src/*. > > No. The *pro files are not meant to declare static functions, > s

Re: Remove function prototypes for static functions

On Sun, Sep 30, 2018 at 7:03 PM Yegappan Lakshmanan wrote: > > Hi Bram, > > On Sun, Sep 30, 2018 at 8:12 AM Bram Moolenaar wrote: > > > > Yegappan wrote: > > > > > The quickfix.c file uses several function prototypes for static > > > functions in the file. The attached patch removes these > > >

Re: Patch 8.1.0400

On Sun, Sep 16, 2018 at 6:11 PM Bram Moolenaar wrote: > Q: How many legs does a giraffe have? > A: Eight: two in front, two behind, two on the left and two on the right Q.: Prove that horses have an odd number of legs. A.: Two in front, two at the rear, two on the left and two on the right, that

Re: When using diff I am getting "E959: Invalid diff format" in master gVim on Windows

On Thu, Sep 13, 2018 at 10:25 AM Tony Mechelynck wrote: > > On Thu, Sep 13, 2018 at 10:13 AM Igor Forca wrote: > > > > 1. QUESTION > > copy c:\aaa\a.txt C:\Users\igor\AppData\Local\Temp\file1.txt > > copy c:\aaa\b.txt C:\Users\igor\AppData\Local\Temp\file2.txt

Re: When using diff I am getting "E959: Invalid diff format" in master gVim on Windows

On Thu, Sep 13, 2018 at 10:13 AM Igor Forca wrote: > > 1. QUESTION > copy c:\aaa\a.txt C:\Users\igor\AppData\Local\Temp\file1.txt > copy c:\aaa\b.txt C:\Users\igor\AppData\Local\Temp\file2.txt > > > C:\cygwin\bin>diff -a --binary C:\Users\igor\AppData\Local\Temp\file1.txt > diff -a --binary

Re: [patch] has('patch-8.1.0') returns 0

On Thu, Sep 13, 2018 at 7:32 AM Tony Mechelynck wrote: > > On Thu, Sep 13, 2018 at 6:42 AM h_east wrote: > > > > Hi Bram and developers, > > > > :echo has('patch-8.1.0') > > 0 > > > > This should return 1. > > A patch attached. > &

Re: [patch] has('patch-8.1.0') returns 0

On Thu, Sep 13, 2018 at 6:42 AM h_east wrote: > > Hi Bram and developers, > > :echo has('patch-8.1.0') > 0 > > This should return 1. > A patch attached. > > NOTE: > This issue was reported by Takuya Fujiwara. > > -- > Best regards, > Hirohito Higashi (h_east) I disagree. There never was a patch

Re: Patch 8.1.0374

On Wed, Sep 12, 2018 at 11:16 PM Bram Moolenaar wrote: > > > Patch 8.1.0374 > Problem:Moving the cursor is slow when 'relativenumber' is set. > Solution: Only redraw the number column, not all lines. > Files: src/screen.c, src/move.c I just noticed the following message in Huge, Big

Re: When using diff I am getting "E959: Invalid diff format" in master gVim on Windows

On Wed, Sep 12, 2018 at 11:19 AM Igor Forca wrote: > > Now I set > :set diffopt+=internal diffexpr= > in $VIMRC file, > restarted the gVim and now it works fine. > > Still it is interesting gVim v8.1.0359 works fine without above setting, > but v8.1.0366 only works if above setting is set. Until

Re: Patch 8.1.0369

ooglegroups.com. For more options, visit https://groups.google.com/d/optout. # HG changeset patch # User Tony Mechelynck # Parent 8014307a918820085ed49a07995c3c4c10373ba1 Fix typo in comment continuation documentation diff --git a/runtime/doc/repeat.txt b/runtime/doc/repeat.txt --- a/runti

Re: Highlighting in the quickfix list

On Thu, Aug 30, 2018 at 7:38 AM Christian Brabandt wrote: > > > On Mi, 29 Aug 2018, Jason Franklin wrote: > > > Greetings, > > > > Just throwing this out there to see if it's possible. > > > > I'd like some improved highlighting when I'm browsing the quickfix list. To > > see what I mean, take a

Re: Leveraging the new 'incsearch' functionality from a Vim plugin

On Thu, Aug 30, 2018 at 5:33 AM Yegappan Lakshmanan wrote: > > Hi, > > Is it possible for a Vim plugin use the new 'incsearch' functionality > in a custom command? For example, I would like to enable this > functionality for the new cfilter plugin. The cfilter plugin adds a > command ":Cfilter"

Re: Link error if eval feature not included after patches 8.1. 311-313

Ha! Brenton Horne beat me to the ball. Best regards, Tony. -- -- 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 because you

Link error if eval feature not included after patches 8.1. 311-313

After applying patches 8.1.311 to 8.1.311, I get a link error in the Tiny build (shown below) and also in Small (the same error, not shown). These two builds are without expression evaluation, which makes me think that an #ifdef was forgotten in src/memline.c around the "dictionary" operations

Re: ATTENTION message with spurious (still running) warning

On Tue, Aug 21, 2018 at 3:57 PM, Bram Moolenaar wrote: > > Tony wrote: > >> If Vim is reloaded after a crash there will usually be one or more >> ATTENTION (E325) messages. This is usually no problem for me as I save >> my work at regular intervals, which means that I can usually delete >> the

Re: Patch 8.1.0306

On Tue, Aug 21, 2018 at 3:12 PM, Bram Moolenaar wrote: > > Patch 8.1.0306 > Problem:Plural messages are not translated properly. > Solution: Add more usage of NGETTEXT(). (Sergey Alyoshin) > Files: src/vim.h, src/buffer.c, src/ex_cmds.c, src/ex_docmd.c, > src/fileio.c,

ATTENTION message with spurious (still running) warning

If Vim is reloaded after a crash there will usually be one or more ATTENTION (E325) messages. This is usually no problem for me as I save my work at regular intervals, which means that I can usually delete the swapfiles left standing after the crash (they will have "modified: no"). However

Re: Comments halfway continuation lines

P.S. Inside a single-quoted string, \c means "backslash followed by c" and we want to keep that; so I propose the following three constructs: '\c ... some comment ... \c '\c ... some comment ... \c' '\c ... some comment ... \c'' (all inside an already-started single-quoted comment) to mean (I'm

Re: Comments halfway continuation lines

On Mon, Aug 20, 2018 at 1:18 PM, Bram Moolenaar wrote: > > Tony Mechelynck wrote: >> [...] >> Fixed-form COBOL (the only kind I knew), where comments had to be on >> their own lines (with an asterisk in column 7 IIRC), and continuation >> lines had a dash in the

Re: Comments halfway continuation lines

On Mon, Aug 20, 2018 at 10:06 AM, Bram Moolenaar wrote: > >> On Monday, August 20, 2018 at 1:37:53 AM UTC+9, Bram Moolenaar wrote: >> > Currently, when making a list with continuation lines, it is not >> > possible to add a comment somewhere: >> > >> > let array = [ >> > \ item,

Re: Comments halfway continuation lines

On Sun, Aug 19, 2018 at 6:37 PM, Bram Moolenaar wrote: > > Currently, when making a list with continuation lines, it is not > possible to add a comment somewhere: > > let array = [ > \ item, > \ item, > \ item, > \] > >

Re: Patch 8.1.0294

On Sun, Aug 19, 2018 at 10:38 AM, Axel Bender wrote: > Probably correlated with this patch (did not bisect, but must have happened > between 292 and 296 inclusively), but the following command stopped to work > for me on Windows: > > gvim.exe --servername GVX --remote-silent +"silent! bwipeout

Re: current version funny

On Mon, Aug 13, 2018 at 12:13 AM, tooth pik wrote: > i see a patch 279 in the list, but my vim is 278 and git is telling me > i have current > source Mercurial tells me the same thing. Apparently the latest patch, «'incsearch' highlighting does not skip white space.», did not make it to the

Re: Uganda visit report

On Fri, Aug 10, 2018 at 4:45 PM, Bram Moolenaar wrote: > > Hello Vimmers, > > I have visited Vim's charity project in June. I finally had time to > finish writing my report and organise the pictures. You can find it > here: http://www.iccf.nl/news.html > > It has links to the photo album and a

Re: Patch 8.1.0256

> If "R" is Reverse, how come "D" is FORWARD? because scanning "forward" toward the D does it forward while scanning "reverse" toward the R does it backward. :-P -- -- You received this message from the "vim_dev" maillist. Do not top-post! Type your reply below the text you are replying to.

RFE: Need a plural form?

When I hit u immediately after a chage has happened (the change may have needed a bit of computation, e.g. after triggering the CloseTag plugin at the end of a long HTML file to check that there are no stray unpaired tags) I sometimes see (if I do it very fast after the change) "1 seconds ago"

Re: Patch 8.1.0245

On Tue, Aug 7, 2018 at 11:00 PM, Christ van Willegen wrote: > Hi, > > > > Op di 7 aug. 2018 19:05 schreef Bram Moolenaar : >> >> >> Patch 8.1.0245 >> Problem:Calling setline() in TextChangedI autocmd breaks undo. (Jason >> Felice) >> Solution: Don't save lines for undo when

Re: Deleting the A-A-P recipe

On Tue, Aug 7, 2018 at 2:55 PM, Bram Moolenaar wrote: > > Is anyone building Vim using src/main.aap? I can't talk for other people, but I can guess. I think the most "popular" ways of getting Vim (in no particular order) are the following: * Find a precompiled executable with its runtime files,

Re: Allow clicking away from cmdline

On Sun, Aug 5, 2018 at 3:26 PM, Jason Franklin wrote: > I noticed that while editing the command line, I can't click away to focus on > a window. This is mildly annoying to me for whatever reason, so I fixed it. > > 1. Open a bunch of windows. > 2. Edit the cmdline with ":test" > 3. Try to left

Re: autochdir feature not seen by has() and :version

On Fri, Jul 27, 2018 at 5:40 PM, wrote: > On Friday, July 27, 2018 at 12:50:44 AM UTC-4, Tony Mechelynck wrote: >> On Fri, Jul 27, 2018 at 3:41 AM, wrote: >> > If Vim is built with the 'autochdir' feature defined, it is not reported >> > as such by the ":ver

Re: autochdir feature not seen by has() and :version

On Fri, Jul 27, 2018 at 3:41 AM, wrote: > If Vim is built with the 'autochdir' feature defined, it is not reported as > such by the ":version" command and has('autochdir') returns zero. Maybe this is only a documentation error under :help 'autochdir' ? Such a feature is also not mentioned

Warning in Tiny and Small at ex_docmd.c line 10657 after applying patches 210 to 213

After applying patches (8.1.)210 to 213 I get the following message in Tiny and Small (shown here for Small) but not for the other featuresets: gcc -c -I. -Iproto -DHAVE_CONFIG_H -DFEAT_GUI_MOTIF -O2 -fno-strength-reduce -Wall -U_FORTIFY_SOURCE -D_FORTIFY_SOURCE=1 -o objects/ex_docmd.o

Re: Configure script should fail when --with-x=yes and --enable-gui are set but needed dependencies are missing

On Fri, Jul 20, 2018 at 12:39 PM, wrote: > Hi, > > I was trying to compile Vim with GUI on Fedora Server. I used configure > options: > > ./configure --with-x=yes --with-tlib=ncurses --with-features=huge > --enable-gui=gtk3 > > and compilation went smoothly, but when I ran created binary, it

Re: problem about refresh screen of vim

On Mon, Jul 16, 2018 at 3:45 AM, 许建 <17120...@bjtu.edu.cn> wrote: > Dear developers, > Iam a beginner of Linux programming. In amiga.c, source code of vim1.14, I > found this: > > 75 flushbuf() > 76 { > 77 if (bpos != 0) > 78 Write(raw_out, (char

Re: How to determine the x and y position of the Vim text window on screen

On Sat, Jul 14, 2018 at 1:30 AM, tooth pik wrote: > are you looking for :winpos? No, according to earllier posts in this thread he doesn't want to know the pixel position of the Vim screen relative to the desktop, but the position in character cells of the current window (containing one view on

Re: [vim/vim] Change in paren matching from 8.0.0386 to 8.0.1298? (#3190)

On Wed, Jul 11, 2018 at 1:31 AM, tlathm wrote: > I'll try that test with --clean however first I need to clear up some > unspeakable confusion: If I use vim --clean it appears that the paren > matching is totally disabled. I've read countless conflicting things as to > how to enable that. I'm

Re: Patch 8.1.0177

On Tue, Jul 10, 2018 at 7:39 PM, Bram Moolenaar wrote: > > Patch 8.1.0177 > Problem:Defining function in sandbox is inconsistent, cannot use :function > but can define a lambda. > Solution: Allow defining a function in the sandbox, but also use the sandbox > when

Re: Compiler warning undo.c on Windows 7

On Tue, Jul 10, 2018 at 3:07 PM, Bram Moolenaar wrote: > > Axel Bender wrote: > >> Compiling gVim 8.1 (latest) on Windows 7 64-bit with MinGW gcc 7.30 64-bit I >> receive the following compiler warning in file undo.c: >> >> gcc -c -Iproto -DWIN32 -DWINVER=0x0600 -D_WIN32_WINNT=0x0600

Re: Compiler warning in userfunc.c

On Mon, Jul 9, 2018 at 9:32 AM, Dominique Pellé wrote: > Axel Bender wrote: > >> Compiling gVim 8.1 (latest) on Windows 7 64-bit with MinGW gcc 7.30 64-bit I >> receive the following compiler warning in file userfunc.c: >> >> gcc -c -Iproto -DWIN32 -DWINVER=0x0600 -D_WIN32_WINNT=0x0600

Re: Patch 8.1.0168

On Sun, Jul 8, 2018 at 5:57 PM, Bram Moolenaar wrote: > > Patch 8.1.0168 > Problem:Output of :marks is too short with multi-byte chars. (Tony > Mechelynck) > Solution: Get more bytes from the text line. > Files: src/mark.c, src/testdir/test_ma

Re: :marks truncation

On Sun, Jul 8, 2018 at 3:29 PM, Bram Moolenaar wrote: > > Tony wrote: > >> When typing ":marks" in a file with long lines, I notice that the text >> of the marked lines is truncated after a number of _bytes_ (including >> line number etc.) equal to the 'columns' setting; in partly non-ASCII >>

:marks truncation

When typing ":marks" in a file with long lines, I notice that the text of the marked lines is truncated after a number of _bytes_ (including line number etc.) equal to the 'columns' setting; in partly non-ASCII text (and for example in my Russian dictionary mixing Russian (Cyrillic) and French

Re: Patch 8.1.0162

P.S. I wonder why the Italian manpages, but not those in other languages, have the "executable" bit set (-rwxr-xr-x 0755 rather than -rw-r--r-- 0644 like all the others). Maybe they were originally produced on DOS/Windows, where there is no such thing as an "execute" permission? Both .info files

Re: Patch 8.1.0162

On Sat, Jul 7, 2018 at 10:27 PM, Bram Moolenaar wrote: > > Patch 8.1.0162 > Problem:Danish and German man pages are not installed. (Tony Mechelynck) > Solution: Adjust the makefile > Files: src/Makefile After applying this patch, then running "make" (appar

Re: Patch 8.1.0160

On Sat, Jul 7, 2018 at 5:22 PM, Bram Moolenaar wrote: > > Patch 8.1.0160 > Problem:No Danish manual translations. > Solution: Add the Danish manual translations to the file list. > Files: Filelist Shouldn't the src/Makefile also be updated? AFAICT, by both looking into the

Re: [PATCH] Copy Make_all.mak to SHADOWDIR

On Thu, Jul 5, 2018 at 11:46 AM, Elimar Riesebieter wrote: > * Tony Mechelynck [2018-07-05 11:39 +0200]: > >> On Thu, Jul 5, 2018 at 11:30 AM, Elimar Riesebieter >> wrote: >> > * Tony Mechelynck [2018-07-05 09:49 +0200]: >> > >> > [...] >> &

Re: [PATCH] Copy Make_all.mak to SHADOWDIR

On Thu, Jul 5, 2018 at 11:30 AM, Elimar Riesebieter wrote: > * Tony Mechelynck [2018-07-05 09:49 +0200]: > > [...] > >> Since there is no reason a user would modify the Make_all.mak, a link >> is enough (like for most other sources) -- see attached patch. > &

Re: [PATCH] Copy Make_all.mak to SHADOWDIR

On Thu, Jul 5, 2018 at 8:06 AM, Elimar Riesebieter wrote: > To build vim in SHADOWDIR we need to copy Make_all.mak as well to > $(SHADOWDIR). > > --- > src/Makefile | 2 +- > 1 file changed, 1 insertion(+), 1 deletion(-) > > diff --git a/src/Makefile b/src/Makefile > index 2c4421ee2..016046fd5

Re: [vim/vim] Possibly missing evim.man file (#3151)

On Wed, Jul 4, 2018 at 2:33 AM, scootergrisen wrote: > How come the other files have a .man file but not evim? On my system, where there is an own-compiled Vim 8.1 (8.1.146 as of this writing) and (further down the $PATH) a Vim 8.0.1568 from my Linux distro, I see at the bottom "2006 Apr 11" in

Re: Error when trying to compile vim with statically linked python

I don't have this problem on Linux. Is it MinGW (or MinGW-x64)-only or does it also happen on other configurations? My Huge Vim (8.1.136 as of this writing) is configured with static Python (2.7.14 as distributed with openSUSE 15.0), and my gcc version is 7.3.1 (also distributed with openSUSE

Re: Patch 8.1.0128

On Sun, Jul 1, 2018 at 2:59 AM, John Little wrote: > On Sunday, July 1, 2018 at 2:28:04 AM UTC+12, Bram Moolenaar wrote: >> Patch 8.1.0128 > > Just noticed version.c on github doesn't have patch number 128. No effect, > other than a little confusion. > > Regards, John Little Nor does it on the

Re: Visual Studio 2017 fails to compile one of six Vims...

On Thu, Jun 28, 2018 at 11:34 PM, tux. wrote: > As some of you might know, I provide my own Windows Vim builds. My > latest hardware upgrade brought a new infrastructure though. > > I usually compile six Vims in a row: > > - x86 GVim without OLE > - x86 GVim with OLE > - x86 CLI Vim > - the same

Re: Command to get the help translations file and set language

Shouldn't the translated help files be (like the translated menu and messages files already are) part of Vim's version control system, i.e. shouldn't they live somewhere on Vim's git server (and therefore on its Mercurial mirror)? Then "make installruntime" (and therefore "make install") would

Re: Patch 8.1.0115

On Mon, Jun 25, 2018 at 12:06 AM, Bram Moolenaar wrote: > > Patch 8.1.0115 > Problem:The matchparen plugin may throw an error. > Solution: Change the skip argument from zero to "0". > Files: runtime/plugin/matchparen.vim Nit: We forgot to bump line 3, it still says «" Last Change:

Re: Error in matchparen.vim after applying patches 8.1.111 to 113 + runtime files

On Sun, Jun 24, 2018 at 11:36 PM, Christian Brabandt wrote: > > On So, 24 Jun 2018, Tony Mechelynck wrote: > >> It doesn't even apply. Here are my lines 115-130 of that script, > > I wonder why? I made the change against the repository version. The version I have is dat

Re: Error in matchparen.vim after applying patches 8.1.111 to 113 + runtime files

On Sun, Jun 24, 2018 at 10:21 PM, Christian Brabandt wrote: > > On So, 24 Jun 2018, Tony Mechelynck wrote: > >> At startup from a handcoded Session.vim I get this error (which I >> didn't get before with the same session script) >> >> Error d

Error in matchparen.vim after applying patches 8.1.111 to 113 + runtime files

At startup from a handcoded Session.vim I get this error (which I didn't get before with the same session script) Error detected while processing function 24_Highlight_Matching_Pair: line 97: E475: Invalid argument: 0 I get this several times, including when clicking the statusline of a

Re: i am such an ingrate, forgive me

On Sat, Jun 23, 2018 at 11:29 PM, Christ van Willegen wrote: > Do you have expandtabs set? That would explain this, I think... > > Christ van Willegen I haven't tried them yet, but I would expect :set vartabstop=4,20,10,8 to mean that hitting the tab key moves the cursor

Re: Patch 8.1.0104

On Sat, Jun 23, 2018 at 5:15 PM, Bram Moolenaar wrote: > > Patch 8.1.0104 > Problem:Can't build without the +eval feature. > Solution: Add #ifdef. > Files: src/regexp_nfa.c Now my Tiny build compiles again. Thanks Bram! Best regards, Tony. -- -- You received this message from the

Re: Patch 8.1.0102

On Sat, Jun 23, 2018 at 3:09 PM, Bram Moolenaar wrote: > > Patch 8.1.0102 > Problem:Cannot build without syntax highlighting. > Solution: Add #ifdef around using reg_do_extmatch. > Files: src/regexp.c After applying this patch, my Tiny build has two fewer errors compared with patch

Re: Patch 8.1.0098

On Sat, Jun 23, 2018 at 2:21 PM, Bram Moolenaar wrote: > > Patch 8.1.0098 > Problem:Segfault when pattern with \z() is very slow. > Solution: Check for NULL regprog. Add "nfa_fail" to test_override() to be > able to test this. Fix that 'searchhl' resets called_emsg. > Files:

Re: Warning when compiling 8.1.89 os_unix.c

On Thu, Jun 21, 2018 at 10:37 AM, Gary Johnson wrote: > On 2018-06-20, Gary Johnson wrote: >> On 2018-06-20, Bram Moolenaar wrote: >> > Gary Johnson wrote: >> > >> > > When compiling Vim 8.1.89 on an Ubuntu Linux system, I get the >> > > following warning. >> > > >> > > os_unix.c: In function

Re: Patch 8.1.0078

On Wed, Jun 20, 2018 at 5:59 AM, Ken Takata wrote: > Hi Bram, > > 2018/6/19 Tue 21:24:20 UTC+9 Bram Moolenaar wrote: >> Patch 8.1.0078 >> Problem:"..." used inconsistently in messages. >> Solution: Drop the space before " ...". >> Files:src/spellfile.c, src/regexp_nfa.c > > One

Re: [vim/vim] langremap doesn't work for Cyrillic letters (#3018)

On Tue, Jun 19, 2018 at 11:42 AM, Christian Brabandt wrote: > Hm, the macro that is responsible for the langmap feature is LANGMAP_ADJUST. > I noticed it works on single bytes, e.g. what is in the input queue buffer. > However the cyrillic character о ('о' U+043E Dec:1086 CYRILLIC SMALL LETTER >

Re: Patch 8.1.0030

On Mon, Jun 4, 2018 at 11:14 AM, Marius Gedminas wrote: > On Sun, Jun 03, 2018 at 05:11:43PM +0200, Bram Moolenaar wrote: >> Patch 8.1.0030 >> Problem:Stoping Vim running in a terminal may not work. >> Solution: Instead of sending send CTRL-O. > >> ***

Re: feature to differentiate 32 from 64 bits build version

On Thu, May 24, 2018 at 11:38 AM, Andreas wrote: > What about just testing sizeof(void *)==8 ? > Regards > anst That won't work, because we want a solution for vimscript, not for C: :echo sizeof(void *) E121: Undefined variable: void E116: Invalid arguments for function

Re: feature to differentiate 32 from 64 bits build version

On Wed, May 23, 2018 at 3:14 PM, Ken Takata wrote: > Hi, > > 2018/5/23 Wed 21:29:43 UTC+9 Ni Va wrote: >> I build both 32 and 64 bits version of gvim but always 1 is returned when >> from 32bits or 64bits I do : >> >> echo has('num64') >> echo has('win32') >> echo

<    1   2   3   4   5   6   7   8   9   10   >