2018-03-19 7:32 GMT+09:00 Manuel Ortega :
> On Sun, Mar 18, 2018 at 5:04 PM, Kazunobu Kuriyama <
> kazunobu.kuriy...@gmail.com> wrote:
>
>> 2018-03-19 5:25 GMT+09:00 Manuel Ortega :
>>
>>>
>>>
>>> Finally, another reason to not put "!" in &cpo by default just yet is
>>> that the colors are hard to
2018-03-19 7:24 GMT+09:00 Manuel Ortega :
> On Sun, Mar 18, 2018 at 5:04 PM, Kazunobu Kuriyama <
> kazunobu.kuriy...@gmail.com> wrote:
>
>> 2018-03-19 5:25 GMT+09:00 Manuel Ortega :
>>
>>> On Sun, Mar 18, 2018 at 4:10 PM, Kazunobu Kuriyama <
>>> kazunobu.kuriy...@gmail.com> wrote:
>>>
2018-03
Hi
Attached is a nit-picky parentheses mismatch patch in
runtime/doc/eval.txt
Regards
Dominique
--
--
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
---
Yo
On Sun, Mar 18, 2018 at 5:04 PM, Kazunobu Kuriyama <
kazunobu.kuriy...@gmail.com> wrote:
> 2018-03-19 5:25 GMT+09:00 Manuel Ortega :
>
>>
>>
>> Finally, another reason to not put "!" in &cpo by default just yet is
>> that the colors are hard to read if your colorscheme has a black or nearly
>> bla
On Sun, Mar 18, 2018 at 5:04 PM, Kazunobu Kuriyama <
kazunobu.kuriy...@gmail.com> wrote:
> 2018-03-19 5:25 GMT+09:00 Manuel Ortega :
>
>> On Sun, Mar 18, 2018 at 4:10 PM, Kazunobu Kuriyama <
>> kazunobu.kuriy...@gmail.com> wrote:
>>
>>> 2018-03-19 4:26 GMT+09:00 Bram Moolenaar :
>>>
Unti
On Sun, Mar 18, 2018 at 9:25 PM, Manuel Ortega wrote:
[...]
> But when using "!" in &cpo on MacVim, the blank line is in a different
> place. It's right below `:!ls`, and before the output of the `ls` command.
> Then the "Press ENTER" part has no blank line above it to separate it from
> the `ls`
2018-03-19 5:25 GMT+09:00 Manuel Ortega :
> On Sun, Mar 18, 2018 at 4:10 PM, Kazunobu Kuriyama <
> kazunobu.kuriy...@gmail.com> wrote:
>
>> 2018-03-19 4:26 GMT+09:00 Bram Moolenaar :
>>
>>>
>>> Until recently, the GUI used a "dumb" terminal for external commands.
>>> With patch 8.0.1616 it is now
On Sun, Mar 18, 2018 at 4:10 PM, Kazunobu Kuriyama <
kazunobu.kuriy...@gmail.com> wrote:
> 2018-03-19 4:26 GMT+09:00 Bram Moolenaar :
>
>>
>> Until recently, the GUI used a "dumb" terminal for external commands.
>> With patch 8.0.1616 it is now possible to run an external command inside
>> the GUI
2018-03-19 4:26 GMT+09:00 Bram Moolenaar :
>
> Until recently, the GUI used a "dumb" terminal for external commands.
> With patch 8.0.1616 it is now possible to run an external command inside
> the GUI window. Try it out with:
> :set go+=!
> :!cat testdir/color_ramp.txt
>
Seems l
Until recently, the GUI used a "dumb" terminal for external commands.
With patch 8.0.1616 it is now possible to run an external command inside
the GUI window. Try it out with:
:set go+=!
:!cat testdir/color_ramp.txt
Without adding "!" to 'guioptions' it doesn't work at all. On U
Hi Michael
Attached is a patch that improves the doxygen Vim syntax file:
- fixed the \param tag which was not properly highlighted
- added \related tag which is a synonym for \relates
- added \relatedalso tag which is a synonym for \relatesalso
- added \details tag
- small speedup when using "se
Patch 8.0.1616
Problem:Win32: shell commands in the GUI open a new console.
Solution: Use a terminal window for interactive use when 'guioptions'
contains "!".
Files: src/os_win32.c
*** ../vim-8.0.1615/src/os_win32.c 2018-03-08 22:03:09.867578790 +0100
--- src/os_win3
Patch 8.0.1615
Problem:term_dumpload() does not use the right colors.
Solution: Initialize colors when not using create_vterm().
Files: src/terminal.c
*** ../vim-8.0.1614/src/terminal.c 2018-03-18 19:11:34.589942285 +0100
--- src/terminal.c 2018-03-18 19:13:28.909168026 +010
2018-03-18 15:48 GMT+01:00 Bram Moolenaar :
>
> Justin M. Keyes wrote:
>
> I'm glad to give credits to developers who send me a patch that I can
> include and make Vim users happy. No matter where that code came from.
> Why give credit to NeoVim as a project, instead of its individual
> contributo
Boxu Zhang wrote:
> Hi Vims,
> I've fixed a crash when using vim-lldb plugin. You can view the reason
> here: https://github.com/boxu-zhang/vim
> The patch file is attched. Also you can view the patch on github:
> https://github.com/boxu-zhang/vim/commit/8752085132dcf2a44a5554ba1334d4687b
Justin M. Keyes wrote:
I'm glad to give credits to developers who send me a patch that I can
include and make Vim users happy. No matter where that code came from.
Why give credit to NeoVim as a project, instead of its individual
contributors? That would mean NeoVim helps Vim moving forward.
As
Le dimanche 18 mars 2018 12:24:38 UTC+1, Justin M. Keyes a écrit :
> 2018-03-11 16:04 GMT+01:00 Bram Moolenaar :
> >
> > Justin M. Keyes wrote:
> >
> >> 2018-03-08 18:05 GMT+01:00 Bram Moolenaar :
> >> >
> >> > I'm thinking of creating the 8.1 release. The main new feature is the
> >> > terminal w
Le jeudi 8 mars 2018 18:05:36 UTC+1, Bram Moolenaar a écrit :
> I'm thinking of creating the 8.1 release. The main new feature is the
> terminal window, with the debugger plugin. And lots of smaller
> additions and plenty of bug fixes.
>
> Is there is something important that should still be inc
2018-03-11 16:04 GMT+01:00 Bram Moolenaar :
>
> Justin M. Keyes wrote:
>
>> 2018-03-08 18:05 GMT+01:00 Bram Moolenaar :
>> >
>> > I'm thinking of creating the 8.1 release. The main new feature is the
>> > terminal window, with the debugger plugin. And lots of smaller
>> > additions and plenty of
19 matches
Mail list logo