-
-
Notifications
You must be signed in to change notification settings - Fork 222
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Failed to run config
for neorg: `config.lua 56 [neorg]: Unable to determine the currently active operating system!
#1273
Labels
bug
Issues related to bugs. Please attach a severity, a priority and category with this label.
Comments
Squeeeez
added a commit
to Squeeeez/neorg
that referenced
this issue
Jan 19, 2024
vhyrro
pushed a commit
that referenced
this issue
Jan 28, 2024
gruejay
pushed a commit
to gruejay/neorg
that referenced
this issue
Jan 31, 2024
Thanks everyone. |
benlubas
pushed a commit
to benlubas/neorg
that referenced
this issue
Feb 6, 2024
vhyrro
pushed a commit
that referenced
this issue
Feb 17, 2024
sahinf
pushed a commit
to sahinf/neorg
that referenced
this issue
May 15, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
bug
Issues related to bugs. Please attach a severity, a priority and category with this label.
Prerequisites
Neovim Version
NVIM v0.9.4 Build type: Release LuaJIT 2.1.1692716794 system vimrc file: "$VIM/sysinit.vim" fall-back for $VIM: "/usr/local/share/nvim" Run :checkhealth for more info
Neorg setup
Actual behavior
Error occurs on load of neovim, and Neorg fails to load.
Expected behavior
I thought BSD compatibility would precede compatibility of closed source operating systems.
Steps to reproduce
Run neorg on any BSD system.
Potentially conflicting plugins
No response
Other information
Just add both FreeBSD and OpenBSD info to the block of code on line 56 in config.lua, then the problem is solved.
Help
No
Implementation help
I would since the fix would be rather simple, but I am so strapped for time these days. Production critical work as well.
The text was updated successfully, but these errors were encountered: