|
| 1 | +--- |
| 2 | +title: PDE |
| 3 | +author: TJ DeVries (twitch.tv/teej_dv) |
| 4 | +date: 2022-02-10 |
| 5 | +--- |
| 6 | + |
| 7 | +- TODO: Consider re-recording as a ted talk |
| 8 | + |
| 9 | +# PDE |
| 10 | + |
| 11 | +# Intro |
| 12 | + |
| 13 | +- Who am I? |
| 14 | + - [tjdevries](https://github.com/tjdevries) |
| 15 | + - Neovim core member |
| 16 | + - Telescope.nvim author |
| 17 | +- [Twitch](twitch.tv/teej_dv): `teej_dv` |
| 18 | +- [YouTube](youtube.com/c/TjDeVries): `TjDeVries` |
| 19 | + |
| 20 | + |
| 21 | +# PDE? |
| 22 | + |
| 23 | +Personalized Development Environment |
| 24 | + |
| 25 | +# PDE |
| 26 | + |
| 27 | +> Text Editor <-> IDE |
| 28 | +
|
| 29 | +- The above seems like too limited of a spectrum. |
| 30 | +- It seems to confuse people (especially those who have never tried something like neovim) as to what the purpose would be of using them. |
| 31 | + |
| 32 | +# PDE |
| 33 | + |
| 34 | +> Text Editor <-> PDE <-> IDE |
| 35 | +
|
| 36 | +Something in between Text Editor and IDE I think could be useful to add to our vocabulary |
| 37 | + |
| 38 | +# PDE |
| 39 | + |
| 40 | +## Requirements |
| 41 | + |
| 42 | +> Some assembly required |
| 43 | +
|
| 44 | +# PDE |
| 45 | + |
| 46 | +## Requirements |
| 47 | + |
| 48 | +- Coding "basics": |
| 49 | + - Syntax highlighting |
| 50 | + - Folding |
| 51 | + - (basically just not Notepad...) |
| 52 | + |
| 53 | +# PDE |
| 54 | + |
| 55 | +## Requirements |
| 56 | + |
| 57 | +- Coding "basics": |
| 58 | + - Syntax highlighting |
| 59 | + - Folding |
| 60 | + - (basically just not Notepad...) |
| 61 | +- Code Intelligence |
| 62 | + - For example: LSP |
| 63 | + - (Can be builtin or plugin) |
| 64 | + |
| 65 | +# PDE |
| 66 | + |
| 67 | +## Requirements |
| 68 | + |
| 69 | +- Coding "basics": |
| 70 | + - Syntax highlighting |
| 71 | + - Folding |
| 72 | + - (basically just not Notepad...) |
| 73 | +- Code Intelligence |
| 74 | + - For example: LSP |
| 75 | + - (Can be builtin or plugin) |
| 76 | +- PDE provides: |
| 77 | + - Composition of tools |
| 78 | + - Scriptable & Extensible |
| 79 | + |
| 80 | +# PDE |
| 81 | + |
| 82 | +## Requirements |
| 83 | + |
| 84 | +- YOU ARE HAVING FUN! |
| 85 | + |
| 86 | +_side rant about "faster" as an argument for a tool_ |
| 87 | + |
| 88 | + |
| 89 | +# Neovim as PDE |
| 90 | + |
| 91 | +It can do syntax highlighting, folding, movements, editing files, etc. |
| 92 | + |
| 93 | +I don't think that's really contested by anyone, not even the `ackshually` crowd. |
| 94 | + |
| 95 | +# Neovim as PDE |
| 96 | + |
| 97 | +- API |
| 98 | + - Exposes robust api (`:help api`) |
| 99 | + |
| 100 | +```lua |
| 101 | +vim.api.nvim_buf_set_lines(0, 0, -1, false, { |
| 102 | + "First Line", |
| 103 | + "Second Line" |
| 104 | +}) |
| 105 | +``` |
| 106 | + |
| 107 | +# Neovim as PDE |
| 108 | + |
| 109 | +- Lua-ify Everything |
| 110 | + - Settings |
| 111 | + - Keymaps |
| 112 | + - Commands |
| 113 | + - Autocmds (soon) |
| 114 | + - etc. |
| 115 | + |
| 116 | +Scripting is configuration. Configuration is scripting. |
| 117 | + |
| 118 | +# Neovim as PDE |
| 119 | + |
| 120 | +- Treesitter |
| 121 | + - Syntax highlighting |
| 122 | + - But so much more than syntax highlighting! |
| 123 | + |
| 124 | +# Neovim as PDE |
| 125 | + |
| 126 | +- Builtin LSP |
| 127 | + |
| 128 | +# Neovim as PDE |
| 129 | + |
| 130 | +- nvim-dap |
| 131 | +- vimspector |
0 commit comments