craftzdog / solarized-osaka.nvim Goto Github PK

Did you check docs and existing issues?

• I have read all the solarized-osaka.nvim docs
• I have searched the existing issues of solarized-osaka.nvim
• I have searched the existing issues of plugins related to this issue

Neovim version (nvim -v)

0.10

Operating system/version

Arch Linux

Describe the bug

The colors are not properly working for the html tags which you can see from the image below:

On a .tsx files this issue goes away.

Steps To Reproduce

1. Create a .jsx file
2. Open

Expected Behavior

The colors should be consistent as they are when using .tsx format but instead are not working properly.

Repro

-- DO NOT change the paths and don't remove the colorscheme
local root = vim.fn.fnamemodify("./.repro", ":p")

-- set stdpaths to use .repro
for _, name in ipairs({ "config", "data", "state", "cache" }) do
  vim.env[("XDG_%s_HOME"):format(name:upper())] = root .. "/" .. name
end

-- bootstrap lazy
local lazypath = root .. "/plugins/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", lazypath, })
end
vim.opt.runtimepath:prepend(lazypath)

-- install plugins
local plugins = {
  "craftzdog/solarized-osaka.nvim",
  "craftzdog/solarized-osaka.nvim",
  -- add any other plugins here
}
require("lazy").setup(plugins, {
  root = root .. "/plugins",
})

vim.cmd.colorscheme("solarized-osaka")
-- add anything else here

Did you check docs and existing issues?

• I have read all the tokyonight.nvim docs
• I have searched the existing issues of tokyonight.nvim
• I have searched the existing issues of plugins related to this issue

Neovim version (nvim -v)

v0.9.2

Operating system/version

Ubuntu 22.04

Describe the bug

on_highlight options is not working when set.

It's seems the function is commented by accident?

Steps To Reproduce

1. Set on_highlight option when call require("solarized-osaka").setup()

Expected Behavior

The specific highlight group should be overwritten when the on_highlight callback was set.

Repro

No response

Did you check docs and existing issues?

• I have read all the solarized-osaka.nvim docs
• I have searched the existing issues of solarized-osaka.nvim
• I have searched the existing issues of plugins related to this issue

Neovim version (nvim -v)

NVIM v0.10.0-dev-2048+g367e52cc7-Homebrew

Operating system/version

MacOs Venture 13.6.1

Describe the bug

I am using nvim-bqf and have troubles rendering the preview window background highlight with the same background colour as the normal buffer. In particular, the window colour seems to default to a darker shade as in the screenshot below:

I have checked the definitions of the theme colour highlight groups but I cannot seem to find the correct one that applies to it (I tried BufferAlternate/BufferInactive and so forth).

To reproduce I am using the following configuration

{
"craftzdog/solarized-osaka.nvim",
lazy = false,
priority = 1000,
opts = {
	transparent = true,
	styles = {
		keywords = { italic = false },
		sidebars = "transparent",
		floats = "transparent",
	},
},
init = function()
	vim.cmd([[colorscheme solarized-osaka]])
end,
}

What is the specific highlight group to modify in this case?

P. S. I have tried changing sidebars/floats option values to no avail.

Steps To Reproduce

1. use the configuration provided above
2. open the quickfix window
3. colours default to a darker shade than the normal buffer

Expected Behavior

The background colour of the nvim-bqf preview window is as the normal buffer.

Repro

No response

Color files in extra, like kitty, still use tokyonight colors.

Did you check the docs?

• I have read all the solarized-osaka.nvim docs

Is your feature request related to a problem? Please describe.

I like more the older (2nd lualine in screenshot) variant, in which section b has a different color than section c.

Is there a way to customize this via the config/opts for solarized-osaka?

I know there is an issue #12 in which section b was matched to the color of section c. But now the difference between section b and c has disappeared.

Describe the solution you'd like

An option or highlight group, alternatively a tip on how I can achieve this using the available options.

Describe alternatives you've considered

Additional context

Did you check docs and existing issues?

• I have read all the solarized-osaka.nvim docs
• I have searched the existing issues of solarized-osaka.nvim
• I have searched the existing issues of plugins related to this issue

Neovim version (nvim -v)

0.9.5

Operating system/version

14.3.1

Describe the bug

Using (lspsaga](https://github.com/nvimdev/lspsaga.nvim) with breadcrumb, Winbar background flash while cursor moves around empty line or function call and statement

Steps To Reproduce

function call with winbar background

empty line with winbar background

statment without background

Expected Behavior

always with/without background color

Repro

-- DO NOT change the paths and don't remove the colorscheme
local root = vim.fn.fnamemodify("./.repro", ":p")

-- set stdpaths to use .repro
for _, name in ipairs({ "config", "data", "state", "cache" }) do
  vim.env[("XDG_%s_HOME"):format(name:upper())] = root .. "/" .. name
end

-- bootstrap lazy
local lazypath = root .. "/plugins/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", lazypath, })
end
vim.opt.runtimepath:prepend(lazypath)

