On Thursday, May 30, 2019 at 9:19:39 PM UTC+1, toothpik wrote:
> i just git pulled 1430 and it fails to build:
>
> evalfunc.c:816:33: error: ‘f_popup_getposition’ undeclared here (not
> in a function)
> {"popup_getposition", 1, 1, f_popup_getposition},
> ^
>
Hi Bram,
2019/5/28 Tue 5:22:09 UTC+9 Bram Moolenaar wrote:
> Ken Takata wrote:
>
> > I found many typos and mistakes in version8.txt.
> > Please check the attached patch.
>
> I'll include it, thanks!
I found some more missing contributor names. Also found a mistake in my
previous patch.
Patch 8.1.1432 (after 8.1.1429)
Problem:Can't build with eval feature.
Solution: Add missing rename.
Files: src/evalfunc.c
*** ../vim-8.1.1431/src/evalfunc.c 2019-05-30 19:24:57.615269014 +0200
--- src/evalfunc.c 2019-05-30 21:18:00.775192562 +0200
***
***
Patch 8.1.1431
Problem:Popup window listed as "Scratch".
Solution: List them as "Popup".
Files: src/buffer.c, src/popupwin.c, src/testdir/test_popupwin.vim,
runtime/doc/popup.txt, runtime/doc/windows.txt
*** ../vim-8.1.1430/src/buffer.c2019-05-28
i just git pulled 1430 and it fails to build:
evalfunc.c:816:33: error: ‘f_popup_getposition’ undeclared here (not
in a function)
{"popup_getposition", 1, 1, f_popup_getposition},
^
Makefile:3005: recipe for target 'objects/evalfunc.o' failed
make[1]: ***
Patch 8.1.1429
Problem:"pos" option of popup window not supported yet.
Solution: Implement the option. Rename popup_getposition() to
popup_getpos().
Files: src/structs.h, src/popupwin.c, src/proto/popupwin.pro,
runtime/doc/popup.txt
***
Patch 8.1.1430
Problem:Popup window option "wrap" not supported.
Solution: Implement it.
Files: src/popupwin.c, src/testdir/test_popupwin.vim,
src/testdir/dumps/Test_popupwin_wrap.dump,
src/testdir/dumps/Test_popupwin_nowrap.dump
***
Dominique wrote:
> Please find attached the Esperanto translation
> (src/po/eo.po) updated with vim-8.1.1426.
I'll include it, thanks.
--
Keyboard not found. Think ENTER to continue.
/// Bram Moolenaar -- b...@moolenaar.net -- http://www.Moolenaar.net \\\
///sponsor Vim, vote
You probably need the nested keyword for your autocommand
> Am 30.05.2019 um 07:24 schrieb Edward Peschko :
>
> All,
>
> I'm hitting an odd bug when I define an event which involves splitting a
> window. I've isolated it down to the following example:
>
> autocmd CursorMoved * :execute
Patch 8.1.1424
Problem:Crash when popup menu is deleted while waiting for char.
Solution: Bail out when pum_array was cleared.
Files: src/popupmnu.c
*** ../vim-8.1.1423/src/popupmnu.c 2019-05-28 23:08:12.072648675 +0200
--- src/popupmnu.c 2019-05-30 15:51:54.799280366
Ken Takata wrote:
> Recently Vim supported binary numbers, but it was not written in usr_41.txt.
> Please check the attached patch.
I'll include it, thanks!
--
Never go to the toilet in a paperless office.
/// Bram Moolenaar -- b...@moolenaar.net -- http://www.Moolenaar.net \\\
///
Patch 8.1.1423
Problem:Popup windows use options from current window and buffer.
Solution: Clear all local options when creating a popup window.
Files: src/popupwin.c, src/option.c, src/proto/option.pro,
src/testdir/test_popupwin.vim
*** ../vim-8.1.1422/src/popupwin.c
Hi,
Recently Vim supported binary numbers, but it was not written in usr_41.txt.
Please check the attached patch.
Regards,
Ken Takata
--
--
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
Patch 8.1.1422
Problem:Popup_getoptions() not implemented yet.
Solution: Implement it. (closes #4452)
Files: runtime/doc/popup.txt, src/evalfunc.c, src/popupwin.c,
src/proto/popupwin.pro, src/testdir/test_popupwin.vim
*** ../vim-8.1.1421/runtime/doc/popup.txt
Patch 8.1.1426
Problem:No test for syntax highlight in popup window.
Solution: Add a screenshot test. Update associated documentation. Avoid
'buftype' being reset by setbufvar().
Files: runtime/doc/eval.txt, src/testdir/test_popupwin.vim,
On Wednesday, May 29, 2019 at 11:33:35 PM UTC-7, Christian Brabandt wrote:
> You probably need the nested keyword for your autocommand
>
Christian -
I don't see any documentation on that keyword inside of vim. Not seeing much on
the internet either.
Can you give an example and why it is
Patch 8.1.1425
Problem:Win_execute() does not set window pointers properly.
Solution: Use switch_win_noblock(). Also execute autocommands in a popup
window.
Files: src/window.c, src/proto/window.pro, src/evalfunc.c, src/autocmd.c
*** ../vim-8.1.1424/src/window.c
On 2019-05-30, Edward Peschko wrote:
> On Wednesday, May 29, 2019 at 11:33:35 PM UTC-7, Christian Brabandt wrote:
> > You probably need the nested keyword for your autocommand
> >
> Christian -
>
> I don't see any documentation on that keyword inside of vim. Not
> seeing much on the internet
Patch 8.1.1428
Problem:Popup_atcursor() not implemented yet.
Solution: Implement it. (Yasuhiro Matsumoto, closes #4456)
Files: runtime/doc/popup.txt, src/evalfunc.c, src/popupwin.c,
src/proto/popupwin.pro, src/testdir/test_popupwin.vim
***
On 2019-05-30, Paul Jolly wrote:
> So I'd like to explore a pattern by which the end user calls a config
> function from their .vimrc or whenever they want to change a config
> value. This will have the benefit of pushing the config value to the
> channel-based plugin, but also allowing tighter
On Do, 30 Mai 2019, Edward Peschko wrote:
> thanks Gary, I found it by doing grep -r of the vim source directory. Your
> methods are much cleaner though...
Sorry, I wasn't in front of my desktop PC when I wrote the answer, so
couldn't point to the right vim documentation. In addition, the
On 5/30/19 1:06 PM, Paul Jolly wrote:
Hi all,
As a follow up to a recent thread ("Plugins exposing events to other
plugins":
https://groups.google.com/d/msg/vim_dev/uiw6gHft-0g/i8qdfT8YBQAJ)
I'd like to ask whether there is an existing pattern of configuration
functions that plugin
Patch 8.1.1427 (after 8.1.1426)
Problem:Popup window screenshot test fails.
Solution: Add missing change to popup window code.
Files: src/popupwin.c
*** ../vim-8.1.1426/src/popupwin.c 2019-05-30 15:22:39.836174965 +0200
--- src/popupwin.c 2019-05-30 18:37:05.505469701
Hi all,
As a follow up to a recent thread ("Plugins exposing events to other
plugins": https://groups.google.com/d/msg/vim_dev/uiw6gHft-0g/i8qdfT8YBQAJ)
I'd like to ask whether there is an existing pattern of configuration
functions that plugin developers follow?
Some background.
I'm not
> :help autocmd-nested
>
> You can find this by typing
>
> :help nested
>
> and hitting Ctrl-D to list help entries containing "nested". See
> just
>
> :help
>
> You can also use :helpgrep to search the documentation for words or
> patterns. For example,
>
> :helpgrep
25 matches
Mail list logo