nyoom-engineering / oxocarbon.nvim Goto Github PK

Hi there, I always seek themes with colorschemes for terminal I use (wezterm) to get unified experience.

Would you mind adding support for it? Nightfox has automated generator which can be used to generate those colorschemes of the palettes. It would be most welcomed.

There should be an option to configure and enable transparency, or anything else to make it easier for the user to use the theme in this way. Many themes have this kind of feature, so I thought it was fair to ask.

Note: I took a quick look at the issues and didn't see similar requests, if this has already been answered, sorry.

Hi there, I am not fimiliar with fennel but however lua is built of it seems to be broken at the moment. This patch has fixed it for me:

diff --git a/lua/oxocarbon/init.lua b/lua/oxocarbon/init.lua
index 53cbf19..ba01f77 100644
--- a/lua/oxocarbon/init.lua
+++ b/lua/oxocarbon/init.lua
@@ -1,5 +1,5 @@
 local _2afile_2a = "fnl/oxocarbon/init.fnl"
-local _local_1_ = require("colorutils")
+local _local_1_ = require("oxocarbon.colorutils")
 local blend_hex = _local_1_["blend-hex"]
 local base00 = "#161616"
 local base06 = "#ffffff"
diff --git a/plugin/oxocarbon.vim b/plugin/oxocarbon.vim
index 0427867..adc8e1a 100644
--- a/plugin/oxocarbon.vim
+++ b/plugin/oxocarbon.vim
@@ -1,3 +1,3 @@
 if has("nvim")
-  lua require("oxocarbon.main").init()
+  lua require("oxocarbon")
 endif

How cold that be changed on fennel side?

when i do :colorscheme oxocarbon i get this weird error

Hello, seems like oxocarbon.nvim does not set up any highlighting groups for diffs. This results in ugly (default) highlights in various plugins like neogit and diffview.

Also, CurSearch highlight is used for highlighting search result under the cursor - at the moment such search result gets no highlight at all. It could be as simple as linking it to IncSearch.

Could you please add those as well?

I used Vim-Plug and got an error after downloading that said Post-update hook for oxocarbon.nvim ... Exit status: 127

After some digging, I realized that I must have uninstalled rust at some point because it said cargo wasn't installed, but this isn't clear from the error message.

I'm not sure if this is even fixable, because it seems to just be how Vim-Plug displays the errors by only giving the exit status, but I just wanted to let you know

Look, the "f"s from function items are with the background colored, not the text. It changes when they're in selection line:

Also, It can be a thing of mine configuration, but seemed to be that there's a little lag before the right colors are applied. Maybe it's something related to treesitter. The colors do not apply fast as other colorschemes, they take like 1-2 seconds to apply.

Hey, I kinda liked the statusline used in the screenshots... Is it possible to get that statusline configuration

img:

I get this error after I booted up today, since the only "rust" based plugin i use is this one so I thought it might be related to this plugin.

Here is the error message

thread '<unnamed>' panicked at 'called `Result::unwrap()` on an `Err` value: NvimError("\'ctermbg\' must be string or integer")', /home/iamb4uc/.local/share/cargo/registry/src/github.com-1ecc6299db9ec823/nvim-oxi-0.1.3/src/lua/lua.rs:42:12
                                                note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace
                                                                                                                             fatal runtime error: Rust panics must be rethrown
                                                                                                                                                                              zsh: IOT instruction  nvim
         %

device specification:
OS: void linux
Kernel: 5.19.13_1
Shell: zsh

Right now, markdown documents are almost entirely colored with the default color, which is a bit of a bummer

Nvim is deprecating VertSplit and moving to WinSeparator for borders in 0.10. By default, WinSeparator links to normal which does not look great for most colorschemes.

Hi, I'm loving this theme and already trying to extend it to support some of the plugins that I use (NeoTree, make Telescope look a bit more user friendly etc).

However, not having a color palette reference is makign it quite tricky.

I notice that Base16 Oxocarbon has a really nice palette graphic in it's readme, is it possible to get something like this for this nvim theme too?

