2016-04-25 20:49 GMT+03:00 Davit Samvelyan <[email protected]>: >> Which is by no means going to “end patched fonts madness”. This is >> what I call “useless”: > Well lets say I want to add icons to the completion popup menu which > indicates item type (function, class, member, ...). I should pick up a > character range not used by any of the existing patch font plugins to avoid > conflicts, patch most widely used fonts with the new characters to make > plugin appealing to the user. > And what if someone uses https://github.com/ryanoasis/vim-devicons this > plugin and wants to add mine. > Lets create a patched fonts with all possible plugins which need custom > glyphs for all common fonts. And require user to patch its font by himself if > its isn't in that list. Madness!!!
I did not say this current solution is good. I said that your solution is no solution for many users. > >> many if not most users are using Vim from terminal, also there are many >> powerline users that use it for tmux or their shell. > Where did you get that statistics from? In our company almost everyone uses > gvim. I personally use terminal vim only when ssh-ed into remote machine. I have no statistics. Just I am watching IRC and mailing list and terminal users are very common here. > > >> It is easier to continue requiring patched fonts then >> learn new technology just for a portion (special fonts can be >> disabled, AFAIR airline even disables them by default) of a portion >> (GUI and no powerline in shell/etc: if there is powerline in shell >> then patched fonts are still needed) of a portion (not all users can >> have most recent Vim) users. > Of course its easier for existing plugins stay the way they are, but easier > doesn't mean better. > I am talking about out of box experience for users, who will eventually will > get the latest version. > And why possible cool functionalities of the GUI vim should be sacrificed to > the limitations of the terminal ? Adding XPM icons will not make patched fonts go away, so this will not solve that madness. I did not say they should, just said that it is not a solution and thus most likely will not be widely adopted: nobody wants to maintain one code for terminal users and another for GUI users, especially when not-so-good terminal variant works. (Depends on how easy the API will be though.) > > For example why there is still no completion popup like this in gvim: > http://docs.telerik.com/devtools/aspnet-ajax/general-information/integration-with-visual-studio/typescript-definitions/images/typescript-intellisense-declared-variable-event-handler.png > > -- > -- > 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 [email protected]. > For more options, visit https://groups.google.com/d/optout. -- -- 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 [email protected]. For more options, visit https://groups.google.com/d/optout.