-- install plugins
local plugins = {
  "craftzdog/solarized-osaka.nvim",
  "craftzdog/solarized-osaka.nvim",
  -- add any other plugins here
  "nvimdev/lspsaga.nvim"
}
require("lazy").setup(plugins, {
  root = root .. "/plugins",
})

vim.cmd.colorscheme("solarized-osaka")
-- add anything else here

Did you check docs and existing issues?

• I have read all the solarized-osaka.nvim docs
• I have searched the existing issues of solarized-osaka.nvim
• I have searched the existing issues of plugins related to this issue

Neovim version (nvim -v)

v0.9.5

Operating system/version

Arch Linux

Describe the bug

The colorscheme is complete broken on .tsx files.
This issue first occurred with .jsx, html and other files but .tsx files where working properly.
For some reason similar issue has now come back for .tsx files.

As you can see it is now broken on .tsx files i had not opened a tsx file for some while so i just noticed it today.

Steps To Reproduce

Open any .tsx file.

Expected Behavior

Normal syntax

Repro

-- DO NOT change the paths and don't remove the colorscheme
local root = vim.fn.fnamemodify("./.repro", ":p")

-- set stdpaths to use .repro
for _, name in ipairs({ "config", "data", "state", "cache" }) do
  vim.env[("XDG_%s_HOME"):format(name:upper())] = root .. "/" .. name
end

-- bootstrap lazy
local lazypath = root .. "/plugins/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", lazypath, })
end
vim.opt.runtimepath:prepend(lazypath)

-- install plugins
local plugins = {
  "craftzdog/solarized-osaka.nvim",
  "craftzdog/solarized-osaka.nvim",
  -- add any other plugins here
}
require("lazy").setup(plugins, {
  root = root .. "/plugins",
})

vim.cmd.colorscheme("solarized-osaka")
-- add anything else here

Did you check the docs?

• I have read all the solarized-osaka.nvim docs

Is your feature request related to a problem? Please describe.

Selection highlighting is hard to read.

Describe the solution you'd like

I find that selected text is too jumbled with all the different colors. Ideally, selected text would work like other themes where it's a single color, semi-transparent with the original highlight colors coming through.

Describe alternatives you've considered

I'm sure there is a way to overwrite those colors, but I'm not familiar enough with how theme colors work in nvim.

Additional context

No response

Hi there, I really like your colorscheme. The thing is that I often use tmux inside of zellij. Anyway, I pretty much copy/pasted your tmux color scheme, and then matched the Zellij colorscheme to it. Either example will work equally well. Anyway, I thought I would share it. I am totally rocking your colorscheme in alacritty, nvim, dmenu, dwm, tmux, and now zellij. Have a nice day. Thanks, Shasten -- @the_jr_dev (Twitter)

// Osaka colorscheme for Zellij
// hexidecimal code
theme { 
    solarized-osaka {
        fg "#fdf6e3"
        bg "#2e3440"
        black "#2e3440"
        red "#002b36"
        green "#7aa2f7"
        yellow "#b58900"
        blue "#7aa2f7"
        magenta "#d33682"
        cyan "#2aa198"
        white "#eee8d5"
        orange "#cb4b16"
    }
}

// rgb code
theme { 
    solarized-osaka {
        fg 253 246 227
        bg 46 52 64
        black 46 52 64
        red 0 43 54
        green 122 162 247
        yellow 181 137 0
        blue 122 162 247
        magenta 211 54 130
        cyan 42 161 152
        white 238 232 213
        orange 203 75 22
    }
}

theme "solarized-osaka"

Did you check docs and existing issues?

• I have read all the solarized-osaka.nvim docs
• I have searched the existing issues of solarized-osaka.nvim
• I have searched the existing issues of plugins related to this issue

Neovim version (nvim -v)

0.9.5

Operating system/version

Sonoma 14.3.1

Describe the bug

I'm using https://github.com/craftzdog/solarized-osaka.nvim with https://github.com/lambdalisue/glyph-palette.vim.

glyph-palette.vim assumes that if g:terminal_color_0 exists, other colors exist too (color: 0-15).

With this default setup, g:terminal_color_7 and g:terminal_color_8 variables are missing because colors.terminal_black and colors.fg_dark are not set properly and they return nil on setup.

require("solarized-osaka").setup({})

I'm not sure this behavior maybe affect to other highlighting function or not.

Steps To Reproduce

Just start nvim with default solarized-osaka setup.

Expected Behavior

I think g:terminal_color_7 and g:terminal_color_8 variables should be set.

Repro

-- DO NOT change the paths and don't remove the colorscheme
local root = vim.fn.fnamemodify("./.repro", ":p")

-- set stdpaths to use .repro
for _, name in ipairs({ "config", "data", "state", "cache" }) do
  vim.env[("XDG_%s_HOME"):format(name:upper())] = root .. "/" .. name
end

-- bootstrap lazy
local lazypath = root .. "/plugins/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", lazypath, })
end
vim.opt.runtimepath:prepend(lazypath)

