Re: Choices for Vim9 class implementation
Hi Bram, Before everything becomes unchangeable, can I suggest to use "new ClassName" instead of "ClassName.new" to create an instance ? According to the description in vim9class.txt: > An object can only be created by a class. A class provides: > - A new() method, the constructor, which returns an object for the class. > This method is invoked on the class name: MyClass.new(). An object can be created by: var pos = TextPosition.new(1, 1) Is it possible to change it to: var pos = new TextPosition(1, 1) this makes me feel more nature/familiar. Since the vim9-class is built from scratch without any backward-compatible problems, why not choose some intuitive grammars ? 在2022年12月20日星期二 UTC+8 17:49:10 写道： > For what it's worth, I feel that the formal "var memberVariable : Type" > syntax for member is (while more verbose) more likely to stand out. The > `var` keyword is a signpost and so is likely to be syntax highlighted. > Simple `memberVariable : Type` doesn't stand out anywhere and contains > mostly identifiers without keywords. > > Additionally, I personally prefer the symmetry with local variables. If > all declarations look the same, then it's one less rule to remember. > > You can then also use const: `const memberVarConstant : Type` maybe? > > On Tuesday, December 20, 2022 at 12:30:50 AM UTC ch...@createng.com wrote: > >> >>> The difference between a regular method and a constructor is that for a >>> constructor it is very common to assign the argument to an object >>> member. >>> >>> The idea comes from Dart, and I don't think Dart supports this for >>> anything but constructors. >>> >> >> That's a good point, it is usually constructors where it get tedious. >> I really appreciate your considered replies. >> Thanks >> >> > -- -- 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 received this message because you are subscribed to the Google Groups "vim_dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to vim_dev+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/vim_dev/73c55b7d-7770-42b1-8049-0b969bf02ac1n%40googlegroups.com.
Re: Vim9 script feature-complete
fair enough, thanks. 在2021年12月31日星期五 UTC+8 19:35:37 写道： > > Wei Zhang wrote: > > > any chance to remove the space compulsory in vim9 ?? > > > > Vim9 script enforces proper use of white space. This is no longer > allowed: > > > > > var name=234 # Error! > > var name= 234 # Error! > > var name =234 # Error! > > There must be white space before and after the "=": > > > var name = 234 # OK > > This was an intentional choice. It may look a bit strict, but you will > eventually appreciate that scripts are easier to read. If the three > forms above would be allowed then you end up with a mix of them, making > scripts less uniform and taking a bit longer to spot the structure. > > -- > You're as much use as a condom machine at the Vatican. > -- Rimmer to Holly in Red Dwarf 'Queeg' > > /// Bram Moolenaar -- br...@moolenaar.net -- http://www.Moolenaar.net \\\ > /// \\\ > \\\ sponsor Vim, vote for features -- http://www.Vim.org/sponsor/ /// > \\\ help me help AIDS victims -- http://ICCF-Holland.org /// > -- -- 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 received this message because you are subscribed to the Google Groups "vim_dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to vim_dev+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/vim_dev/f1af1ac6-6ada-4974-9380-75fd44da52c2n%40googlegroups.com.
Re: Vim9 script feature-complete
any chance to remove the space compulsory in vim9 ?? Vim9 script enforces proper use of white space. This is no longer allowed: > var name=234# Error! var name= 234# Error! var name =234# Error! There must be white space before and after the "=": > var name = 234# OK 在2021年12月31日星期五 UTC+8 04:39:55 写道： > > [it appears this message did not reach the list, sending it again] > > The work on Vim9 script is coming to a point where the syntax and > semantics are practially done. There might be some more tests > uncovering problems that need to be fixed and perhaps some tiny tweaks, > but otherwise it has been quite stable for the past months. > > If you have remarks on something in Vim9 script that you think should be > different, speak up now! Soon we'll only make backwards compatible > changes to avoid breaking existing plugins. > > The information about Vim9 script and many of the choices made can be > found in a recent build with ":help vim9". Or see it online (without > concealing): https://github.com/vim/vim/blob/master/runtime/doc/vim9.txt > > In a few days I will add the "vim9script" feature, so that plugins can > check for Vim9 script being supported and rely on it working. From that > moment Vim9 script needs to be backwards compatible! > > This is not the end, I plan to add more features later. But these will > be backwards compatible. That is why some commands such as "class" and > "interface" have been reserved for future use. > > I will now work on including remarks about the Vim9 syntax throughout > the help text. > > -- > hundred-and-one symptoms of being an internet addict: > 115. You are late picking up your kid from school and try to explain > to the teacher you were stuck in Web traffic. > > /// Bram Moolenaar -- br...@moolenaar.net -- http://www.Moolenaar.net \\\ > /// \\\ > \\\ sponsor Vim, vote for features -- http://www.Vim.org/sponsor/ /// > \\\ help me help AIDS victims -- http://ICCF-Holland.org /// > -- -- 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 received this message because you are subscribed to the Google Groups "vim_dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to vim_dev+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/vim_dev/f882fa68-ce08-4e8b-a3d3-b9bc0b8db15bn%40googlegroups.com.
Re: Patch 8.2.0852
What purpose do you have to stop the terminal ??
If everything I remember is accurate, you are a neovim user and seldom use
vim.
Since neovim set IXON too, you can't stop the terminal in your everyday
work.
Why are you willing to stop terminal in vim ? for what ?
在 2020年6月1日星期一 UTC+8上午12:10:07，wsdjeg写道：
>
> Why Vim breaks this compatibility, with this patch I can not use Ctrl-s
> to stop the terminal!!
> --
> wsdjeg
> >
> >Patch 8.2.0852
> >Problem:Cannot map CTRL-S on some systems.
> >Solution: Do not use CTRL-S for flow control.
> >Files: src/os_unix.c
> >
> >
> >*** ../vim-8.2.0851/src/os_unix.c2020-05-30 18:14:37.828521058
> +0200
> >--- src/os_unix.c2020-05-30 20:00:41.856511541 +0200
> >***
> >*** 3482,3492
> > {
> > // ~ICRNL enables typing ^V^M
> > tnew.c_iflag &= ~ICRNL;
> >- # ifdef IXON_NOT_USED
> > // Do not make CTRL-S stop output, for most users it is unexpected and
> > // is hardly ever useful.
> > tnew.c_iflag |= IXON;
> >- # endif
> > tnew.c_lflag &= ~(ICANON | ECHO | ISIG | ECHOE
> > # if defined(IEXTEN) && !defined(__MINT__)
> > | IEXTEN// IEXTEN enables typing ^V on SOLARIS
> >--- 3482,3490
> >*** ../vim-8.2.0851/src/version.c2020-05-30 19:52:42.270340843
> +0200
> >--- src/version.c2020-05-30 19:58:42.416967148 +0200
> >***
> >*** 748,749
> >--- 748,751
> > { /* Add new patch number below this line */
> >+ /**/
> >+ 852,
> > /**/
> >
> >--
> >hundred-and-one symptoms of being an internet addict:
> >219. Your spouse has his or her lawyer deliver the divorce papers...
> > via e-mail.
> >
> > /// Bram Moolenaar -- b...@moolenaar.net -- http://www.Moolenaar.net \\\
> >/// sponsor Vim, vote for features -- http://www.Vim.org/sponsor/ \\\
> >\\\ an exciting new programming language -- http://www.Zimbu.org ///
> > \\\ help me help AIDS victims -- http://ICCF-Holland.org ///
> >
> >--
> >--
> >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 received this message because you are subscribed to the Google Groups
> "vim_dev" group.
> >To unsubscribe from this group and stop receiving emails from it, send an
> email to vim...@googlegroups.com .
> >To view this discussion on the web visit
> https://groups.google.com/d/msgid/vim_dev/202005301805.04UI5UQE420071%40masaka.moolenaar.net
> .
--
--
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 received this message because you are subscribed to the Google Groups
"vim_dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to vim_dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/vim_dev/b2c09f67-4d67-49ca-ac2e-2b114485a708%40googlegroups.com.
Vim 8.2 is released!
Thanks Bram，without your effort these amazing features may not be possible。 -- -- 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 received this message because you are subscribed to the Google Groups "vim_dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to vim_dev+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/vim_dev/3f01aad2-df8e-453d-94b6-4dff684477c7%40googlegroups.com.
So, how about Vim 9?
Only one request, can we just replace all the endif endwhile endfor endfunction with a single end statement? -- -- 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 received this message because you are subscribed to the Google Groups "vim_dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to vim_dev+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/vim_dev/1255b02b-726b-4d0f-a959-0d70ef24ef07%40googlegroups.com.
Why does the text property development suspended
No update for 4 month, do we have any difficulty that can't be overcame ? Does it need a big refactor ?? Anything the community can help ?? -- -- 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 received this message because you are subscribed to the Google Groups "vim_dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to vim_dev+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: Patch 8.0.1850
在 2018年5月17日星期四 UTC+8下午7:21:10，Bram Moolenaar写道： > Patch 8.0.1850 > Problem:Todo items in source code not visible for users. > Solution: Move the todo items to the help file. > Files: src/terminal.c Has 8.0.1850 been tagged as 8.1 ?? :version VIM - Vi IMproved 8.1 (2018 May 17, compiled May 17 2018 23:10:54) Compiled by skywind@airvm1 -- -- 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 received this message because you are subscribed to the Google Groups "vim_dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to vim_dev+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: Patch 8.0.1570
> Executing menu command **BEFORE** ":popup" exiting is important because > following commands can get the result of selected item. if not, every > following command in the same function behave in the wrong way. Once, I was trying to call ":popup" in an imap .. function because I need a popup menu in insert mode which contains some items like: - Insert - Insert - Insert block - - - Insert Emoji - Insert Emoji . Each menu item will just set a global variable to a given number, and commands after ":popup" will know what item has been selected and do some complex work. This will help me a lot without leaving insert mode. But it is impossible to get the result after ":popup" . So, I have no idea about what to return in my imap function. Most vim users are using UltiSnip, to many snip keywords to be remember and they are easy to be forgotten. UltiSnip uses inputlist() to enable user choose snippets if they have no idea about what snippets they can input. But selecting snippets in insert mode with inputlist() is awful, A popup window in insert mode can emulate inputlist() and let user choose the most often used snippets. More friendly to inputlist(), but it is impossible to do such thing in GVim, because the following command can't get the result of ":popup" command. -- Popup menus are friendly to new users, an enhanced popup menu is also very helpful to men with bad memory like me. I always forget some keymaps if I don't use them for two weeks. Every time I read "index.txt" I can learn something new and very helpful, then I want put them in a popup menu and when I share my .vimrc to someone who haven't read this they can use this menu to discover what they can do immediately. Do you think the these cases above can be a good reason to enhance popup menu and replace GVim's ":popup" with terminal vim's ":popup" ? or to have an new guioption to disable native Win32 popup window ?? -- -- 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 received this message because you are subscribed to the Google Groups "vim_dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to vim_dev+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: Patch 8.0.1570
> > And on last thing, special character '&' can not be used in the TUI popup, > > Yeah, it's hard to find a way to highlight it. And then how do you type > the character? Mappings may get in the way. Alt key may not always > work. > It is not necessary to highlight special character, they can be distinguished by parentheses. :amenu PopUp.Cscope\ ()efinition ... :amenu PopUp.Cscope\ ()ymbol ... :amenu PopUp.Cscope\ ()allee ... :amenu PopUp.Cscope\ ()ssigned ... They should look like: Cscope (D)efinition Cscope (S)ymbol Cscope (C)allee Cscope (A)ssigned or items can also be arranged by user like: [D] Cscope Definition [S] Cscope Symbol [C] Cscope Callee [A] Cscope Assigned Both of them are quite acceptable, just like some traditional mono color TUI tools . So, highlighting is not necessary if it requires a lot of work. What might be necessary is making GVim's ':popup' command display the TUI's text based popup menu instead of the native win32's popup menu (or a guioption for this ?). Can I explain this a little ? 1. GUI popup is only available for Win32 and GTK, but text based popup can run every where. 2. Part of vim users use CTRL+[ as ESC, text based popup can be closed by CTRL+[ while native GUI popup can't. 3. Native GUI ":popup" command sometimes behave in a strange way (also mentioned in gui.txt) and different from TUI's popup menu. Here is an example: --- menutest.vim silent! aunmenu ]test.* let g:selected_index=-1 amenu ]test.item\ 1 :let g:selected_index=1 amenu ]test.item\ 2 :let g:selected_index=2 amenu ]test.item\ 3 :let g:selected_index=3 amenu ]test.item\ 4 :let g:selected_index=4 amenu ]test.item\ 5 :let g:selected_index=5 amenu ]test.item\ 6 :let g:selected_index=6 function! MenuInputList() let g:selected_index=-1 popup ]test echo "selected: ".g:selected_index return g:selected_index endfunc - When MenuInputList() happens in TUI vim, you can see `g:selected_index` has been changed after ":popup" command, it is definitely the right way. But it is a different result in GVim, no matter what item is selected, the echo command below will always print "selected: -1". After my investigation, ":popup" command returns before actually executing the real menu command "let g:selected_index=?". It seems that the real menu command has been queued in win32 message buffer and will not be execute before ':popup' exits. So, the echo command displays the unchanged g:selected_index in GVim. But when I was trying the TUI's ":popup" command in the latest vim, it worked great !! menu command (let g:selected_index=?) can be executed **BEFORE** ":popup" command returns. Executing menu command **BEFORE** ":popup" exiting is important because following commands can get the result of selected item. if not, every following command in the same function behave in the wrong way. So, do you think it is necessary to execute menu command before ":popup" returning ? or to replace GVim's ":popup" menu with the TUI's text based one ? -- -- 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 received this message because you are subscribed to the Google Groups "vim_dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to vim_dev+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: Patch 8.0.1570
Thanks a lot, I always can't remember my keymaps and need to check the vimrc
again and again when I forget some. popup windows will help me and other
newbees.
An issue has been found during my test:
When you are navigating the items in the popup with arrow keys, you can see the
cursor is visible and locate just behind the current selected item.
I suppose cursor should be invisible when popup window is in-use ??
And on last thing, special character '&' can not be used in the TUI popup,
:amenu PopUp.Cscope\ :cs find g =expand("")
:amenu PopUp.Cscope\ :cs find s =expand("")
:amenu PopUp.Cscope\ :cs find c =expand("")
:amenu PopUp.Cscope\ :cs find a =expand("")
I always forget cscope commands, so, it's necessary for me to put them into a
popup menu and give each item a shortcut by using '&'.
This shortcuts can be used on gvim but it doesn't work in TUI now.
在 2018年3月6日星期二 UTC+8上午4:07:01，Bram Moolenaar写道：
> Patch 8.0.1570
> Problem:Can't use :popup for a menu in the terminal. (Wei Zhang)
> Solution: Make :popup work in the terminal. Also fix that entries were
> included that don't work in the current state.
> Files: src/ex_docmd.c, src/popupmnu.c, src/proto/popupmnu.pro,
> src/menu.c, src/proto/menu.pro
>
>
> *** ../vim-8.0.1569/src/ex_docmd.c2018-03-04 20:14:08.244064367 +0100
> --- src/ex_docmd.c2018-03-05 20:33:27.651337765 +0100
> ***
> *** 204,210
> #else
> # define ex_tearoff ex_ni
> #endif
> ! #if (defined(FEAT_GUI_MSWIN) || defined(FEAT_GUI_GTK)) && defined(FEAT_MENU)
> static void ex_popup(exarg_T *eap);
> #else
> # define ex_popup ex_ni
> --- 204,211
> #else
> # define ex_tearoff ex_ni
> #endif
> ! #if (defined(FEAT_GUI_MSWIN) || defined(FEAT_GUI_GTK) \
> ! || defined(FEAT_TERM_POPUP_MENU)) && defined(FEAT_MENU)
> static void ex_popup(exarg_T *eap);
> #else
> # define ex_popup ex_ni
> ***
> *** 8741,8751
> }
> #endif
>
> ! #if (defined(FEAT_GUI_MSWIN) || defined(FEAT_GUI_GTK)) && defined(FEAT_MENU)
> static void
> ex_popup(exarg_T *eap)
> {
> ! gui_make_popup(eap->arg, eap->forceit);
> }
> #endif
>
> --- 8742,8762
> }
> #endif
>
> ! #if (defined(FEAT_GUI_MSWIN) || defined(FEAT_GUI_GTK) \
> ! || defined(FEAT_TERM_POPUP_MENU)) && defined(FEAT_MENU)
> static void
> ex_popup(exarg_T *eap)
> {
> ! # if defined(FEAT_GUI_MSWIN) || defined(FEAT_GUI_GTK)
> ! if (gui.in_use)
> ! gui_make_popup(eap->arg, eap->forceit);
> ! # ifdef FEAT_TERM_POPUP_MENU
> ! else
> ! # endif
> ! # endif
> ! # ifdef FEAT_TERM_POPUP_MENU
> ! pum_make_popup(eap->arg, eap->forceit);
> ! # endif
> }
> #endif
>
> *** ../vim-8.0.1569/src/popupmnu.c2018-03-03 18:59:11.612531627 +0100
> --- src/popupmnu.c2018-03-05 21:01:01.461275616 +0100
> ***
> *** 1132,1143
> #ifdef FEAT_BEVAL_TERM
> int save_bevalterm = p_bevalterm;
> #endif
>
> pum_undisplay();
> pum_size = 0;
>
> for (mp = menu->children; mp != NULL; mp = mp->next)
> ! ++pum_size;
>
> array = (pumitem_T *)alloc_clear((unsigned)sizeof(pumitem_T) *
> pum_size);
> if (array == NULL)
> --- 1132,1147
> #ifdef FEAT_BEVAL_TERM
> int save_bevalterm = p_bevalterm;
> #endif
> + int mode;
>
> pum_undisplay();
> pum_size = 0;
> + mode = get_menu_mode_flag();
>
> for (mp = menu->children; mp != NULL; mp = mp->next)
> ! if (menu_is_separator(mp->dname)
> ! || (mp->modes & mp->enabled & mode))
> ! ++pum_size;
>
> array = (pumitem_T *)alloc_clear((unsigned)sizeof(pumitem_T) *
> pum_size);
> if (array == NULL)
> ***
> *** 1146,1152
> for (mp = menu->children; mp != NULL; mp = mp->next)
> if (menu_is_separator(mp->dname))
> array[idx++].pum_text = (char_u *)"";
> ! else
> array[idx++].pum_text = mp->dname;
>
> pum_array = array;
> --- 1150,1156
> for (mp = menu->children; mp != NULL; mp = mp->next)
> if (menu_is_separator(mp->dname))
> array[idx++].pum_text = (char_u *)"";
> ! else if (mp->modes & mp->enabled & mode)
> array[idx++].pum_text = mp->dname;
>
> pum_array = array;
> ***
> *** 1232,1237
> --
Re: Patch 8.0.1558
Thanks, great, I can use it with mouse now. And one last wish, can I popup it in TUI via ':popup ...' command in vimscript ? Or something like `:call inputlist()` but use popup menu to select item. 在 2018年3月5日星期一 UTC+8下午5:56:07，Bram Moolenaar写道： > Wei Zhang wrote: > > > Seems cool, but how to use this right-click popup menu ? > > > > have tried: > > > > 1. click right mouse botton on text: it switched to visual mode > > 2. shift+left/right botton: no use > > 3. execute ":popup PopUp" : Sorry, the command is not available in this > > version > > > > It doesn't have any documentation yet. > > The popup menu has existed in the GUI for a very long time. > To use it in a terminal: > :set mousemodel=popup > or > :set mousemodel=popup_setpos > > For MS-Windows the default already is "popup" and I checked it works in > a console. Unfortunately it doesn't have mouse move events. Not sure > if that is a problem of the console or of Vim... Ah, we drop move > events in decode_mouse_event(). Should keep them when p_bevalterm is > set. > > -- > I used to wonder about the meaning of life. But I looked it > up in the dictionary under "L" and there it was - the meaning > of life. It was less than I expected. - Dogbert > > /// Bram Moolenaar -- b...@moolenaar.net -- http://www.Moolenaar.net \\\ > ///sponsor Vim, vote for features -- http://www.Vim.org/sponsor/ \\\ > \\\ an exciting new programming language -- http://www.Zimbu.org/// > \\\help me help AIDS victims -- http://ICCF-Holland.org/// -- -- 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 received this message because you are subscribed to the Google Groups "vim_dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to vim_dev+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: Patch 8.0.1558
Can we use it by ":popup PopUp" or ":popup ]something" in the future ? If so, we can use it as an alternative to "inputlist()" and it will provide better user experience than "inputlist()" in TUI. 在 2018年3月5日星期一 UTC+8下午12:02:17，Wei Zhang写道： > Seems cool, but how to use this right-click popup menu ? > > have tried: > > 1. click right mouse botton on text: it switched to visual mode > 2. shift+left/right botton: no use > 3. execute ":popup PopUp" : Sorry, the command is not available in this > version > > It doesn't have any documentation yet. -- -- 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 received this message because you are subscribed to the Google Groups "vim_dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to vim_dev+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: Patch 8.0.1558
Seems cool, but how to use this right-click popup menu ? have tried: 1. click right mouse botton on text: it switched to visual mode 2. shift+left/right botton: no use 3. execute ":popup PopUp" : Sorry, the command is not available in this version It doesn't have any documentation yet. -- -- 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 received this message because you are subscribed to the Google Groups "vim_dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to vim_dev+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: RFC: Signature help/argument hints in a second popup menu
I really like this feature. -- -- 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 received this message because you are subscribed to the Google Groups "vim_dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to vim_dev+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Is Bram OK ??
-- -- 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 received this message because you are subscribed to the Google Groups "vim_dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to vim_dev+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [vim/vim] netrw 162m closes and deletes current window/buffer when opening directory (#2141)
As long as Dr. Chip works on a Windows pc for a week, he will find netrw is totally crap on Windows. 在 2017年12月15日星期五 UTC+8上午11:31:48，K.Takata写道： > Hi Dr. Chip, > > There are more than 20 issues related to netrw in this repository. > > You can easily find them by searching the plugin-netrw label: > > https://github.com/vim/vim/labels/plugin-netrw > > Please also care about these issues. > > Thanks. > > > — > You are receiving this because you are subscribed to this thread. > Reply to this email directly, view it on GitHub -- -- 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 received this message because you are subscribed to the Google Groups "vim_dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to vim_dev+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
