text stringlengths 0 2.02k |
|---|
• He initially found it difficult to use Lua but eventually converted his config to Lua and saw benefits |
• The benefits include reduced lines of code and increased power |
• TJ mentions that NeoVim is still missing some features to make configuration in Lua fully elegant |
• Some parts of the config, like auto commands, still require VimScript |
• TJ suggests that switching to init.lua is not necessary, but rather extending specific parts of the config with Lua is more beneficial |
• Lua has advantages in ergonomics, such as using closures and passing functions around easily. |
• Comparison of VimScript and Lua configuration options |
• Advantages of using Lua in Vim configuration, including auto commands and object-oriented programming |
• Challenges of translating VimScript to Lua and vice versa |
• Project to transpile VimScript to Lua and maintain semantic consistency |
• Potential for NeoVim to gain popularity over Vim due to its Lua support and plugins like Limelight |
• Goal of keeping Vim and NeoVim "friendly" and compatible |
• Discussion about the limitations of integrating TreeSitter into some editors |
• Mention of NeoVim-only plugins and the potential for plugins to be exclusive to Vim or NeoVim |
• Emphasis on the NeoVim team's goal of coexisting with the Vim community, not trying to replace it |
• Discussion about the history and evolution of Vim and NeoVim, with a nod to Bram's contributions |
• Lighthearted jokes about the "hostile takeover" and "long con" aspects of some open-source projects |
• Shift to discussing the Square platform and opportunity for developers to build apps for sellers |
• Introduction of Shannon Skipper, head of developer relations at Square, to discuss the opportunity for developers on the Square platform |
• Development on the Square platform's seller trust |
• Release of NeoVim 0.5 and its features |
• History of Language Server Protocol (LSP) development in NeoVim |
• Benefits and goals of LSP, including reducing M times N problems |
• Explanation of how LSP works, including communication between editors and servers |
• Comparison of VS Code and Vim development experiences, including use of LSP |
• Origins and design of LSP by Microsoft |
• LSP (Language Server Protocol) allows for communication between editor and language tools in a standardized way |
• LSP can be used to customize editor functionality, such as going to definition |
• LSP can be implemented in various ways, including as an external program or as a built-in binary |
• Communication with LSP is typically done over standard input/output or TCP, with JSON used for request and response formatting |
• NeoVim can spin up an LSP process and communicate with it through standard input/output |
• LSP can be used to implement editor functionality in a modular and customizable way |
• Example of using LSP to implement a custom "go to implementation" feature in NeoVim |
• Discussion of how LSP can be used to create a standardized interface for language tool makers and editor tool makers to interact with each other |
• LSP (Language Server Protocol) and its interaction with NeoVim |
• Installing and configuring LSP servers for NeoVim |
• Difference between LSP and TreeSitter |
• TreeSitter's role in handling syntax trees and error recovery |
• Comparison of LSP's project-wide scope vs TreeSitter's file-by-file scope |
• TreeSitter is incremental, only parsing the necessary parts of a file, not re-parsing the entire file. |
• TreeSitter generates a tree structure of the file, allowing for named nodes and ranges. |
• This allows for better and more powerful syntax highlighting, especially for complicated file types. |
• TreeSitter is a separate library that can be embedded in other editors, and is designed to be fast and performant. |
• To use TreeSitter in NeoVim, a separate plugin is not required, but can be used to simplify configuration. |
• However, an extra step is required to generate bindings, which can be done manually but is considered complicated. |
• The conversation is about NeoVim and the TreeSitter plugin |
• The speaker mentions that TreeSitter grammars should be included in NeoVim core for languages like C, Lua, and VimScript |
• The plugin "nvimtscommentstring" is discussed, which automatically updates the comment string option based on the language detected by TreeSitter |
• The plugin can handle languages embedded within each other, such as JavaScript and HTML, and can comment out code correctly in these cases |
• Another example is given of using TreeSitter to highlight C code within Lua files |
• A snippets plugin called Lua Snips is mentioned, which allows running Lua code to generate text as snippets are expanded |
• The speaker wrote a Lua snippet that uses TreeSitter to query the return type of a function, making it easier to write code in languages like Golang |
• Discussing the features and capabilities of TreeSitter |
• Exploring the potential of snippets in editors |
• Introducing Telescope, a fuzzy finder for NeoVim |
• Describing Telescope's design and goals, including extensibility and configurability |
• Comparing Telescope to FZF and discussing potential use cases |
• Mentioning ongoing development and performance improvements for Telescope |
• The speaker likes FZF but uses Telescope for daily use |
• The speaker recommends using both FZF and Telescope for specific use cases |
• The speaker prefers Telescope's UI and consistency |
• The speaker notes that Telescope integrates well with other editor features |
• The speaker discusses the excitement and enthusiasm around the NeoVim 0.5 release |
• The speaker invites people to join the NeoVim community and contribute |
• The speaker shares resources for getting involved with NeoVim, including a chat room on Element or Matrix |
• Discussion of community engagement and welcoming open-source projects |
• Sharing personal experience with contributing to NeoVim and receiving help from the community |
• Tips for contributing to open-source projects, including commenting on issues and asking for help |
• Importance of appreciating the people behind proprietary software |
• Requesting guests and topics for future episodes of the ChangeLog |
• Final words and shoutouts to the audience and Twitch channel |
• The Galaxy brand move is to get the master feed at ChangeLog.com slash master |
• All podcasts are available in a single feed |
• Special thanks to partners Linode, Fastly, and LaunchDarkly |
• Special thanks to Breakmaster Cylinder for music |
• End of episode |
[0.56 --> 4.86] What's up, welcome back, I'm Adam Stachowiak and you are listening to The Change Log. |
[5.12 --> 10.28] On this show, Jared and I talk with the hackers, leaders, and innovators from all areas of the software world. |
[10.58 --> 13.18] We face our imposter syndrome, so you don't have to. |
[13.52 --> 17.16] Today on The Change Log, Jared is joined by a special co-host, Nick Neesey from JS Party. |
[17.46 --> 21.00] For a follow-up on our Vim episode, talking to TJ DeVries about NeoVim. |
[21.92 --> 25.82] TJ is a core maintainer of NeoVim, and he tells us why it was created in the first place, |
[25.82 --> 29.96] how it differs from Vim, why Lua is awesome for configuration and plugins, |
[30.38 --> 33.58] what LSPs are all about, the cool tech inside TreeSitter, |
[33.88 --> 37.72] and how he's writing his own fuzzy file finder for NeoVim called Telescope. |
[38.04 --> 41.44] Of course, big thanks to our partners Linode, Fastly, and LaunchDarkly. |
[41.74 --> 43.96] We love Linode, they keep it fast and simple. |
[44.22 --> 47.00] Get $100 in credit at linode.com slash changelog. |
[47.24 --> 50.96] Our bandwidth is provided by Fastly. Learn more at fastly.com. |
[50.96 --> 55.12] And get your feature flags, powered by LaunchDarkly. Get a demo at launchdarkly.com. |
[55.82 --> 61.18] This episode is brought to you by Gitpod. |
[61.28 --> 65.48] Gitpod lets you spin up fresh, ephemeral, automated dev environments in the cloud in seconds. |
[66.00 --> 68.42] And I'm here with Johannes Landgraf, co-founder of Gitpod. |
[68.78 --> 71.42] Johannes, GitHub made a big announcement recently with Codespaces, |
[71.76 --> 76.36] validating that it is now time for dev teams to consider what automated dev environments can do for them. |
[76.52 --> 77.30] What do you have to say to that? |
[77.50 --> 80.28] I'd say, welcome to the party, GitHub and Microsoft. |
[80.28 --> 87.64] No, honestly, we were very excited because it validated to the developer community what we have been pioneering over the last years. |
[87.80 --> 90.96] That developer environments need to be automated and ephemeral. |
[91.24 --> 96.04] We are now at the right place and the right time to move software development to the cloud for everybody. |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.