-- install plugins
local plugins = {
  "craftzdog/solarized-osaka.nvim",
  "lambdalisue/glyph-palette.vim",
}
require("lazy").setup(plugins, {
  root = root .. "/plugins",
})

vim.cmd.colorscheme("solarized-osaka")
-- add anything else here

Did you check docs and existing issues?

• I have read all the solarized-osaka.nvim docs
• I have searched the existing issues of solarized-osaka.nvim
• I have searched the existing issues of plugins related to this issue

Neovim version (nvim -v)

v0.10.0-dev-2543+gade1b12f4-Homebrew

Operating system/version

MacOS 14.4.1

Describe the bug

Wezterm themes are just Tokyo night copy-pasted
https://github.com/craftzdog/solarized-osaka.nvim/tree/main/extras/wezterm

Steps To Reproduce

1. Inspect the Wezterm themes
2. See metadata

Expected Behavior

That they have the actual colorscheme

Repro

-- DO NOT change the paths and don't remove the colorscheme
local root = vim.fn.fnamemodify("./.repro", ":p")

-- set stdpaths to use .repro
for _, name in ipairs({ "config", "data", "state", "cache" }) do
  vim.env[("XDG_%s_HOME"):format(name:upper())] = root .. "/" .. name
end

-- bootstrap lazy
local lazypath = root .. "/plugins/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", lazypath, })
end
vim.opt.runtimepath:prepend(lazypath)

-- install plugins
local plugins = {
  "craftzdog/solarized-osaka.nvim",
  "craftzdog/solarized-osaka.nvim",
  -- add any other plugins here
}
require("lazy").setup(plugins, {
  root = root .. "/plugins",
})

vim.cmd.colorscheme("solarized-osaka")
-- add anything else here

Did you check docs and existing issues?

• I have read all the solarized-osaka.nvim docs
• I have searched the existing issues of solarized-osaka.nvim
• I have searched the existing issues of plugins related to this issue

Neovim version (nvim -v)

0.9.2

Operating system/version

Ubuntu 22.04

Describe the bug

Hello,

TroubleNormal makes diagnostics's window from folke/trouble really weird, difficult to read, I commented the line with TroubleNormal in LspTrouble and it looks much better.

Thank you

Steps To Reproduce

Install folke/trouble.nvim and open diagnostics with :TroubleToggle

Expected Behavior

Readable LspTrouble diagnostic window by changing colors of TroubleNormal

Repro

-- DO NOT change the paths and don't remove the colorscheme
local root = vim.fn.fnamemodify("./.repro", ":p")

-- set stdpaths to use .repro
for _, name in ipairs({ "config", "data", "state", "cache" }) do
  vim.env[("XDG_%s_HOME"):format(name:upper())] = root .. "/" .. name
end

-- bootstrap lazy
local lazypath = root .. "/plugins/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", lazypath, })
end
vim.opt.runtimepath:prepend(lazypath)

-- install plugins
local plugins = {
  "folke/trouble.nvim",
  "craftzdog/solarized-osaka.nvim",
  "craftzdog/solarized-osaka.nvim",
  -- add any other plugins here
}
require("lazy").setup(plugins, {
  root = root .. "/plugins",
})

vim.cmd.colorscheme("solarized-osaka")
-- add anything else here

Did you check the docs?

• I have read all the solarized-osaka.nvim docs

Is your feature request related to a problem? Please describe.

I am using this fantastic colorscheme with Lualine and I noticed that (the diff and diagnostics status part of) b section of Lualine looks quite unpleasant:

Describe the solution you'd like

I think that we can change the normal.b.bg to make the whole thing look better. Changing foreground colors can also be done but involves more changes (e.g. setting LuaLineDiffAdd LuaLineDiffChange and LuaLineDiffDelete and changing diagnostic colors).

Describe alternatives you've considered

(None)

Additional context

No response

Did you check the docs?

• I have read all the tokyonight.nvim docs

Is your feature request related to a problem? Please describe.

Can I get the one for vscode please?

Describe the solution you'd like

Can I get the one for vscode please?

Describe alternatives you've considered

vscode and windows terminal ?? :D

Additional context

No response

Did you check docs and existing issues?

• I have read all the tokyonight.nvim docs
• I have searched the existing issues of tokyonight.nvim
• I have searched the existing issues of plugins related to this issue

Neovim version (nvim -v)

v0.9.4

Operating system/version

MacOS Ventura 13.5.2

Describe the bug

It seems like the background color is not set.

When I check the Normal highlight (which is what controls the background if I am not mistaken) i see this

:highlight Normal
Normal         xxx guifg=#9eabac

I tried this on both iTerm2 and newly installed WezTerm and had the same thing happen.
It also doesn't seem to happen with other colorschemes I have installed such as solarized (normal) and tokyonight.
The problem also exists on neovim 0.10.0 dev build

I don't know if this is an issue with my system or the colorscheme at this point. Do you have any ideas?

