Iron-E / nvim-highlite

A colorscheme generator that is "lite" on logic for the developer.
Other
240 stars 33 forks source link

Export to wezterm does not work #32

Closed damanis closed 2 months ago

damanis commented 3 months ago

The call lua require('highlite.export').wezterm('everforest') causes error. Export to bat, for example, works properly.

Iron-E commented 3 months ago

Thank you for the report! I'll take a look at this tomorrow.

Iron-E commented 3 months ago

Odd, it seems my version of Neovim doesn't even have everforest. If I change it to default, though, it seems to work for me

damanis commented 3 months ago

Everforest for neovim But same problem with other themes, for example, Nightfox. Same themes are exported to bat by nvim-highlite without problem. The error: image

Iron-E commented 3 months ago

Thank you for the links, I'll check this out further

Iron-E commented 3 months ago

I wasn't able to reproduce with everforest; could you share your Neovim version and/or config?

damanis commented 3 months ago

I tested both on neovim 0.10.0 and nightly build. Configuration in lazy:

  {'Iron-E/nvim-highlite',
    enabled = true,
    lazy = true,
    priority = math.huge,
    -- version = '^4.0.0',
    config = function(_, opts)
      -- OPTIONAL: setup the plugin. See "Configuration" for information
      require('highlite').setup {generator = {plugins = {vim = false}, syntax = false}}
    end,
  },

In lazy-lock.json:

"nvim-highlite": { "branch": "master-v4", "commit": "83a6fcc41eb55db93eee37199600b547638d3a28" },
Iron-E commented 3 months ago

I couldn't reproduce the issue, but I do think that I know what the problem is. Could you try #33 to see if the error goes away?

damanis commented 3 months ago

@Iron-E Yes, with dir argument export to wezterm works. Note. Export to vim, for example, does not require dir argument, nvim-highlite creates output folder itself.