Comment #3 on issue 250 by john.wel...@gmail.com: Random US-International
keyboard layout (dead keys) support
http://code.google.com/p/vim/issues/detail?id=250
Ok, I've made an interesting discovery that proves that it's not related to
Microsoft compiler as implied in
https://groups.googl
> I wonder if we can think of a better name for v:rhs.
We will be able to provide it as v:command for CmdUndefined. But we will have
to provode v:function for FuncUndefined.
> And what will v:lhs be used for exactly?
Currently none. reserved for future.
--
--
You received this message from t
Comment #2 on issue 250 by john.wel...@gmail.com: Random US-International
keyboard layout (dead keys) support
http://code.google.com/p/vim/issues/detail?id=250
In the past I remember testing several builds and if I remember correctly
some of the 'VIm without cream' builds did also exhibits
Olaf Dabrunz wrote:
> to reproduce this in vim:
>
> :echo system('md5sum', '')
> E677: Error writing temp file
>
> With the patch below, there is no error and the result is as expected:
>
> :echo system('md5sum', '')
> d41d8cd98f00b204e9800998ecf8427e -
>
> Tested against vim
Christian Brabandt wrote:
> On Di, 19 Aug 2014, Bram Moolenaar wrote:
>
> > Christian Brabandt wrote:
> >
> > > On Mo, 18 Aug 2014, Bram Moolenaar wrote:
> > >
> > > > Christian Brabandt wrote:
> > > > > > > I have found a breakindent bug.
> > >
> > > It's actually not a breakindent bug. The
Hello,
to reproduce this in vim:
:echo system('md5sum', '')
E677: Error writing temp file
With the patch below, there is no error and the result is as expected:
:echo system('md5sum', '')
d41d8cd98f00b204e9800998ecf8427e -
Tested against vim 7.4.000 on Ubuntu 12.04. The patch
On Di, 19 Aug 2014, Bram Moolenaar wrote:
> Christian Brabandt wrote:
>
> > On Mo, 18 Aug 2014, Bram Moolenaar wrote:
> >
> > > Christian Brabandt wrote:
> > > > > > I have found a breakindent bug.
> >
> > It's actually not a breakindent bug. The breakindent feature just makes
> > it more appa
Christian Brabandt wrote:
> On Mo, 18 Aug 2014, Bram Moolenaar wrote:
>
> > Christian Brabandt wrote:
> > > > > I have found a breakindent bug.
>
> It's actually not a breakindent bug. The breakindent feature just makes
> it more apparent. I can reproduce the issue on a plain 7.4 version.
> L
Dominique wrote:
> Attached patch fixes typos in Bram's name in
> French, Portuguese and Chinese tutor files.
Thanks!
--
You have the right to remain silent. Anything you say will be
misquoted, then used against you.
/// Bram Moolenaar -- b...@moolenaar.net -- http://www.Moolenaar.net \\\
Yukihiro Nakadaira wrote:
> According to :help arglistid(), it returns zero for invalid argument.
> But it returns -1 instead.
>
> diff -r 7af530381fec runtime/doc/eval.txt
> --- a/runtime/doc/eval.txtSun Aug 17 17:24:07 2014 +0200
> +++ b/runtime/doc/eval.txtTue Aug 19 21:28:25 2014 +09
Yasuhiro Matsumoto wrote:
> I implemented CmdUndefined autocmd that is listed in todo list.
>
> https://gist.github.com/mattn/a9591869fb5d4139a2aa
>
> http://marc.info/?l=vim-dev&m=100887940823495
> http://marc.info/?l=vim-dev&m=110788023426405
>
> I modified FuncUndefined also because add v:r
On Di, 19 Aug 2014, Tim Chase wrote:
> Playing around with the most recent vimgolf challenge, I was
> surprised by the following. To replicate the issue in a document with
> multiple different misspelled words:
>
> - :set spell
>
>
> - On a misspelled word (in the vimgolf case, this is "Mosst")
Comment #1 on issue 250 by chrisbr...@googlemail.com: Random
US-International keyboard layout (dead keys) support
http://code.google.com/p/vim/issues/detail?id=250
This has been reported before:
https://groups.google.com/d/msg/vim_dev/99DYFZvvBNE/xuwuWsZdc1IJ
sounded like a compiler bug to me
On Mo, 18 Aug 2014, Bram Moolenaar wrote:
> Christian Brabandt wrote:
> > > > I have found a breakindent bug.
It's actually not a breakindent bug. The breakindent feature just makes
it more apparent. I can reproduce the issue on a plain 7.4 version.
Looking at the mercurial repository, that par
On 19/08/14 16:17, Tux wrote:
Am 19. August 2014 16:13:36 MESZ, schrieb Bram Moolenaar :
Those numbers are for major and minor releases, not patchlevels.
Why does 7.4.410 still identify as 7.4.280 then? I guess in most OSs it doesn't
matter, but Windows (for example) shows the executable ve
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Am 19. August 2014 16:13:36 MESZ, schrieb Bram Moolenaar :
>Those numbers are for major and minor releases, not patchlevels.
Why does 7.4.410 still identify as 7.4.280 then? I guess in most OSs it doesn't
matter, but Windows (for example) shows
John Little wrote:
> On Tuesday, August 19, 2014 11:24:22 AM UTC+12, tux. wrote:
> > Is there any reason VIM_VERSION_BUILD is never increased beyond 280?
>
> in version.h
> #define VIM_VERSION_BUILD 280
>
> This also looks odd:
> #define VIM_VERSION_BUILD_BCD 0x118
>
> unl
According to :help arglistid(), it returns zero for invalid argument.
But it returns -1 instead.
diff -r 7af530381fec runtime/doc/eval.txt
--- a/runtime/doc/eval.txtSun Aug 17 17:24:07 2014 +0200
+++ b/runtime/doc/eval.txtTue Aug 19 21:28:25 2014 +0900
@@ -2113,7 +2113,7 @@
Return
Status: New
Owner:
Labels: Type-Defect Priority-Medium
New issue 250 by john.wel...@gmail.com: Random US-International keyboard
layout (dead keys) support
http://code.google.com/p/vim/issues/detail?id=250
What steps will reproduce the problem?
1. OS: Win7 64 (32bit GVIm build)
2. Use US-
Hi list.
I implemented CmdUndefined autocmd that is listed in todo list.
https://gist.github.com/mattn/a9591869fb5d4139a2aa
http://marc.info/?l=vim-dev&m=100887940823495
http://marc.info/?l=vim-dev&m=110788023426405
I modified FuncUndefined also because add v:rhs to handle function-name or
co
> Keys? v:key is list index, it cannot contain spaces.
> Spaces in values shouldn't matter.
> Not sure what you mean.
I wonder this won't works correctly.
[{"a": "b"}, {"a b": ""}]
--
--
You received this message from the "vim_dev" maillist.
Do not top-post! Type your reply below the text you
21 matches
Mail list logo