Steps To Reproduce

nvim -u repro.lua with the minimal configuration results in the screenshot above

Expected Behavior

The background should not be black (unless it should?)

Repro

-- DO NOT change the paths and don't remove the colorscheme
local root = vim.fn.fnamemodify("./.repro", ":p")

-- set stdpaths to use .repro
for _, name in ipairs({ "config", "data", "state", "cache" }) do
  vim.env[("XDG_%s_HOME"):format(name:upper())] = root .. "/" .. name
end

-- bootstrap lazy
local lazypath = root .. "/plugins/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", lazypath, })
end
vim.opt.runtimepath:prepend(lazypath)

-- install plugins
local plugins = {
  "craftzdog/solarized-osaka.nvim",
  -- add any other plugins here
}
require("lazy").setup(plugins, {
  root = root .. "/plugins",
})

vim.cmd.colorscheme("solarized-osaka")
-- add anything else here

Did you check docs and existing issues?

• I have read all the solarized-osaka.nvim docs
• I have searched the existing issues of solarized-osaka.nvim
• I have searched the existing issues of plugins related to this issue

Neovim version (nvim -v)

v0.9.5

Operating system/version

Arch Linux

Describe the bug

When using this color scheme in a rust file it shows an undercurl on println! like commands and other statements too

You can see here that the same issue does not reproduce if you are using Catppuccin.
The issue is also present in tokyonight.nvim so i'm currently clueless to why this is happening in these 2 themes.

Steps To Reproduce

1. create a .rs file and use println! statements.

Expected Behavior

Should not show the undercurl.

Repro

-- DO NOT change the paths and don't remove the colorscheme
local root = vim.fn.fnamemodify("./.repro", ":p")

-- set stdpaths to use .repro
for _, name in ipairs({ "config", "data", "state", "cache" }) do
  vim.env[("XDG_%s_HOME"):format(name:upper())] = root .. "/" .. name
end

-- bootstrap lazy
local lazypath = root .. "/plugins/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", lazypath, })
end
vim.opt.runtimepath:prepend(lazypath)

-- install plugins
local plugins = {
  "craftzdog/solarized-osaka.nvim",
  "craftzdog/solarized-osaka.nvim",
  -- add any other plugins here
}
require("lazy").setup(plugins, {
  root = root .. "/plugins",
})

vim.cmd.colorscheme("solarized-osaka")
-- add anything else here

