REMOVE ME Re: patch for strong encryption in vim, resending patch for vim7* dev branch.

please remove me in the mailing list. 2010/3/22 Benjamin R. Haskell > On Sun, 21 Mar 2010, Bram Moolenaar wrote: > > > > > Benjamin R. Haskell wrote: > > > > > Also, you say you're not in the U.S., but Vim's hosted mostly on > > > Sourceforge (which is a U.S.-based entity), correct? > > > > The

[patch] C omni completion does not work

I don't know how this could have happened, but somehow since the last update to autoload/ccomplete.vim no-one complained about the C omni completion not working properly. The last update among other changes introduced this minor one which is the culprit. The attached patch reverts the change. I on

Re: patch for strong encryption in vim, resending patch for vim7* dev branch.

Dominique, The bf_self_test is important - it checks the constants have not been modified. There is a similar self test in sha2.c. I have some more ideas to enhance the feature: key strengthening, enhance the header to include filesize, salt for password. I would also like to run bf in cbc mod

Re: patch for strong encryption in vim, resending patch for vim7* dev branch.

Le Sun, 21 Mar 2010 19:07:37 +0100, Dominique Pellé a écrit dans le message  : > The patch is missing the changes to the Makefile (I needed > to add blowfish.c & sha2.c to the Makefile to be able to link > successfully). Yes, I'm waiting a full patch (-c) for testing warnings on Linux/Gcc 3.2 and

Incorrect type is used for memory size calculation.

Incorrect type is used for memory size calculation. Please check the following line. --- a/src/screen.c +++ b/src/screen.c @@ -7536,7 +7536,7 @@ new_ScreenLines = (schar_T *)lalloc((long_u)( (Rows + 1) * Columns * sizeof(schar_T)), FALSE); #ifdef FEAT_MBYTE -

Re: [patch] Uninitialized memory access in screen.c introduced by patch 7.2.119

Dominique Pellé wrote: Hi I see the following Valgrind error with Gvim-7.2.402 (GTK2 GUI on Linux). ==12686== Conditional jump or move depends on uninitialised value(s) ==12686==at 0x53A5E0: screen_comp_differs (screen.c:6294) ==12686==by 0x53AB30: screen_puts_len (screen.c:6456) ==1268

Re: patch for strong encryption in vim, resending patch for vim7* dev branch.

Mosh wrote: > Dominique, > Resending as a zip file. > thanks, > mohsin Hi Mosh, I tried your blowfish patch today. Here are some remarks. The patch is missing the changes to the Makefile (I needed to add blowfish.c & sha2.c to the Makefile to be able to link successfully). I compiled with -g -

Why is "CTRL-O u" so slow in insert mode?

See also vim_use thread with the same title. Using vimrc_example.vim as .vimrc, it appears that typing "CTRL-O u" in insert mode takes 2-3 s to execute. 1) Using an empty .vimrc and launching gvim --noplugin shows the delay. 2) Using gvim -u NONE does not show the delay. A priori, cases 1) and

[patch] Parsing the 'cino' value

This fixes a problem in get_c_indent() where during parsing the value of 'cino' including multiple options, the position of a pointer does not get updated properly. How to observe the problem? Currently there is no way to observe the problem. However, if the following new flags happen to be added,

[patch] New method for C code and expression indenting

I implemented an option for Vim which modifies the way C indenting is performed and the value returned by 'indentexpr' option affects indentation. The option has been described in todo.txt: 7 Use Tabs for the indent of starting lines, pad with spaces for continuation lines. Allows changing

Re: patch for strong encryption in vim, resending patch for vim7* dev branch.

On Sun, 21 Mar 2010, Bram Moolenaar wrote: > > Benjamin R. Haskell wrote: > > > Also, you say you're not in the U.S., but Vim's hosted mostly on > > Sourceforge (which is a U.S.-based entity), correct? > > The main Vim ftp server is in Amsterdam. Okay. I was going off of www.vim.org == source

--remote* cmds do not trigger autocmd on vim server

Hello guys, I found the --remote commands sending to the vim server do not trigger the autocmd events on the server at first. After that the events work fine. For example: Starting server: d:\> gvim -u NONE -N ^ -c "au! bufnew,winenter * echo 'Hello: '.expand('%')" ^ -c "set vbs=9" newfile

Re: [patch] fixed 2 more bugs in syntax highlighting of directories in wildmode=list

Dominique Pelle wrote: > Recent patch 7.2.401 fixed a bug with syntax highlighting of directories > with 'set wildmode=list'. I still see 2 other bugs with syntax highlighting > of directories. > > Bug #1: > > Starting vim with... > > $ vim -u NONE -c 'set nocompatible wildmode=list' > > ..

Re: patch for strong encryption in vim, resending patch for vim7* dev branch.

Benjamin R. Haskell wrote: > Also, you say you're not in the U.S., but Vim's hosted mostly on > Sourceforge (which is a U.S.-based entity), correct? The main Vim ftp server is in Amsterdam. There are mirrors all over the world. I don't see how the location of a server, that merely forwards by