dotfiles VS lazy.nvim

You can set this up with even less customization. Here's my snippet for doing so [0]. In this way, the default rule for all containers that are part of compose projects gets assigned a subdomain (service.compose-stack.lvh.me).

However, even with my tweaks, the overall solution is still limited. Because it's not on "localhost", the browser considers it an "insecure context" unless you also set up local HTTPS.

[0] https://github.com/CGamesPlay/dotfiles/blob/13659d19ca899cea...

I’ve started using Remote OSS [0] with some custom scripts to install and run the remote code host. Works great on remote servers and even with devcontainers on remote hosts. You can use a script like the one here to handle automatically installing and setting up the tunnel [1]. I’m working on a PR that adds a way to automatically run custom scripts to set up the tunnels as well [1].

[0] https://open-vsx.org/extension/xaberus/remote-oss

[1] https://github.com/CGamesPlay/dotfiles/blob/master/files/.lo...

[2] https://github.com/xaberus/vscode-remote-oss/pull/9

I built a "Control-P" feature for fish that would also be a good trigger for this tool. Basically, you activate the shortcut to run the program, then it will change the directory based on the selection, but restore your original command line after. So you can be halfway through a command before realizing you are in the wrong place. Also, can cd with one fewer keystroke. My version is at [0], but obviously modifiable for other tools like this one.

[0] https://github.com/CGamesPlay/dotfiles/blob/master/files/.co...

FWIW, I still use regular vim with ale [0] and it does everything I want. It formats files with Black and isort, shows ruff and pyright errors, supports jumping to definitions, and has variable information available on hover. I have collected my config over the past several years, but I pretty rarely encounter errors with it.

[0]: https://github.com/dense-analysis/ale [1] https://github.com/CGamesPlay/dotfiles/blob/master/files/.co...

I think the first example should have been done with direnv rather than having a manual step, but I supposed to each their own. The other examples are all pretty neat.

I recently set up fasd, which I recommend, but I tied it together with fzf, which makes it really nice.

fasd: https://github.com/clvv/fasd

tie it with fzf: https://github.com/CGamesPlay/dotfiles/blob/master/files/.co...

First, I installed NeoSolarized.nvim via lazy.nvim, so the code would be simple like the following one.

In my case, I have switched to Lazy.nvim for all of my Neovim plugin needs ( Thanks again Folke! ), so it would be great if you were at least minimally familiar with how Lazy works as well.

If you've read old tutorials about Neovim configuration you've find the way they create keymaps is a little bit different from what people do now. And if you check other people's configuration sometimes you'll find they create their keymaps using lazy.nvim. This is causing confusion among Neovim users.

The basic plugins will be downloaded on the first run using Lazy, a package manager for Neovim that loads only the necessary plugins as you use them. Once it's done you should be looking at a full-fledged IDE.

it looks more like something is wrong with your neovim install rather than your config. based on this lazy.nvim issue you may have an updated neovim binary but your neovim runtime files are not up to date. try completely reinstalling neovim.

It is possible to manage plugins yourself, but I would recommend a plugin manager such as Lazy (https://github.com/folke/lazy.nvim). There are many more plugins that most would argue are virtually essential, but these should at least be able to get you some autocompletion and highlighting without too much messing about. Be sure to read the install instructions for each of these plugins!

whenever i add this: ``` -- bootstrap lazy.nvim local lazypath = vim.fn.stdpath("data") .. "/lazy/lazy.nvim" if not vim.loop.fs_stat(lazypath) then vim.fn.system({ "git", "clone", "--filter=blob:none", "https://github.com/folke/lazy.nvim.git", "--branch=stable", -- latest stable release lazypath, }) end vim.opt.rtp:prepend(lazypath)

Easily updatable. Versions are stored in manifests and can be easily updated with a single command. neovim's lazy-lock.json however is managed separately by lazy.

require("keymaps") local lazypath = vim.fn.stdpath("data") .. "/lazy/lazy.nvim" if not vim.loop.fs_stat(lazypath) then vim.fn.system({ "git", "clone", "--filter=blob:none", "https://github.com/folke/lazy.nvim.git", "--branch=stable", -- latest stable release lazypath, }) end vim.opt.rtp:prepend(lazypath) require("lazy").setup({ "folke/tokyonight.nvim", {"nvim-treesitter/nvim-treesitter", build = ":TSUpdate"}, { 'nvim-telescope/telescope.nvim', tag = '0.1.4', dependencies = { 'nvim-lua/plenary.nvim' } } })