I love watching your videos, and I liked using the nvim editor, although I am still a beginner, I don't know many functionalities that I can do with the editor, and I would like to download your theme but I don't know. how to do it :(. I am a Windows user, I await your prompt response if you can help me, greetings takuya

Did you check the docs?

• I have read all the tokyonight.nvim docs

Is your feature request related to a problem? Please describe.

I love the colorscheme you have created and I would love to use it but i've built a setup around mini.nvim and this colorscheme is incompatible with mini-statusline. The middle part of the statusline is completely grayed out instead of correctly displaying the filename. See screenshot.

Describe the solution you'd like

If you are interested and have the time I would be very happy if you could add compatibility for mini-statusline in this project that way i could switch over to this colorscheme permanently.

Describe alternatives you've considered

Maybe you could share a way how i could resolve this issue using the on_colors or on_highlights functionality of your plugin.

Additional context

No response

Did you check docs and existing issues?

• I have read all the solarized-osaka.nvim docs
• I have searched the existing issues of solarized-osaka.nvim
• I have searched the existing issues of plugins related to this issue

Neovim version (nvim -v)

0.9.5

Operating system/version

macOS 14.2.1 (23C71)

Describe the bug

I'm using Alacritty 0.13.1 and tmux 3.3a, with the classic 'solarized-dark' theme set up for Alacritty.

However, after installing nvim, lazy.nvim, and craftzdog/solarized-osaka.nvim, and restarting everything, my color scheme doesn't align with the colors shown in the README. Here's a screenshot for reference:

Steps To Reproduce

1. Install Alacritty 0.13.1 on macOS 14.2.1.
2. Use the following ~/.config/alacritty/alacritty.toml config file:

live_config_reload = true
working_directory = "None"

[bell]
animation = "EaseOutExpo"
color = "0xffffff"
duration = 0

[colors]
draw_bold_text_with_bright_colors = true

[colors.bright]
black = "0x002b36"
blue = "0x839496"
cyan = "0x93a1a1"
green = "0x586e75"
magenta = "0x6c71c4"
red = "0xcb4b16"
white = "0xfdf6e3"
yellow = "0x657b83"

[colors.cursor]
cursor = "0x839496"
text = "0x002b36"

[colors.normal]
black = "0x073642"
blue = "0x268bd2"
cyan = "0x2aa198"
green = "0x859900"
magenta = "0xd33682"
red = "0xdc322f"
white = "0xeee8d5"
yellow = "0xb58900"

[colors.primary]
background = "0x002b36"
foreground = "0x839496"

[colors.selection]
background = "0x073642"
text = "0x93a1a1"

[cursor]
style = "Block"
unfocused_hollow = true

[debug]
log_level = "Warn"
persistent_logging = false
print_events = false
render_timer = false

[env]
TERM = "xterm-256color"

[font]
size = 13.0

[font.bold]
family = "JetBrainsMono Nerd Font"
style = "Bold"

[font.glyph_offset]
x = 0
y = 0

[font.italic]
family = "JetBrainsMono Nerd Font"
style = "Italic"

[font.normal]
family = "JetBrainsMono Nerd Font"
style = "Regular"

[font.offset]
x = 0
y = 0

[[keyboard.bindings]]
action = "Paste"
key = "Paste"

[[keyboard.bindings]]
action = "Copy"
key = "Copy"

[[keyboard.bindings]]
action = "ClearLogNotice"
key = "L"
mods = "Control"

[[keyboard.bindings]]
chars = "\f"
key = "L"
mods = "Control"

[[keyboard.bindings]]
chars = "\u001B[1;3H"
key = "Home"
mods = "Alt"

[[keyboard.bindings]]
chars = "\u001BOH"
key = "Home"
mode = "AppCursor"

[[keyboard.bindings]]
chars = "\u001B[H"
key = "Home"
mode = "~AppCursor"

[[keyboard.bindings]]
chars = "\u001B[1;3F"
key = "End"
mods = "Alt"

[[keyboard.bindings]]
chars = "\u001BOF"
key = "End"
mode = "AppCursor"

[[keyboard.bindings]]
chars = "\u001B[F"
key = "End"
mode = "~AppCursor"

[[keyboard.bindings]]
action = "ScrollPageUp"
key = "PageUp"
mode = "~Alt"
mods = "Shift"

[[keyboard.bindings]]
chars = "\u001B[5;2~"
key = "PageUp"
mode = "Alt"
mods = "Shift"

[[keyboard.bindings]]
chars = "\u001B[5;5~"
key = "PageUp"
mods = "Control"

[[keyboard.bindings]]
chars = "\u001B[5;3~"
key = "PageUp"
mods = "Alt"

[[keyboard.bindings]]
chars = "\u001B[5~"
key = "PageUp"

[[keyboard.bindings]]
action = "ScrollPageDown"
key = "PageDown"
mode = "~Alt"
mods = "Shift"

[[keyboard.bindings]]
chars = "\u001B[6;2~"
key = "PageDown"
mode = "Alt"
mods = "Shift"

[[keyboard.bindings]]
chars = "\u001B[6;5~"
key = "PageDown"
mods = "Control"

[[keyboard.bindings]]
chars = "\u001B[6;3~"
key = "PageDown"
mods = "Alt"

[[keyboard.bindings]]
chars = "\u001B[6~"
key = "PageDown"

[[keyboard.bindings]]
chars = "\u001B[Z"
key = "Tab"
mods = "Shift"

[[keyboard.bindings]]
chars = "\u007F"
key = "Back"

[[keyboard.bindings]]
chars = "\u001B\u007F"
key = "Back"
mods = "Alt"

[[keyboard.bindings]]
chars = "\u001B[2~"
key = "Insert"

[[keyboard.bindings]]
chars = "\u001B[3~"
key = "Delete"

[[keyboard.bindings]]
chars = "\u001B[1;2D"
key = "Left"
mods = "Shift"

[[keyboard.bindings]]
chars = "\u001B[1;5D"
key = "Left"
mods = "Control"

[[keyboard.bindings]]
chars = "\u001B[1;3D"
key = "Left"
mods = "Alt"

[[keyboard.bindings]]
chars = "\u001B[D"
key = "Left"
mode = "~AppCursor"

[[keyboard.bindings]]
chars = "\u001BOD"
key = "Left"
mode = "AppCursor"

[[keyboard.bindings]]
chars = "\u001B[1;2C"
key = "Right"
mods = "Shift"

[[keyboard.bindings]]
chars = "\u001B[1;5C"
key = "Right"
mods = "Control"

[[keyboard.bindings]]
chars = "\u001B[1;3C"
key = "Right"
mods = "Alt"

[[keyboard.bindings]]
chars = "\u001B[C"
key = "Right"
mode = "~AppCursor"

[[keyboard.bindings]]
chars = "\u001BOC"
key = "Right"
mode = "AppCursor"

[[keyboard.bindings]]
chars = "\u001B[1;2A"
key = "Up"
mods = "Shift"

[[keyboard.bindings]]
chars = "\u001B[1;5A"
key = "Up"
mods = "Control"

[[keyboard.bindings]]
chars = "\u001B[1;3A"
key = "Up"
mods = "Alt"

[[keyboard.bindings]]
chars = "\u001B[A"
key = "Up"
mode = "~AppCursor"

[[keyboard.bindings]]
chars = "\u001BOA"
key = "Up"
mode = "AppCursor"

[[keyboard.bindings]]
chars = "\u001B[1;2B"
key = "Down"
mods = "Shift"

[[keyboard.bindings]]
chars = "\u001B[1;5B"
key = "Down"
mods = "Control"

[[keyboard.bindings]]
chars = "\u001B[1;3B"
key = "Down"
mods = "Alt"

[[keyboard.bindings]]
chars = "\u001B[B"
key = "Down"
mode = "~AppCursor"

[[keyboard.bindings]]
chars = "\u001BOB"
key = "Down"
mode = "AppCursor"

[[keyboard.bindings]]
chars = "\u001BOP"
key = "F1"

[[keyboard.bindings]]
chars = "\u001BOQ"
key = "F2"

[[keyboard.bindings]]
chars = "\u001BOR"
key = "F3"

[[keyboard.bindings]]
chars = "\u001BOS"
key = "F4"

[[keyboard.bindings]]
chars = "\u001B[15~"
key = "F5"

[[keyboard.bindings]]
chars = "\u001B[17~"
key = "F6"

[[keyboard.bindings]]
chars = "\u001B[18~"
key = "F7"

[[keyboard.bindings]]
chars = "\u001B[19~"
key = "F8"

[[keyboard.bindings]]
chars = "\u001B[20~"
key = "F9"

[[keyboard.bindings]]
chars = "\u001B[21~"
key = "F10"

[[keyboard.bindings]]
chars = "\u001B[23~"
key = "F11"

[[keyboard.bindings]]
chars = "\u001B[24~"
key = "F12"

[[keyboard.bindings]]
chars = "\u001B[1;2P"
key = "F1"
mods = "Shift"

[[keyboard.bindings]]
chars = "\u001B[1;2Q"
key = "F2"
mods = "Shift"

[[keyboard.bindings]]
chars = "\u001B[1;2R"
key = "F3"
mods = "Shift"

[[keyboard.bindings]]
chars = "\u001B[1;2S"
key = "F4"
mods = "Shift"

[[keyboard.bindings]]
chars = "\u001B[15;2~"
key = "F5"
mods = "Shift"

[[keyboard.bindings]]
chars = "\u001B[17;2~"
key = "F6"
mods = "Shift"

[[keyboard.bindings]]
chars = "\u001B[18;2~"
key = "F7"
mods = "Shift"

[[keyboard.bindings]]
chars = "\u001B[19;2~"
key = "F8"
mods = "Shift"

[[keyboard.bindings]]
chars = "\u001B[20;2~"
key = "F9"
mods = "Shift"

[[keyboard.bindings]]
chars = "\u001B[21;2~"
key = "F10"
mods = "Shift"

[[keyboard.bindings]]
chars = "\u001B[23;2~"
key = "F11"
mods = "Shift"

[[keyboard.bindings]]
chars = "\u001B[24;2~"
key = "F12"
mods = "Shift"

[[keyboard.bindings]]
chars = "\u001B[1;5P"
key = "F1"
mods = "Control"

[[keyboard.bindings]]
chars = "\u001B[1;5Q"
key = "F2"
mods = "Control"

[[keyboard.bindings]]
chars = "\u001B[1;5R"
key = "F3"
mods = "Control"

[[keyboard.bindings]]
chars = "\u001B[1;5S"
key = "F4"
mods = "Control"

[[keyboard.bindings]]
chars = "\u001B[15;5~"
key = "F5"
mods = "Control"

[[keyboard.bindings]]
chars = "\u001B[17;5~"
key = "F6"
mods = "Control"

[[keyboard.bindings]]
chars = "\u001B[18;5~"
key = "F7"
mods = "Control"

[[keyboard.bindings]]
chars = "\u001B[19;5~"
key = "F8"
mods = "Control"

[[keyboard.bindings]]
chars = "\u001B[20;5~"
key = "F9"
mods = "Control"

[[keyboard.bindings]]
chars = "\u001B[21;5~"
key = "F10"
mods = "Control"

[[keyboard.bindings]]
chars = "\u001B[23;5~"
key = "F11"
mods = "Control"

[[keyboard.bindings]]
chars = "\u001B[24;5~"
key = "F12"
mods = "Control"

[[keyboard.bindings]]
chars = "\u001B[1;6P"
key = "F1"
mods = "Alt"

[[keyboard.bindings]]
chars = "\u001B[1;6Q"
key = "F2"
mods = "Alt"

[[keyboard.bindings]]
chars = "\u001B[1;6R"
key = "F3"
mods = "Alt"

[[keyboard.bindings]]
chars = "\u001B[1;6S"
key = "F4"
mods = "Alt"

[[keyboard.bindings]]
chars = "\u001B[15;6~"
key = "F5"
mods = "Alt"

[[keyboard.bindings]]
chars = "\u001B[17;6~"
key = "F6"
mods = "Alt"

[[keyboard.bindings]]
chars = "\u001B[18;6~"
key = "F7"
mods = "Alt"

[[keyboard.bindings]]
chars = "\u001B[19;6~"
key = "F8"
mods = "Alt"

[[keyboard.bindings]]
chars = "\u001B[20;6~"
key = "F9"
mods = "Alt"

[[keyboard.bindings]]
chars = "\u001B[21;6~"
key = "F10"
mods = "Alt"

[[keyboard.bindings]]
chars = "\u001B[23;6~"
key = "F11"
mods = "Alt"

[[keyboard.bindings]]
chars = "\u001B[24;6~"
key = "F12"
mods = "Alt"

[[keyboard.bindings]]
chars = "\u001B[1;3P"
key = "F1"
mods = "Super"

[[keyboard.bindings]]
chars = "\u001B[1;3Q"
key = "F2"
mods = "Super"

[[keyboard.bindings]]
chars = "\u001B[1;3R"
key = "F3"
mods = "Super"

[[keyboard.bindings]]
chars = "\u001B[1;3S"
key = "F4"
mods = "Super"

[[keyboard.bindings]]
chars = "\u001B[15;3~"
key = "F5"
mods = "Super"

[[keyboard.bindings]]
chars = "\u001B[17;3~"
key = "F6"
mods = "Super"

[[keyboard.bindings]]
chars = "\u001B[18;3~"
key = "F7"
mods = "Super"

[[keyboard.bindings]]
chars = "\u001B[19;3~"
key = "F8"
mods = "Super"

[[keyboard.bindings]]
chars = "\u001B[20;3~"
key = "F9"
mods = "Super"

[[keyboard.bindings]]
chars = "\u001B[21;3~"
key = "F10"
mods = "Super"

[[keyboard.bindings]]
chars = "\u001B[23;3~"
key = "F11"
mods = "Super"

[[keyboard.bindings]]
chars = "\u001B[24;3~"
key = "F12"
mods = "Super"

[[keyboard.bindings]]
chars = """

"""
key = "NumpadEnter"

[[keyboard.bindings]]
chars = "\u001Bf"
key = "F"
mods = "Alt"

[[keyboard.bindings]]
chars = "\u001Bb"
key = "B"
mods = "Alt"

[[keyboard.bindings]]
chars = "\u001Bd"
key = "D"
mods = "Alt"

[[keyboard.bindings]]
key = "N"
mods = "Command"

[keyboard.bindings.command]
args = ["-n", "/Applications/Alacritty.app"]
program = "open"

[mouse]
hide_when_typing = true

[[mouse.bindings]]
action = "PasteSelection"
mouse = "Middle"

[scrolling]
history = 0
multiplier = 3

[selection]
save_to_clipboard = true
semantic_escape_chars = ",│`|:\"' ()[]{}<>"

[window]
decorations = "full"
dynamic_padding = true
startup_mode = "Windowed"

[window.dimensions]
columns = 0
lines = 0

[window.padding]
x = 0
y = 0

3. Install nvim 0.9.5.
4. Install lazy.nvim plugin.
5. Use the following ~/.config/nvim/init.lua config file:

require('lazy').setup({
  -- List your plugins here
  {'tpope/vim-unimpaired'},
  {'junegunn/fzf'},
  {
    "craftzdog/solarized-osaka.nvim",
    lazy = false,
    priority = 1000,
    opts = function()
      return {
        transparent = true,
      } 
    end,
  }
})

-- Redefine leader key
vim.g.mapleader = " "

-- Custom keybindings
vim.api.nvim_set_keymap('n', '<Leader>w', ':w<CR>', { noremap = true, silent = true })
vim.api.nvim_set_keymap('n', '<Leader>s', ':source ~/.config/nvim/init.lua<CR>', { noremap = true, silent = true })
vim.api.nvim_set_keymap('n', '<Leader>d', ':bd<CR>', { noremap = true, silent = true })
-- remove trailing whitespaces automatically
vim.api.nvim_set_keymap('n', '<Leader>x', ':%s/\\s\\+$//e<CR>', { noremap = true, silent = true })
vim.api.nvim_set_keymap('n', '~', ':buffers<CR>', { noremap = true, silent = true })

-- Configure fzf plugin
vim.api.nvim_set_keymap('n', '<Leader>f', ':FZF<CR>', { noremap = true, silent = true })

-- Make buffer cycling much more effective
vim.api.nvim_set_keymap('n', '<C-K>', ':bprev<CR>', { noremap = true, silent = true })
vim.api.nvim_set_keymap('n', '<C-J>', ':bnext<CR>', { noremap = true, silent = true })

-- Set numbering
vim.wo.number = true

-- Search settings
vim.o.hlsearch = true
vim.o.incsearch = true

-- Set the number of spaces that a <Tab> in the file counts for
vim.opt.tabstop = 2

-- Set the number of spaces to use for each step of (auto)indent
vim.opt.shiftwidth = 2

-- Use spaces instead of tabs
vim.opt.expandtab = true

-- Optionally, set the number of spaces for a tab when editing
vim.opt.softtabstop = 2

-- Enable true color (24-bit color) support
vim.opt.termguicolors = true

-- Run plugins
vim.cmd[[colorscheme solarized-osaka]]

Expected Behavior

Colors must align with those depicted in the README. The bottom line in nvim should display a discernible background.

Repro

-- DO NOT change the paths and don't remove the colorscheme
local root = vim.fn.fnamemodify("./.repro", ":p")

-- set stdpaths to use .repro
for _, name in ipairs({ "config", "data", "state", "cache" }) do
  vim.env[("XDG_%s_HOME"):format(name:upper())] = root .. "/" .. name
end

-- bootstrap lazy
local lazypath = root .. "/plugins/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", lazypath, })
end
vim.opt.runtimepath:prepend(lazypath)

