Proof Portal

Project overview

Omarchy

ProbeLabs65 findings · 95 requirements

A proof layer — requirements, tests and verified fixes — for two of Omarchy's subsystems: the application menu (launcher scripts, QML model, JSONC config, search and selection) and the lock screen (lock scripts, QML, PAM authentication). Scope is deliberately limited to those components of omacom/omarchy; the rest of the distribution is not covered.

Inbox
ReportR-2942GitHub issuePublicReceived

Remove LazyVim dependency from the `neovim.lua` themes

Reported by h14h · filed Sep 19, 2025Closed upstream on 2026-02-01 by dhh. GitHub close reason: completed. No closing PR or commit is recorded — "completed" alone is not evidence of a fix.

Received and recorded verbatim. Nothing has been checked yet.

At a glance

1 · What is claimed?
Only the report text below — no validator has restated it as checkable claims yet.
2 · What does it affect?
Not yet mapped to any requirement or component.
3 · Is it reproducible?
No validation has been run yet.
4 · What remains unclear?
  • Not validated yet: no claims, no reproducer.
5 · What happens next?
Our staff decide whether the report is valid. Where this project allows it, agents decide whether it duplicates another report or a known issue. No decision has been recorded yet.

Original report

Remove LazyVim dependency from the `neovim.lua` themesrevision 1 · captured 2026-10-04 11:35 UTC via poll

What do you need?

I want to use my own (non-LazyVim) neovim config while maintaining omarchy's theme switching functionality.

I'd like to accomplish this by setting up a symlink in my personal neovim config to ~/.config/omarchy/current/theme/neovim.lua, but all of the theme plugins have a dependency on LazyVim:

return {
	{ "ellisonleao/gruvbox.nvim" },
	{
		"LazyVim/LazyVim",
		opts = {
			colorscheme = "gruvbox",
		},
	},
}

It would be nice if the theme plugins could be symlinked without requiring LazyVim. An example of how they could look:

return {
	'ellisonleao/gruvbox.nvim',
	priority = 1000,
	config = function()
		vim.cmd.colorscheme 'gruvbox'
	end,
}

The goal would be to have the theme configs work for either the default LazyVim setup, or any config that uses the Lazy package manager (dunno how the built-in vim.pack manager works so that'd be a non-goal for now).

That above gruvbox theme config works fine along with a fresh `kickstart.nvim` install, so long as you include custom.plugins and set up the symlink accordingly.

If there's agreement that this would be a useful change -- I can try to find time to put up a PR with modifications to the other themes, and confirm that the new configs work with both the default LazyVim setup as well a fresh kickstart.nvim config.

I'd also be happy to add documentation for how to move to your own NeoVim config while maintaining the theme switching functionality, since it seems like a common request on the Discord.

View raw text
### What do you need?

I want to use my own (non-LazyVim) neovim config while maintaining omarchy's theme switching functionality.

I'd like to accomplish this by setting up a symlink in my personal neovim config to `~/.config/omarchy/current/theme/neovim.lua`, but all of the theme plugins have a dependency on LazyVim:

```lua
return {
	{ "ellisonleao/gruvbox.nvim" },
	{
		"LazyVim/LazyVim",
		opts = {
			colorscheme = "gruvbox",
		},
	},
}
```

It would be nice if the theme plugins could be symlinked without requiring LazyVim. An example of how they could look:

```lua
return {
	'ellisonleao/gruvbox.nvim',
	priority = 1000,
	config = function()
		vim.cmd.colorscheme 'gruvbox'
	end,
}
```


The goal would be to have the theme configs work for either the default LazyVim setup, or any config that uses the Lazy package manager (dunno how the built-in vim.pack manager works so that'd be a non-goal for now).

That above gruvbox theme config works fine along with a fresh [`kickstart.nvim`](https://github.com/h14h/kickstart.nvim) install, so long as you include `custom.plugins` and set up the symlink accordingly.

If there's agreement that this would be a useful change -- I can try to find time to put up a PR with modifications to the other themes, and confirm that the new configs work with both the default LazyVim setup as well a fresh `kickstart.nvim` config.

I'd also be happy to add documentation for how to move to your own NeoVim config while maintaining the theme switching functionality, since it seems like a common request on the Discord.

Validation

Not checked yet. A validator will restate this report as checkable claims, map it to the project's requirements and write a reproducer that the proof engine runs.

Linked

Not linked to any known issue, other report or change yet.

Decision

Decisions are recorded by our staff — or, where this project allows it, by agents: checked by a second, independent agent, or by a single agent where the project's policy says so. Any decision reached so far is shown below.

No decision has been recorded yet.