Thanks! 🙇

Could we add highlights to function arguments, function type signatures, and enum members, so that input and enum members are highlighted?
I understand this may add colours that are not in the carbon colourscheme, however I think it would improve the syntax highlighting.

Function argument "input" is highlighted in Kanagawa, but not in oxocarbon.
Kanagawa:

Also, the type annotation &str in the function signature isn't highlighted in oxocarbon.
Oxocarbon:

Enum members Up, Down, Left, Right are highlighted in Kanagawa, but not in oxocarbon:
Kanagawa:

Oxocarbon:

the pop-up inputs do not show text, so it's impossible to input text.

I can batter show a picture.
With tokyo-night, when adding/renaming a file in NeoTree:

In oxocarbon:

To reproduce:

• install LazyVim
• install oxocarbon plugin

I just updated oxocarbon using Packer and now I can't start neovim anymore:

thread '<unnamed>' panicked at 'called `Result::unwrap()` on an `Err` value: NvimError("nocombine is not a boolean")', /<home>/.cargo/git/checkouts/nvim-oxi-68d2fdc1d1cdbe82/425e63d/nvim-oxi/src/lua/lua.rs:45:12
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace
fatal runtime error: Rust panics must be rethrown
[1]    207427 IOT instruction (core dumped)  nvim

The backtrace (if enabled) is unreadable because it somehow corrupts my terminal and I can't type or scroll anymore. If you need the core dump I'll post it.

I'm using Neovim v0.7.2 on Arch.

I have treesitter with typescript and tsx installed.

When I do this:

vim.cmd.colorscheme "oxocarbon"

I get incorrect colors:

But when I load a different theme first:

vim.cmd.colorscheme "everforest"
vim.cmd.colorscheme "oxocarbon"

I get correct colors:

Am I doing something wrong? It might have to do something with #4

Please support Indent Blankline color.

With my dotfiles and latest oxocarbon, indent-blankline show (maybe) ugly blue color.

It would make looking at markdown files more pleasing to the eyes.

I have been using your theme for the last view weeks. But lately I am not able to use it anymore.
When I enter the command:

:colorscheme oxocarbon

Then neovim crashes with this message.

thread '<unnamed>' panicked at 'called `Result::unwrap()` on an `Err` value: NvimError("\'ctermbg\' must be string or integer")', /home/michael/.cargo/registry/src/github.com-1ecc6299db9ec823/nvim-oxi-0.1.3/src/lua/lua.rs:42:12
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace 
fatal runtime error: Rust panics must be rethrown
fish: Job 1, 'nvim' terminated by signal SIGABRT (Abort)

lualine.nvim is a popular neovim status line plugin which has support for various themes, but doesn't really work with oxocarbon. After having used oxocarbon for a few weeks now I can't go back to any other theme so I would love to have oxocarbon as a theme for lualine.

Hi, I get this error when trying the theme with :colo oxocarbon.

E5113: Error while calling lua chunk: .../site/pack/packer/start/impatient.nvim/lua/impatient.lua:264: ...m/site/pack/packer/start
/oxocarbon.nvim/lua/oxocarbon.so:1: '=' expected

The theme has been installed, the install.sh script has been run by packer and I tried running it manually (it succeeded). Rust version is 1.62, neovim is latest head:

NVIM v0.8.0-dev-751-g8952def50                                                                                                                                                                                                                                         
Build type: Release                                                                                                                                                                                                                                                    
LuaJIT 2.1.0-beta3 

EDIT: Forgot to add, I'm on macOs Monterey, 12.3.1, Apple M1.

Tested on latest neovim nightly.

:PackerInstall fails when i try to install

Add vscode support
I have made a theme already, see if it is up to your standards :)
Link

I came here trying to install this theme some three months ago and this error was ocurring to a lot of people. Still not working?

oxocarbon doesn't show bold and italic font there??

I have treesitter installed but it still seems a little monotone. I was wondering if the theme is meant to look like this for tsx files.

Hello,

Maybe I've done something wrong, idk.

1. I installed rust with rustc 1.62.1 (e092d0b6b 2022-07-16), (start new session to reload zsh)
2. then I add this line Plug 'shaunsingh/oxocarbon.nvim', { 'do': './install.sh' } to add the theme with vimplug.
3. Added this line too colorscheme oxocarbon
4. Install plug ; everything is ok on screen
5. But nothing is happening. No theme loaded.

I tried to start ./install.sh and I have this error:

The pictures shows that « target/release/liboxocarbon.so » and « lua/oxocarbon.so » targeted the same file

I'm not sure what to do next ? Or if I did something wrong during the first steps

Thanks for your help :)
have a nice day

If I use oxocarbon, another colorscheme and oxocarbon again, it fails. Eg.:

vim.cmd("colorscheme oxocarbon")
vim.cmd("colorscheme default")
vim.cmd("colorscheme oxocarbon")

It also happens when I :PackerCompile.

Apologies if this is not the right place for this.
Been using oxocarbon for a week now and loving it.
It would great to have oxocarbon for the terminal too. Any possible plans for that?

I wish I could help with this but I have zero clue how themes are done.

Hey! Great colorscheme.

For some reason, a few days ago it started crashing nightly neovim for me. I'm using the AppImage version.

thread '<unnamed>' panicked at 'called `Result::unwrap()` on an `Err` value: NvimError("\'ctermbg\' must be string or integer")', /home/ml/.cargo/git/checkouts/nvim-oxi-68d2fdc1d1cdbe82/15fb30d/nvim-oxi/src/lua/lua.rs:41:12
           note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace
                                                                                        fatal runtime error: Rust panics must be rethrown
                               Aborted (core dumped)

It crashes with the above message. With RUST_BACKTRACE=1, we get more verbosity.

thread '<unnamed>' panicked at 'called `Result::unwrap()` on an `Err` value: NvimError("\'ctermbg\' must be string or integer")', /home/ml/.cargo/git/checkouts/nvim-oxi-68d2fdc1d1cdbe82/15fb30d/nvim-oxi/src/lua/lua.rs:41:12
stack backtrace:
   0: rust_begin_unwind
             at /rustc/1.63.0/library/std/src/panicking.rs:584:5
   1: core::panicking::panic_fmt
             at /rustc/1.63.0/library/core/src/panicking.rs:142:14
   2: core::result::unwrap_failed
             at /rustc/1.63.0/library/core/src/result.rs:1805:5
   3: luaopen_oxocarbon
�[?25l�(B�[m�[H�[2J�[?1004h�[?12h�[?25h   4: lj_BC_FUNCC
   5: lj_cf_package_require
             at /home/runner/work/neovim/neovim/.deps/build/src/luajit/src/lib_package.c:464:3
   6: lj_BC_FUNCC
   7: lua_pcall
             at /home/runner/work/neovim/neovim/.deps/build/src/luajit/src/lj_api.c:1145:12
   8: nlua_pcall
             at /home/runner/work/neovim/neovim/src/nvim/lua/executor.c:135:16
   9: nlua_exec_file
             at /home/runner/work/neovim/neovim/src/nvim/lua/executor.c:1631:7
  10: do_source
             at /home/runner/work/neovim/neovim/src/nvim/runtime.c:1991:5
  11: source_callback
             at /home/runner/work/neovim/neovim/src/nvim/runtime.c:197:9
  12: do_in_cached_path
             at /home/runner/work/neovim/neovim/src/nvim/runtime.c:404:14
  13: do_in_runtimepath
             at /home/runner/work/neovim/neovim/src/nvim/runtime.c:749:16
  14: source_runtime
             at /home/runner/work/neovim/neovim/src/nvim/runtime.c:767:10
  15: load_colors
             at /home/runner/work/neovim/neovim/src/nvim/highlight_group.c:582:14
  16: ex_colorscheme
             at /home/runner/work/neovim/neovim/src/nvim/ex_docmd.c:5160:14
  17: execute_cmd0
             at /home/runner/work/neovim/neovim/src/nvim/ex_docmd.c:1569:29
  18: do_one_cmd
             at /home/runner/work/neovim/neovim/src/nvim/ex_docmd.c:2218:7
  19: do_cmdline
             at /home/runner/work/neovim/neovim/src/nvim/ex_docmd.c:571:20
  20: source_using_linegetter
             at /home/runner/work/neovim/neovim/src/nvim/runtime.c:1774:16
  21: do_source_str
             at /home/runner/work/neovim/neovim/src/nvim/runtime.c:1825:10
  22: nvim_exec
             at /home/runner/work/neovim/neovim/src/nvim/api/vimscript.c:67:3
  23: nlua_api_nvim_exec
             at /home/runner/work/neovim/neovim/build/src/nvim/auto/lua_api_c_bindings.generated.c:5473:22
  24: lj_BC_FUNCC
  25: lj_cf_package_require
             at /home/runner/work/neovim/neovim/.deps/build/src/luajit/src/lib_package.c:464:3
  26: lj_BC_FUNCC
  27: lua_pcall
             at /home/runner/work/neovim/neovim/.deps/build/src/luajit/src/lj_api.c:1145:12
  28: nlua_pcall
             at /home/runner/work/neovim/neovim/src/nvim/lua/executor.c:135:16
  29: nlua_exec_file
             at /home/runner/work/neovim/neovim/src/nvim/lua/executor.c:1631:7
  30: do_source
             at /home/runner/work/neovim/neovim/src/nvim/runtime.c:1991:5
  31: do_user_initialization
             at /home/runner/work/neovim/neovim/src/nvim/main.c:1943:10
  32: source_startup_scripts
             at /home/runner/work/neovim/neovim/src/nvim/main.c:2020:9
  33: main
             at /home/runner/work/neovim/neovim/src/nvim/main.c:396:3
  34: <unknown>
  35: __libc_start_main
  36: _start
note: Some details are omitted, run with `RUST_BACKTRACE=full` for a verbose backtrace.
fatal runtime error: Rust panics must be rethrown

Only applying the colors to custom components (like "Section") and not for normal tags (like "div"):
Obs: I don't know if it's a bug report or a feature request.

Also, white for props/attributes doesn't seems right.

They're all way too low contrast. There's a stream of theprimeagen spending way too long trying to find a good screenshot. (He finally manages to get one here.)

I don't know what the hell you used, but please for the love of your theme, don't disgrace it with these terrible screenshots. For the record, it looks great on my machine (and probably yours too).

Hi,
I just started using oxocarbon, both the dark and light versions and really like it. Thanks for this!

In the light version everything is great, however the LspReferenceText background is quite dark, I think it is base03=#161616. Not sure if this is a choice by design, but it really makes it difficult to see the text behind it many times:

I just want to know if this is a design choice, otherwise I can change it in my own config.

Thanks in advance!

There should be an option to darken inactive windows and windows of plugins like toggleterm, nvim-tree etc. This iwould be similar to material.nvim theme which is quite popular.

I have treesitter and the treesiter-textobjects configured exactly as yours..

my config used lazy.nvim

local M = {
  "nyoom-engineering/oxocarbon.nvim",
  lazy = false,
  priority = 1000,
  enabled = function() return vim.g.theme == 'oxocarbon' end,
}

function M.config()
  require('oxocarbon').setup {
  }
  vim.cmd [[ colorscheme 'oxocarbon' ]]
end

return M

This is my config:

use { "shaunsingh/oxocarbon.nvim", run = "./install.sh" }

I install successfully using :PackerSync but enabling the colourscheme displays the following error:

Error detected while processing /Users/integralist/.local/share/nvim/site/pack/packer/start/oxocarbon.nvim/colors/oxocarbon.lua:
E5113: Error while calling lua chunk: ...te/pack/packer/start/oxocarbon.nvim/colors/oxocarbon.lua:1: module 'oxocarbon' not found:
        no field package.preload['oxocarbon']
        no file './oxocarbon.lua'
        no file '/opt/homebrew/share/luajit-2.1.0-beta3/oxocarbon.lua'
        no file '/usr/local/share/lua/5.1/oxocarbon.lua'
        no file '/usr/local/share/lua/5.1/oxocarbon/init.lua'
        no file '/opt/homebrew/share/lua/5.1/oxocarbon.lua'
        no file '/opt/homebrew/share/lua/5.1/oxocarbon/init.lua'
        no file '/Users/integralist/.cache/nvim/packer_hererocks/2.1.0-beta3/share/lua/5.1/oxocarbon.lua'
        no file '/Users/integralist/.cache/nvim/packer_hererocks/2.1.0-beta3/share/lua/5.1/oxocarbon/init.lua'
        no file '/Users/integralist/.cache/nvim/packer_hererocks/2.1.0-beta3/lib/luarocks/rocks-5.1/oxocarbon.lua'
        no file '/Users/integralist/.cache/nvim/packer_hererocks/2.1.0-beta3/lib/luarocks/rocks-5.1/oxocarbon/init.lua'
        no file './oxocarbon.so'
        no file '/usr/local/lib/lua/5.1/oxocarbon.so'
        no file '/opt/homebrew/lib/lua/5.1/oxocarbon.so'
        no file '/usr/local/lib/lua/5.1/loadall.so'
        no file '/Users/integralist/.cache/nvim/packer_hererocks/2.1.0-beta3/lib/lua/5.1/oxocarbon.so'
stack traceback:
        [C]: in function 'require'
        ...te/pack/packer/start/oxocarbon.nvim/colors/oxocarbon.lua:1: in main chunk

Thanks for the cool theme!

is is possible to disable all the bolds applied by this theme, other than going through every single highlight group manually?

To reproduce:

1. remove everything that sets a colorscheme from your neovim config
2. run :colorscheme oxocarbon
3. run :colorscheme blue (or any other colorscheme)
4. run :colorscheme oxocarbon again

The first two colorscheme will work, but setting oxocarbon as colorscheme a second time does not work. This is relevant for some use cases where you want to change your colorscheme during runtime, for example styler or auto-dark-mode.

I checked, oxocarbon seems to be the only theme that has this issue, other themes, builtin or from the community, do not have this problem.

Cargo build continue to break by

Caused by:
  object not found - no match for id (3afc693ef16b45b19f255df2144688ed936f1aa9); class=Odb (9); code=NotFound (-3)

revert to previous commit fix this.

This doesn't happen immediately, it seems to happen after nvim has been open for a while and it's been used in that time, I'm not sure what triggers it

• Install the lazy vim starter
• Do things as you normally would for a while
• Note that both that focused and blurred tabs are the same color
  Please let me know if you are able to reproduce this or where I can look to see what's causing it.

I'm running nvim version 0.9.0 installed from Brew

After setting the color theme to oxocarbon, neovim crashes with this message:

nvim(64121,0x1047ec580) malloc: *** error for object 0x1046886ae: pointer being freed was not allocated
nvim(64121,0x1047ec580) malloc: *** set a breakpoint in malloc_error_break to debug
zsh: abort
nvim init.lua

I'm assuming that this is due to the new nvim minor version. Just guessing that the native oxocarbon stuff was compiled against 0.8.*.

Other details

oxocarbon version: commit: bb59d86

neovim version:

❯ nvim --version
NVIM v0.9.0-dev-1549+g523b1943c-dirty
Build type: Release
LuaJIT 2.1.0-beta3
Compiled by ririchardson@LUSHF66P5Q2K0

Features: +acl +iconv +tui
See ":help feature-compile"

   system vimrc file: "$VIM/sysinit.vim"
  fall-back for $VIM: "/opt/homebrew/Cellar/neovim/HEAD-523b194/share/nvim"

Run :checkhealth for more info

Since neovim/neovim#21100 has been merged in nightly.