Download as PDF, PPTX
Uploaded byShougo
Vim conf2019
The document outlines the development history of 'dark plugins' for Vim, detailing a progression from zero generation to fourth generation plugins over a span of ten years. It discusses the transition from Vim script to Python3 for improved performance and customization, as well as specific features and examples of each plugin generation. The author emphasizes the importance of customizability, plugin combination, and asynchronous capabilities in plugin development.
More Related Content
Vim conf2019
- 1. My dark pluginsdevelopment history ~ over 10 years ~ Shougo
- 2. 2 "My presentation may bethe last. So I need to speak the development history." Note
- 3. 3 Profile ● Shougo= 暗黒美無王 ● “Dark VimMaster” (pronounciation: Uncock Vim Awe) ● Text editor is the world =
- 4. 4 VimConf 2019’s theme ● “Howto be more productive with Vim?”
- 5. 5 “more productive withVim” is ... ● To develop dark plugins is my productive method!
- 6. 6 My theme is... ● My dark plugins development history over 10 years ● “Why does Shougo discard Vim script and choose Python3 instead?”
- 7. 7 What is “darkplugins”?(1) ● I want to do everything in Vim(neovim) like Emacs ● It is not allowed by “:help design- not” in Vim
- 8. 8 What is “darkplugins”?(2) ● It is not the light way to use Vim ● I have defined it as the dark way My plugins are dark powered!
- 9.
- 10. 10 Why did Iuse the plugins? ● I used IDEs in Windows ● I wanted to use IDE features
- 11. 11 Why did Iquit to use zero generation plugins? ● The plugins are not customizable fully ● Does not exist plugins for me ● I can create the plugins!
- 12. 12 1st generation plugins ● vimshell.vim (2009) ● neocomplcache.vim(2009) ● neosnippet.vim (2012)
- 13.
- 14.
- 15.
- 16.
- 17. 17 2nd generation plugins ● unite.vim (2010) ● vimfiler.vim(2010) ● neobundle.vim (2011) ● neocomplete.vim (2013)
- 18.
- 19. 19 I choosed if_luabecause... Vim script is too Slow!!!
- 20. 20 Plugins combination examples ● Unite.vim+ vimfiler.vim ● Neocomplete.vim + neosnippet.vim ● Unite.vim + neobundle.vim
- 21. 21 3rd generation plugins ● deoplete.nvim (2015) ● denite.nvim(2016) ● deol.nvim (2016) ● dein.vim (2015)
- 22. 22 3rd generation features ● Use Vim8/neovimfeatures ● Use Python3 instead ● Asynchronous
- 23. 23 Use Vim8/neovim features ● :terminal ● JobAPIs ● Remote plugins ● winid ● And more… ● No more Vim 7!
- 24. 24 I have chosenPython3 because... Vim script is too Slow!!!
- 25. 25 Python3 vs if_lua 90%10% if_lua Python3
- 26.
- 27. 27 4th generation plugins ● deoplete.nvim (2019,ver. 5.1~) ● denite.nvim (2019, ver. 3.0~) ● deoppet.nvim (2017) ● defx.nvim (2018)
- 28. 28 4th generation features ● Type definitions ● Nondefault key-mappings ● Remove configuration variables mappings variables
- 29. 29 Why is typedefinition important? ● It can detect some bugs ● Detect bugs is important
- 30. 30 Why non defaultkey-mappings?(1) https://github.com/Shougo/ defx.nvim/issues/5
- 31. 31 Why non defaultkey-mappings?(2) ● No best default key mappings ● Hard to define defaults ● Conflict with other plugins/config Default mappings are not needed!
- 32. 32 Why I haveremoved configuration variables? ● Functions can keep interfaces in multiple plugins ● Example: call defx#custom#option('_', {}) call denite#custom#option('_', {})
- 33. 33 Let’s create yourplugins! ● This is just my history. ● You can choose other selection!
- 34. 34 Your Vim isyour text editor!
- 35. The extra: denite.nvimversion 3 Shougo
- 36. 36 Denite.nvim big changes ● Manyissues are reported after upgrade
- 37. 37 Denite.nvim version 2 ● Stealyour input ● Define original mappings ● Similar to ctrlp.vim
- 38.
- 39. 39 Prompt UI’s disadvantages ● Ignoreuser’s configuration ● Hard to work asynchronously ● Cannot combine with other plugins ● They fit with my policy???
- 40. 40 My plugin developmentpolicy ● Customizable ● Combine with other plugins ● Asynchronous if possible
- 41. 41 Denite.nvim version 3 ● Replaceprompt.nvim to normal buffer ● Edit buffer instead of command line
- 42. 42 Denite.nvim version 3 Normalbuffer Edit buffer
- 43. 43 New UI advantages ● Useuser’s configuration ● Easy to work asynchronously ● Can combine with other plugins ● The features fit with my policy!
- 44.
- 45. The extra2: Mydevelopment note Shougo
- 46.
- 47. 47 I don’t usememo plugins! ● Memolist.vim ● QfixHowm ● Vimwiki ● …
- 48. 48 I use papernote for development ● Here
- 49. 49 I use thepaper note for... ● (Finished)task list ● Technology notes ● Survey for issues
- 50. 50 Why do Iuse paper note? ● Not needed PC! ● Free style
- 51. 51 The note isthe strongest Vim for me! ● Thank you!
- 52.