Patch updated.
Note:
The change of doc/print.txt was discussed and confirmed at the following issue.
(in Japanese)
https://github.com/vim-jp/issues/issues/1243
--
Best regards,
Hirohito Higashi (h_east)
--
--
You received this message from the "vim_dev" maillist.
Do not top-post! Type your r
Hi Bram and list,
Please check an attached patch.
--
Best regards,
Hirohito Higashi (h_east)
--
--
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 r
Patch 8.1.1185
Problem:Mapping for CTRL-X is inconsistent.
Solution: Map CTRL-X to "*d also for the MS-Windows console. (Ken Takata,
closes #4265)
Files: src/getchar.c
*** ../vim-8.1.1184/src/getchar.c 2019-04-04 20:13:06.001014760 +0200
--- src/getchar.c 2019
Patch 8.1.1184
Problem:Undo file left behind after running test.
Solution: Delete the undo file. (Dominique Pelle, closes #4279)
Files: src/testdir/test_filechanged.vim
*** ../vim-8.1.1183/src/testdir/test_filechanged.vim2019-01-25
21:01:13.240877414 +0100
--- src/testdir/test_f
On Thursday, April 18, 2019 at 7:07:30 PM UTC+2, Manuel Ortega wrote:
> The :redraw was just an example to get you started. `:echo ""` or even
> `:echo` should work as well, and wouldn't require repainting the whole
> screen. I'm sure there are lots of other ways to do it; no need to add a new
On Thu, Apr 18, 2019 at 11:42 AM wrote:
> On Thursday, April 18, 2019 at 5:21:50 PM UTC+2, Manuel Ortega wrote:
> > Yes: all you need to do is use an autocommand event like say TabEnter
> or TabLeave to do e.g. ':silent redraw` whenever a tab is entered/left.
>
> That works, thank you! (Altough
On Thursday, April 18, 2019 at 5:21:50 PM UTC+2, Manuel Ortega wrote:
> Yes: all you need to do is use an autocommand event like say TabEnter or
> TabLeave to do e.g. ':silent redraw` whenever a tab is entered/left.
That works, thank you! (Altough it does make loading several files with 'vim
-p
On Thu, Apr 18, 2019 at 6:16 AM wrote:
> Hi,
>
> I'm the user who originally reported this.
>
> On Thursday, April 18, 2019 at 8:43:31 AM UTC+2, Christian Brabandt wrote:
> > Yes as mentioned before, it might be unexpected, that the last output
> > from a command or a plugin will be erased just b
On 2019-04-18, Chris White wrote:
> • In cxw42/editorconfig-vim@e885c43 I have added :EditorConfigDisable and
> :EditorConfigEnable. If this plugin were to be enabled by default, you
> could disable it with EditorConfigDisable in your vimrc.
Plugins are not sourced until after vimrc is
Hi,
I'm the user who originally reported this.
On Thursday, April 18, 2019 at 8:43:31 AM UTC+2, Christian Brabandt wrote:
> Yes as mentioned before, it might be unexpected, that the last output
> from a command or a plugin will be erased just by switching the tabpage.
>
> Or perhaps said differe
Yegappan wrote:
> The updated getcwd() function documentation is below. Let me know if
> you have any
> comments on this.
>
> - Yegappan
>
> getcwd([{winnr} [, {tabnr}]])
> The result is a String, which is the name of the current
> working directory.
>
>
Christian wrote:
> On Mi, 17 Apr 2019, zdoh...@redhat.com wrote:
>
> > 1)$ vim -u NONE -U NONE -N -i NONE -p a b
> > 2)now you can see ""b" [New File]" in vim command line - but you are
> > actually in file "a" (as you can see by :f or in upper tab)
> > 3) try to switch to "b" by 'gt' - previo
12 matches
Mail list logo
