Hi James,
2015/1/17(Sat) 9:56:56 UTC+9 James McCoy:
> On Fri, Jan 16, 2015 at 02:45:49PM -0800, h_east wrote:
> > Hi Bram and list,
> >
> > I found a strange code.
> >
> > ins_compl_bs() in src/edit.c : L3397
> > 3393 /* Stop completion when the whole word was deleted. For Omni
> > comple
On Friday, January 16, 2015 at 4:55:44 PM UTC-6, Christian Brabandt wrote:
> Hi Bram!
>
> On Fr, 16 Jan 2015, Bram Moolenaar wrote:
>
> >
> > Christian Brabandt wrote:
> > > Hm, we already have special cases and
> > > to move by word|WORD. So how about making and move
> > > without breakin
Hi Cesar,
2015/1/16 Fri 23:56:08 UTC+9 Cesar wrote:
> By compiling vim with DIRECTX=yes on Windows 7 with MinGW I get:
>
> --
> [...]
> gcc -c -Iproto -DWIN32 ... -DFEAT_DIRECTX -DDYNAMIC_DIRECTX
> -DFEAT_GUI_W32 -DFEAT_CLIPBOARD -DFEAT_MBYTE -DFEAT_MBYTE_IME
> -DDYNAMIC_IME -DDYNAMIC_I
Hi!
While working on Debian's “reproducible builds” effort [1], we have noticed
that vim has produced different documentation files on two successive builds
[2].
In one run a generated HTML file didn't contain links to tags, but did
so on another run (in an otherwise identical environment).
Afte
On Tuesday, September 14, 2010 at 8:14:49 AM UTC-4, Nikolai Weibull wrote:
> On Tue, Sep 14, 2010 at 03:23, forbin wrote:
> > On Sep 1, 10:54 am, ZyX wrote:
> >> I have written a syntax file for YAML markup language that has the
> >> following
> >> differencies with runtime/syntax/yaml.vim from
On Fri, Jan 16, 2015 at 02:45:49PM -0800, h_east wrote:
> Hi Bram and list,
>
> I found a strange code.
>
> ins_compl_bs() in src/edit.c : L3397
> 3393 /* Stop completion when the whole word was deleted. For Omni
> completion
> 3394 * allow the word to be deleted, we won't match ever
Comment #3 on issue 317 by danek.du...@gmail.com: Encryption Passphrase
Stored Unprotected in Memory
https://code.google.com/p/vim/issues/detail?id=317
There's a function, mlock(), which does exactly this. This will prevent
that section of memory from getting written to a core file, or fro
Hi Bram!
On Fr, 16 Jan 2015, Bram Moolenaar wrote:
>
> Christian Brabandt wrote:
>
> > On Fr, 16 Jan 2015, Ben Fritz wrote:
> >
> > > The problem is, there is no way to move the cursor in insert mode,
> > > without breaking the undo sequence. Such a capability would allow both
> > > of these m
Hi Bram and list,
I found a strange code.
ins_compl_bs() in src/edit.c : L3397
3393 /* Stop completion when the whole word was deleted. For Omni
completion
3394 * allow the word to be deleted, we won't match everything. */
3395 if ((int)(p - line) - (int)compl_col < 0
3396
Christian Brabandt wrote:
> On Fr, 16 Jan 2015, Ben Fritz wrote:
>
> > The problem is, there is no way to move the cursor in insert mode,
> > without breaking the undo sequence. Such a capability would allow both
> > of these mappings:
> >
> > inore ( () inore ) GetNextChar()==")" ? "\" : ")"
Comment #2 on issue 317 by chrisbr...@googlemail.com: Encryption Passphrase
Stored Unprotected in Memory
https://code.google.com/p/vim/issues/detail?id=317
Is this really a problem? Usually any normal user won't be able to trace
and dump the memory of even a process of the same user
(http
Hi Ben!
On Fr, 16 Jan 2015, Ben Fritz wrote:
> The problem is, there is no way to move the cursor in insert mode,
> without breaking the undo sequence. Such a capability would allow both
> of these mappings:
>
> inore ( () inore ) GetNextChar()==")" ? "\" : ")"
>
> Alternatively, there is no w
Comment #1 on issue 317 by fritzoph...@gmail.com: Encryption Passphrase
Stored Unprotected in Memory
https://code.google.com/p/vim/issues/detail?id=317
How exactly should Vim use a password, if it cannot keep it in memory?
I'd really love to know it if there is a concept of "protected" memor
Status: New
Owner:
Labels: Type-Defect Priority-Medium
New issue 318 by robert.p...@gmail.com: sh.vim syntax highlighting glitch
in shell patterns including a # inside bracket expression
https://code.google.com/p/vim/issues/detail?id=318
What steps will reproduce the problem?
1. Using th
Comment #3 on issue 212 by sw...@ingo-karkat.de: feedkeys(".", "n") inside
a macro inserts @. register instead of repeating last operation
https://code.google.com/p/vim/issues/detail?id=212
feedkeys() and macros don't play well together in general. While clever,
this looks too much like a h
Updates:
Labels: patch
Comment #2 on issue 212 by chrisbr...@googlemail.com: feedkeys(".", "n")
inside a macro inserts @. register instead of repeating last operation
https://code.google.com/p/vim/issues/detail?id=212
I have looked at the code. The problem is, when using the feedkeys(
On Thursday, January 15, 2015 at 9:16:27 PM UTC+9, Ingo Karkat wrote:
> Can you demonstrate that this is needed frequently? Which common tasks
> would benefit from this? (And why would a short library function not
> suffice?)
> e
> The only use case I've encountered so far is generating a list of
>
Status: New
Owner:
Labels: Type-Defect Priority-Medium
New issue 317 by troseph: Encryption Passphrase Stored Unprotected in Memory
https://code.google.com/p/vim/issues/detail?id=317
What steps will reproduce the problem?
1.Open Vim Encrypted File
2.Enter Passphrase
3.Dump heap memory for V
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hello Vim developers,
I use the easytags.vim plugin, which invokes another Vim instance, its
arguments properly escaped via shellescape(). On Windows, this doubles "
into "". Starting with
,[ Patch 7.4.432 ]
| MS-Windows: setting 'encoding' do
By compiling vim with DIRECTX=yes on Windows 7 with MinGW I get:
--
[...]
gcc -c -Iproto -DWIN32 ... -DFEAT_DIRECTX -DDYNAMIC_DIRECTX
-DFEAT_GUI_W32 -DFEAT_CLIPBOARD -DFEAT_MBYTE -DFEAT_MBYTE_IME
-DDYNAMIC_IME -DDYNAMIC_ICONV -pipe -w -march=i386 -Wall
-IC:/perl/lib/Core -DFEAT_PERL -D
I just ran into the same problem ended up here. I would appreciate if this
could get fixed.
I'm using version 7.4.567 on Mac OS. Thanks!
On Monday, September 15, 2014 at 6:21:23 AM UTC+2, v...@googlecode.com wrote:
> Comment #1 on issue 212 by jke...@connectwise.com: feedkeys(".", "n")
> insid
Christian Brabandt wrote:
> Hi Dominique!
>
> On Do, 15 Jan 2015, Dominique Pellé wrote:
>
>> Is there a 3000 characters limit in the regexp engine or in syntax
>> highlighting engine? I could not find any such limit in the source code.
>
> Could that be the synmaxcol setting?
>
>
> Best,
> Chris
22 matches
Mail list logo