Explore >> Select a destination
|
You are here 
|
vimcasts.org | ||
| | | | |
www.mintbit.com
|
|
| | | | | Ruby is known for its flexibility and powerful metaprogramming capabilities. One such method that often comes up in Ruby development, particularly in Ruby on Rails applications, is instance_exec. It allows developers to execute a block of code within the context of an object's instance, making it extremely useful for dynamically executing code within objects without exposing unnecessary details or methods. | |
| | | | |
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: | |
| | | | |
danielmangum.com
|
|
| | | | | I have been using Vivado for moss RTL development, which, despite its notoriously large install size, offers a fairly decent developer experience. Or maybe I have just been using it for too long. I'm not sure I would have said this a few months ago. However, I still prefer to write Verilog in Neovim, as it allows me to use vim motions, as well as switch between RTL and software code without changing my workflow. | |
| | | | |
dusty.phillips.codes
|
|
| | | Throughout my career, Ive at least tried most of the available programming editors. More than two decades ago, I heard about the vi-vs-emacs debate, and made a pact with myself to use both for at least a year before deciding which I preferred. I started with vim, switched to emacs after a year, and decided I preferred vim. I joined the sublime-text bandwagon for a year or two in the early 2010s, switched back to vim in the middle of the decade, and eventually did the big switch to vscode. | ||
