On Aug 10, 2014, at 20:38, Bram Moolenaar wrote:
>
> Patch 7.4.399
> Problem:Encryption implementation is messy. Blowfish encryption has a
> weakness.
> Solution: Refactor the encryption, store the state in an allocated struct
> instead of using a save/restore mechanis
On Sunday, August 10, 2014 3:41:38 PM UTC-7, Bram Moolenaar wrote:
> Jacob Niehus wrote:
>
>
>
> > I narrowed it down to the point I can reproduce it with no
>
> > configuration file. Apparently keys typed while a shell command is
>
> > executing are drawn on screen immediately, then drawn aga
On Sunday, August 10, 2014 3:41:38 PM UTC-7, Bram Moolenaar wrote:
> Jacob Niehus wrote:
>
>
>
> > I narrowed it down to the point I can reproduce it with no
>
> > configuration file. Apparently keys typed while a shell command is
>
> > executing are drawn on screen immediately, then drawn aga
Christian wrote:
> On Mi, 06 Aug 2014, Bram Moolenaar wrote:
>
> > Patch 7.4.392
> > Problem:Not easy to detect type of command line window.
> > Solution: Add the getcmdwintype() function. (Jacob Niehus)
> > Files: src/eval.c
>
> I suspect, you already have documentation updated
Jacob Niehus wrote:
> I narrowed it down to the point I can reproduce it with no
> configuration file. Apparently keys typed while a shell command is
> executing are drawn on screen immediately, then drawn again after the
> command finishes. Also I should have mentioned before that this is not
>
Bram,
I narrowed it down to the point I can reproduce it with no configuration file.
Apparently keys typed while a shell command is executing are drawn on screen
immediately, then drawn again after the command finishes. Also I should have
mentioned before that this is not Cygwin-specific; it ju
On Mi, 06 Aug 2014, Bram Moolenaar wrote:
> Patch 7.4.392
> Problem:Not easy to detect type of command line window.
> Solution: Add the getcmdwintype() function. (Jacob Niehus)
> Files:src/eval.c
I suspect, you already have documentation updated but not yet pushed?
Best,
Christ
On 15:51 Sun 10 Aug , Bram Moolenaar wrote:
>
> I wrote:
>
> > Marcin Szamotulski wrote:
> >
> > > I wrote a patch which adds [count] to :colse, :hide and ^Wc normal
> > > command. When given the window with window number [count] will be
> > > closed/hidden. Sometimes I want to close not t
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
Scott Prager wrote:
> On Friday, August 8, 2014 4:03:32 PM UTC-4, Bram Moolenaar wrote:
>
> > I wonder, is an option the right way to change behavior?
>
> I've thought of three possibilities:
> 1) Make it a flag--one person suggested "-bfs". I tried this first, but
>don't understand how th
Hirohito Higashi wrote:
> Hi Bram and list,
>
> I add a special key name "\" for K_CURSORHOLD.
>
> How to reproduce:
> - Create ~/test.vim of the contents of the following.
> augroup hogehoge
> autocmd!
> autocmd CursorHold,CursorHoldI,WinEnter * setlocal cursorline
> augroup END
> fun
Hi Bram and list,
I add a special key name "\" for K_CURSORHOLD.
How to reproduce:
- Create ~/test.vim of the contents of the following.
augroup hogehoge
autocmd!
autocmd CursorHold,CursorHoldI,WinEnter * setlocal cursorline
augroup END
function! s:foo()
echomsg getchar()
return
On Friday, August 8, 2014 4:03:32 PM UTC-4, Bram Moolenaar wrote:
> I wonder, is an option the right way to change behavior?
I've thought of three possibilities:
1) Make it a flag--one person suggested "-bfs". I tried this first, but
don't understand how the "ex_" functions work yet, and I do
Seems to work now. Thanks! :-)
--
--
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 are subscribed to the Google Gr
Zeug wrote:
> I get a pretty lot of unresolved symbols with this build.
> (MSVC 2010)
>
> > ex_docmd.obj : error LNK2001: Nicht aufgelöstes externes Symbol
> > "_crypt_get_key".
> > fileio.obj : error LNK2001: Nicht aufgelöstes externes Symbol
> > "_crypt_encode_alloc".
> > fileio.obj : error
Patch 7.4.401 (after 7.4.399)
Problem:Can't build on MS-Windows.
Solution: Include the new files in all the Makefiles.
Files: src/Make_bc3.mak, src/Make_bc5.mak, src/Make_cyg.mak,
src/Make_dice.mak, src/Make_djg.mak, src/Make_ivc.mak,
src/Make_manx.mak, src/Make_
I get a pretty lot of unresolved symbols with this build.
(MSVC 2010)
> ex_docmd.obj : error LNK2001: Nicht aufgelöstes externes Symbol
> "_crypt_get_key".
> fileio.obj : error LNK2001: Nicht aufgelöstes externes Symbol
> "_crypt_encode_alloc".
> fileio.obj : error LNK2001: Nicht aufgelöstes ext
I wrote:
> Marcin Szamotulski wrote:
>
> > I wrote a patch which adds [count] to :colse, :hide and ^Wc normal
> > command. When given the window with window number [count] will be
> > closed/hidden. Sometimes I want to close not the current window but
> > another one, this command let to do th
Patch 7.4.400
Problem:List of distributed files is incomplete.
Solution: Add recently added files.
Files: Filelist
*** ../vim-7.4.399/Filelist 2014-05-13 13:52:34.817605451 +0200
--- Filelist2014-08-10 13:43:31.612781775 +0200
***
*** 11,16
--- 11,18
Patch 7.4.399
Problem:Encryption implementation is messy. Blowfish encryption has a
weakness.
Solution: Refactor the encryption, store the state in an allocated struct
instead of using a save/restore mechanism. Introduce the
"blowfish2" method, which doe
Jacob Niehus wrote:
> On Wednesday, July 16, 2014 9:18:53 AM UTC-7, Bram Moolenaar wrote:
> > Jacob Niehus wrote:
> >
> > > I agree with all of that in principle, but I've been able to reliably
> > > compile and with and without the screen_start() and see the problem go
> > > away with screen_st
> Hi
>
> Attached patch fixes several typos in Vim help files.
Thanks!
--
hundred-and-one symptoms of being an internet addict:
11. You find yourself typing "com" after every period when using a word
processor.com
/// Bram Moolenaar -- b...@moolenaar.net -- http://www.Moolenaar.net \\\
Jacob Niehus wrote:
> Having "search" set in the 'foldopen' option should cause folds to
> open to show a search result after selecting a previous search from
> the search command line history. This works as expected except when
> there are any CmdwinLeave autocommands. In that case, 'KeyTyped' g
23 matches
Mail list logo