2016年12月8日木曜日 0時22分59秒 UTC+9 kashew_nuts:
> You can view, comment on, or merge this pull request online at:
>
> https://github.com/vim/vim/pull/1313
>
> Commit Summary
>
> fix indent
>
>
> File Changes
>
>
> M
> src/misc2.c
> (2)
>
>
>
> Patch Links:
>
>
Hi
Attached patch improves test coverage of ex_getln.c
to test:
- CTRL-\ e {expr} as described in :help c_CTRL-\_e
- deletion of characters with Del, BS, CTRL-W, CTRL-U
Regards
Dominique
--
--
You received this message from the "vim_dev" maillist.
Do not top-post! Type your reply below the
On Mi, 07 Dez 2016, Christian Brabandt wrote:
> ah yes I can reproduce it. Will look into it. thanks.
Here is a patch.
Best,
Christian
--
Das Leben ist wie eine Achterbahn. Mal wird Dir schlecht, mal willst Du
nochmal fahren.
--
--
You received this message from the "vim_dev" maillist.
Do
On 2016-12-07, Christian Brabandt wrote:
> Hi Gary!
>
> On Mi, 07 Dez 2016, Gary Johnson wrote:
>
> > On 2016-09-28, Christian Brabandt wrote:
> >
> > > Let me just withdraw the patch. I use async feature now to workaround.
> >
> > I recently had a need to save and restore the value of
Several weeks ago when I first noticed the spurious files, I quickly
realized it was not a Vim problem. So I transferred my report to Linux
Questions. Soon thereafter I found it was a grep regression. Slackware
fixed it's version & "upstream" was made aware of it. Thanks for the note.
I should
Hi Gary!
On Mi, 07 Dez 2016, Gary Johnson wrote:
> On 2016-09-28, Christian Brabandt wrote:
>
> > Let me just withdraw the patch. I use async feature now to workaround.
>
> I recently had a need to save and restore the value of v:shell_error
> and went looking for this discussion. I had
On 2016-09-28, Christian Brabandt wrote:
> Let me just withdraw the patch. I use async feature now to workaround.
I recently had a need to save and restore the value of v:shell_error
and went looking for this discussion. I had forgotten that you
withdrew the patch. FWIW, here's my workaround.
Grep-2.27 was released today and should contain the fix for this
problem.
Regards,
Gary
--
--
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
Op 7 dec. 2016 17:03 schreef "lacygoill" :
I don't know where to find the patch and how to apply it..
If it's correct, it will be applied by Bram Moolenaar and distributed in an
official version. You'll just have to wait...
Christ van Willegen
--
--
You received
Hi lacygoill,
2016-12-8(Thu) 1:03:00 UTC+9 lacygoill:
> Thank you very much for the answer! I'm sorry I don't know much about git and
> programming. I don't know where to find the patch and how to apply it.. I
> just found this bug and wanted to report it to you. Again sorry for my lack
> of
Hi James!
2016-12-8(Thu) 1:01:15 UTC+9 James McCoy:
> My real name is Kashun Yoshida!
>
>
> So update your GitHub profile to show that. :)
It maybe true.
However, I have not registered my real name on GitHub, but Bram has recognized
that Github's h-east is Hirohito Higashi.
Probably, I think
Hi lacygoill,
2016-12-7(Wed) 13:26:25 UTC+9 lacygoill:
> Hello,
>
> If I write the following in /tmp/vimrc.vim:
>
> setlocal tw=78
> setlocal cc=78
>
> "zzz
> " zzzyyy
>
>
>
> Then I launch Vim from the shell like this:
Hi Duncan,
2016-12-7(Wed) 17:10:17 UTC+9 Duncan McDougall:
> I have updated this to be in sync with master again. With help I found a
> cleaner way to do this.
>
> I do not understand why the test coverage has reduced, as there is a test..
> Perhaps this is because of the additions to the
13 matches
Mail list logo