Explore >> Select a destination
|
You are here 
|
kdheepak.com | ||
| | | | |
dankelley.github.io
|
|
| | | | | I just made a youtube video in which I show how to navigate through code using the neovim package called lunarvim. My test case is an R file. In a nutshell, I show two commands, each enabled by a few keystrokes. | |
| | | | |
ericlathrop.com
|
|
| | | | | I've been migrating from vim to neovim to get some of the fancy tree-sitter and LSP features. It's really nice when your editor understands the actual nature of your code. Anyways I got that stuff working, but I needed neovim to talk to Godot's built-in language server. If you're using nvim-lspconfig, it's as easy as adding the following code to that plugin's configuration: | |
| | | | |
www.adamalbrecht.com
|
|
| | | | | In order for testing to become part of your development workflow, it needs to become a habit. And like any habit, its biggest enemy is neglect. Too often I'll be in a rush and not add tests to my code for a day, and that turns into a week and then a month, and suddenly I have an app where half of my codebase is untested and the other half has breaking tests. There are many things you can do to help keep this habit (hooking up a CI server immediately comes to mind), but an important one is to make running your tests as quick and easy as possible. One way I do this is by making my ruby tests (either Rspec or Minitest) extremely easy to run while I'm using Vim (and Tmux). With one quick keystroke, I can run the current test file or individual test in a new Tmux... | |
| | | | |
stevelosh.com
|
|
| | | [AI summary] The text is a comprehensive guide to Common Lisp, covering its structure, libraries, and ecosystem. It explains the different layers of project organization, including files, packages, systems, and projects, and highlights popular libraries for various tasks such as utilities, threading, foreign function interfaces, regular expressions, HTTP clients, and more. The guide also discusses tools like Quicklisp and ASDF for managing dependencies and projects, and touches on the stability and community of the language. It concludes by emphasizing the depth of Common Lisp and the importance of careful study for mastering it. | ||
