Re: Segfault on 7.4 caused by syntax :on with Ruby file

On Tue, Aug 13, 2013 at 09:03:36PM +0200, Dominique Pellé wrote: > I could narrow it down further. I can reproduce it with: > > # Create a file (6 space and a x, bug does not happen with less than 6 > spaces): > $ echo " x" > foo > $ valgrind --log-file=valgrind.log vim -u NONE -N -c 'syn o

Re: Segfault on 7.4 caused by syntax :on with Ruby file

On 14 August 2013 05:03, Dominique Pellé wrote: > I could narrow it down further. I can reproduce it with: > > # Create a file (6 space and a x, bug does not happen with less than 6 > spaces): > $ echo " x" > foo > $ valgrind --log-file=valgrind.log vim -u NONE -N -c 'syn on' foo > > Then

Re: Particular Regex Appears Region Broken in 7.4

Alright, so I am admittedly terrible with Regexes, but I think I did find something. Using this file for the regex test: https://gist.github.com/amadeus/82d0288a9b8b2e3ff2a9 And using this regex in search, with hlsearch on: \(\(\(return\|case\)\s\+\)\@<=\|\(\([)\]"']\|\d\|\w\)\s*\)\@ I am pret

Re: [PATCH] make adding new letters to arabic.c easier

On 13/08/13 14:54, Ameretat Reith wrote: On Friday, June 12, 2009 8:08:22 PM UTC+4:30, Ali Gholami Rudi wrote: Bram Moolenaar wrote: Ali Gholami Rudi wrote: After testing it some more, I've updated the patch. It seems almost stable, so I urge arabic.c users to give it a try. Bram, as mentio

Re: Particular Regex Appears Region Broken in 7.4

I am pretty bad with regex stuff, but I will try to figure out how to isolate it. I posted it here quickly just in case there was something silly I was missing in that snippet. For what it's worth, it's used in this syntax plugin: http://github.com/pangloss/vim-javascript And setting the reg

RFC/PATCH: completion should first suggest current buffer when direction switches

Hello. This is more a question to experts than finalized patch: I am not sure that my approach is correct and it breaks one test, but I attach the patch, just to clarify what I mean to do. The problem I encoutered when whole-line completion started to consider other buffers is that it is not easy

Re: Segfault on 7.4 caused by syntax :on with Ruby file

Dominique Pellé wrote: > Christopher Chow wrote: > >> When I start vim with vim -u NONE -N with the following code in a ruby file: >> >> class Billing::EstimatedImportStrategy < Billing::GapImportStrategy >> def applicable? >> has_previous_and_next_data? && has_historic_amount_data? >> end

Re: Particular Regex Appears Region Broken in 7.4

Amadeus Demarzi wrote: > With the update to vim 7.4, it seems as if this particular regex just > doesn't match in particular cases in 7.4, but it worked fine in 7.3. > > syntax region jsRegexpString > start=+\(\(\(return\|case\)\s\+\)\@<=\|\(\([)\]"']\|\d\|\w\)\s*\)\@ skip=+\|\\/+ end=

Vim syntax file should not require interpreter support to highlight :{interp}<

I see that all g:vimsyn_embed flags say things like “embed … **(but only if vim supports it)**”. This is ridiculous: you don’t have to have vim lua support to code in lua and have syntax highlighting; you specifically don’t have to have vim lua support to write or watch lua

Particular Regex Appears Region Broken in 7.4

With the update to vim 7.4, it seems as if this particular regex just doesn't match in particular cases in 7.4, but it worked fine in 7.3. syntax region jsRegexpString start=+\(\(\(return\|case\)\s\+\)\@<=\|\(\([)\]"']\|\d\|\w\)\s*\)\@http://www.vim.org/maillist.php --- You received this m

Re: [PATCH] make adding new letters to arabic.c easier

On Friday, June 12, 2009 8:08:22 PM UTC+4:30, Ali Gholami Rudi wrote: > Bram Moolenaar wrote: > > Ali Gholami Rudi wrote: > > > After testing it some more, I've updated the patch. It seems almost > > > stable, so I urge arabic.c users to give it a try. > > > > > > Bram, as mentioned arabic.h hol

Re: Bug: writing encrypted file, while asked for password, destroys contents

Ingo Karkat wrote: > On 13-Aug-2013 11:15 +0200, Bram Moolenaar wrote: > > > Einar Lielmanis wrote: > > > >> Encrypted file contents are destroyed, if something (e.g autocmd) > >> triggers write event, while user is being asked for password. > >> > >> To repro: > >> 1. have an encrypted.txt rea

Re: Bug: writing encrypted file, while asked for password, destroys contents

On Tue, August 13, 2013 01:00, Einar Lielmanis wrote: > Encrypted file contents are destroyed, if something (e.g autocmd) > triggers write event, while user is being asked for password. > > To repro: > 1. have an encrypted.txt ready (:X) > 2. gvim, :au focuslost * w > 3. :e encrypted.txt, don't typ

Re: Troyan horse in vimrun.exe ?

On 13/08/13 13:30, Joost Andrae wrote: Hi, I've re-built Vim 7.4 (32 bit) without using upx and suddenly the antivirus software doesn't quarantine the vimrun.exe file. Good! It was a false alarm then. Unfortunately Cygwin's strip command doesn't strip much of the file size... Well, what "s

Re: Troyan horse in vimrun.exe ?

Hi, I've re-built Vim 7.4 (32 bit) without using upx and suddenly the antivirus software doesn't quarantine the vimrun.exe file. Unfortunately Cygwin's strip command doesn't strip much of the file size... > > Do you still get the same error if you _don't_ pack the executables with > upx?

Re: Bug: writing encrypted file, while asked for password, destroys contents

On 13-Aug-2013 11:15 +0200, Bram Moolenaar wrote: > Einar Lielmanis wrote: > >> Encrypted file contents are destroyed, if something (e.g autocmd) >> triggers write event, while user is being asked for password. >> >> To repro: >> 1. have an encrypted.txt ready (:X) >> 2. gvim, :au focuslost * w >

Re: Bug: writing encrypted file, while asked for password, destroys contents

Einar Lielmanis wrote: > Encrypted file contents are destroyed, if something (e.g autocmd) > triggers write event, while user is being asked for password. > > To repro: > 1. have an encrypted.txt ready (:X) > 2. gvim, :au focuslost * w > 3. :e encrypted.txt, don't type in the password yet, > 4.

Re: Troyan horse in vimrun.exe ?

Hi Tony, thank you very much for your reply. > > Do you still get the same error if you _don't_ pack the executables with > upx? Packing executables is something which can be done with any > program, good or bad, and if your antivirus software has imprecise > signatures generated from the "packi