-- install plugins
local plugins = {
  "craftzdog/solarized-osaka.nvim",
  "craftzdog/solarized-osaka.nvim",
  -- add any other plugins here
}
require("lazy").setup(plugins, {
  root = root .. "/plugins",
})

vim.cmd.colorscheme("solarized-osaka")
-- add anything else here

Did you check docs and existing issues?

• I have read all the tokyonight.nvim docs
• I have searched the existing issues of tokyonight.nvim
• I have searched the existing issues of plugins related to this issue

Neovim version (nvim -v)

v0.10.0-dev-1811+gc95b9a32f

Operating system/version

Ubuntu 22.04

Describe the bug

I could verify that this problem occurs with or without tmux, on both Terminal and Alacritty.
I have true colors in the terminal.

I haven't modified the colorscheme config

return {
  "craftzdog/solarized-osaka.nvim",
  lazy = true,
  priority = 1000,
  opts = function()
    return {
      transparent = true,
    }
  end,
}

Steps To Reproduce

Install LazyVim with your beautiful video.

Expected Behavior

The text-on-bg should be readable

Repro

No response

Did you check the docs?

• I have read all the solarized-osaka.nvim docs

Is your feature request related to a problem? Please describe.

I only use 2 themes in neovim which is this one and tokyonight.nvim and i noticed that tokyonight provides a little more differentiation and highlighting for some tags which do not reciprocate in solarized-osaka and also this theme has some bad highlighting when it comes to markdown.
One more thing i wanted to add is if it will have some good support working with flash.nvim as the colors do not match when using it and it is very difficult to differentiate when using it.

