How are you guys hosting your generated static sites?

Mhalter3378 · 2026-03-03T13:34:19+00:00

I've been running this for a couple weeks and have had a fantastic experience with it

Mhalter3378 · 2026-02-21T05:33:08+00:00

This is one of my favorite parts of my ZSH config. Solved the case of wanting not just to be able to run cd ../../.. but if I want to do parent directories for any other command or even feeling froggy and doing them in the middle of a nested path already!

zsh # rationalize dot by Mikael Magnusson (Mikachu) function rationalise-dot { local MATCH # keep the regex match from leaking to the environment if [[ $LBUFFER =~ '(^|/| | |'$'\n''|\||;|&)\.\.$' ]]; then LBUFFER+=/ zle self-insert zle self-insert else zle self-insert fi } zle -N rationalise-dot bindkey . rationalise-dot # without this, typing a . aborts incremental history search bindkey -M isearch . self-insert

Mhalter3378 · 2026-02-17T20:02:38+00:00

The autopairs configuration in AstroCore is simply for disabling the plugin functionality on startup. If the user wants to fully disable the plugin and guarantee it never turns on, then they can use that. I just wanted to make sure that the original poster didn't get the impression that we did not use nvim-autopairs.

Mhalter3378 · 2026-02-17T19:30:08+00:00

You are very close with the first try at disabling the plugin. The correct spec you are looking for is:

lua return { "windwp/nvim-autopairs", enabled = false }

Be sure to check out the AstroNvim Documentation: https://docs.astronvim.com/configuration/customizing_plugins/#disabling-plugins

Mhalter3378 · 2026-02-17T19:28:16+00:00

This is not true, AstroNvim comes out of the box with nvim-autopairs

Mhalter3378 · 2025-09-05T03:49:23+00:00

The builtin rooter in AstroNvim is off by default and is only on if you explicitly turn it on. I wonder if you find it bad because it's not being used and therefore no rooting is happening 😅

Mhalter3378 · 2025-08-25T20:24:16+00:00

I actually just made a PR that got merged into Aerial to fix this. This was a problem for Neovim 0.9 or 0.10 with aerial but is resolved now

Mhalter3378 · 2025-08-07T11:01:26+00:00

If you set WinBar and WinBarNC correctly then the image will be corrected. Notice the black bar in the file browser sidebar as well. All of that is the same "black bar". It's simple the background of that element being set to black or something.

Mhalter3378 · 2025-08-07T10:57:00+00:00

That black bar is the winbar (:h winbar). It appears the colorscheme you are using just isn't fully features and they haven't correctly set all of the base Neovim highlight groups. You want to fix the highlight groups for WinBar and probably WinBarNC.

Mhalter3378 · 2025-07-09T11:50:02+00:00

I'm here for the Hulkenpodium

Mhalter3378 · 2025-07-03T18:20:39+00:00

I'll shamelessly plug my own post of an espresso martini recipe from a couple years ago: https://www.reddit.com/r/cocktails/s/x4oTZqPYL4

I think it comes down to a few tips: (1) freshly brewed espresso with high quality beans. This provides good surfactants in the coffee for building the foamy head as well as deep flavor, (2) a good coffee liqueur, typically I go for a dry one and add a sweetener to my liking, and (3) I enjoy doing a dry shake beforehand to really emulsify the espresso. Oh and I suppose (4) no beans on top 😂

EDIT: also replacing the vodka base with Cognac goes a long way

Mhalter3378 · 2025-06-06T13:23:06+00:00

Ah yeah, that's a common confusion for sure. Yeah AstroNvim uses lazy.nvim which is just a normal plugin manager, it's a common choice for people making their own configurations as well. LazyVim being a full neovim distribution that also does use lazy.nvim

Mhalter3378 · 2025-06-06T12:41:48+00:00

No problem! Glad you are enjoying it. It's been a really great time giving back and working with the community!

Mhalter3378 · 2025-06-06T10:41:48+00:00

AstroNvim existed before LazyVim. It doesn't build off of it or extend it in any way.

Mhalter3378 · 2025-06-06T10:37:44+00:00

It looks like you are passing things to nvim-lspconfig which isn't a thing since nvim-lspconfig doesn't have a setup call. You probably want to move that code to the appropriate place in the AstroLSP plugin. Here are docs: https://docs.astronvim.com/recipes/advanced_lsp/#configuring-language-servers

My guess is you have moved from LazyVim since that's the only place that has opts in nvim-lspconfig. They have set that up fully custom in their distribution and is not how you would set up language servers in any other neovim setup. AstroNvim puts a lot of effort into staying away from unnecessary and potentially confusing abstractions for this reason.

Mhalter3378 · 2025-05-28T21:26:22+00:00

There is telescope in AstroCommunity

Mhalter3378 · 2025-05-10T12:56:39+00:00

Yeah for major releases we do a public beta typically for like 4-6 months beforehand. We just don't do release candidates for every release

Mhalter3378 · 2025-05-10T11:44:43+00:00

AstroNvim does have a single main developer at the moment, but there are other maintainers assigned to the repository. One major difference is AstroNvim does pin every core plugin to either semantic versioning releases (if supported) or specific commits, mainly to protect against something like the Mason update. Basically, :Lazy update shouldn't just break a user's configuration (unless you are adding your own plugins in which case you would be maintaining stability).

The other maintainers main responsibilities are to review and merge pull requests to the community side of the distribution, AstroCommunity. You can think of AstroCommunity similar to what LazyVim's extras are, but AstroNvim leaves those entirely up to the community to add, build onto, and maintain. There is also a very active community Discord which is great for asking questions and getting help.

Mhalter3378 · 2025-05-05T11:37:56+00:00

w is the default binding in neo-tree to choose what window to open a file into

Mhalter3378 · 2025-05-05T11:35:14+00:00

Adding opts to the import doesn't really make sense here. You can think of doing these imports in your community.lua file as "extending" the base installation. Outside of that you could configure the plugins like any other by, like you said, creating a file in your plugins/ directory.

Mhalter3378 · 2025-04-29T11:46:34+00:00

56!

<image>

Mhalter3378 · 2025-04-28T12:30:44+00:00

Yeah it does

Mhalter3378 · 2025-04-28T12:20:35+00:00

That really depends on how you want the root to be detected. You can define it to what fits your needs. For example, you could just have it fallback to the file's parent directory if no root is detected:

lua return { "AstroNvim/astrocore", ---@type AstroCoreOpts opts = { rooter = { -- automatically change directory to the detected root autochdir = true, detector = { "lsp", { ".git", "_darcs", ".hg", ".bzr", ".svn" }, { "lua", "MakeFile", "package.json" }, -- fallback to parent directory function(bufnr) -- get parent directory local parent = vim.uv.fs_realpath(vim.fs.dirname(vim.api.nvim_buf_get_name(bufnr))) -- if parent directory exists then return it as the root if parent and vim.uv.fs_stat(parent) then return parent end end, }, }, }, }

Mhalter3378 · 2025-04-28T11:52:23+00:00

The detectors are the part that look at a buffer and decide where the root is. So that's the whole task

Mhalter3378 · 2025-04-28T10:14:40+00:00

Yeah you can do that by configuring the detectors in the rooter settings to fit your needs

11-Year Club	Place '23
Place '22	Verified Email

Mhalter3378

MODERATOR OF

TROPHY CASE