Describe the solution you'd like

I would like this to also have that same highlighting as it helps a lot in visually differentiating between tags.

• A soft example is given below:

This is the solarized-osaka where the components that are being imported and used are not differentiating in color from the other basic html tags whereas if we check this in tokyonight:

This shows a clear difference between those tags.
This was created from a fork of Tokyonight so implementing those features should not be too difficult as it just needs a value of a different color for that treesitter object as far as i can think.

Describe alternatives you've considered

Currently it seems that only Tokyonight has this implemented and i did check it on gruvbox and catppuccin and they show the same behavior.

Additional context

No response

Did you check docs and existing issues?

• I have read all the solarized-osaka.nvim docs
• I have searched the existing issues of solarized-osaka.nvim
• I have searched the existing issues of plugins related to this issue

Neovim version (nvim -v)

0.9.5

Operating system/version

MacOS 14.3.1

Describe the bug

https://github.com/craftzdog/solarized-osaka.nvim/blob/main/extras/tmux/solarized-osaka_night.tmux (as an example) still seems to have the tokyo night colors in it. I see the lua function to generate a config file, but I'm not sure how to call it

Steps To Reproduce

See above

Expected Behavior

expected: tmux uses solarized-osaka colors

Repro

-- DO NOT change the paths and don't remove the colorscheme
local root = vim.fn.fnamemodify("./.repro", ":p")

-- set stdpaths to use .repro
for _, name in ipairs({ "config", "data", "state", "cache" }) do
  vim.env[("XDG_%s_HOME"):format(name:upper())] = root .. "/" .. name
end

-- bootstrap lazy
local lazypath = root .. "/plugins/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", lazypath, })
end
vim.opt.runtimepath:prepend(lazypath)

-- install plugins
local plugins = {
  "craftzdog/solarized-osaka.nvim",
  "craftzdog/solarized-osaka.nvim",
  -- add any other plugins here
}
require("lazy").setup(plugins, {
  root = root .. "/plugins",
})

vim.cmd.colorscheme("solarized-osaka")
-- add anything else here

When using this theme, you may occasionally encounter situations where the background is white and the content cannot be seen clearly.

Did you check docs and existing issues?

• I have read all the solarized-osaka.nvim docs
• I have searched the existing issues of solarized-osaka.nvim
• I have searched the existing issues of plugins related to this issue

Neovim version (nvim -v)

Operating system/version

Describe the bug

Your apache 2.0 license doesn't look completed. It appears that you have forgotten to include your name and the year for the license on Line 189.

Steps To Reproduce

none

Expected Behavior

The section [yyyy] [name of copyright owner] should be replaced with the appropriate information.

Repro

none