help setting up an auto update lualine feature

[brunobmello25]

Trying to setup an update function to update lualine on theme change. Something like this:

_G.UpdateLualine = function()
  local themery = require 'themery'
  local currentTheme = themery.getCurrentTheme()

  require('lualine').setup { options = { theme = currentTheme and currentTheme.name or 'tokyonight' } }
end

return {
  {
    'zaldih/themery.nvim',
    lazy = false,
    priority = 1000,
    dependencies = {
      { 'ellisonleao/gruvbox.nvim' },
      { 'folke/tokyonight.nvim' },
    },
    config = function()
      require('themery').setup {
        themes = { 'tokyonight', 'gruvbox' },
        globalAfter = [[lua UpdateLualine()]],
      }
    end,
  },
}

but for some reason this function is not being called, either because it's not recognized inside this scope, or some other reason. any tips on how to make this work?

[zaldih]

Hi Bruno, sorry for the delay.

I have been studying it and I have noticed two things:

1. the function is executed already in the context of lua, so lua is not required and as it is a global function, add _G. prefix:

globalAfter = [[ _G.UpdateLualine() ]],

2. You have discovered a bug! I didn't have 100% implemented globalAfter and globalBefore, so it wouldn't be called when previewing themes. I have fixed this.

Try updating the plugin and updating your config. If you still have problems, let me know.

[brunobmello25]

Hi @zaldih! No problem at all! Thanks for the response

I tried updating the plugin and then adjusting the globalAfter key, but then I got some strange behaviour where the theme picker will lag when I try switching themes. Additionally, after setting up a globalAfter and then commenting it again, it appears to remain cached on the plugin somehow.

I'll give you the steps to reproduce:

1. checkout my dotfiles on this commit hash use it as your config
   1.b. Or, if you prefer, you can just use these contents to set up the plugin:

_G.UpdateLualine = function()
  local themery = require 'themery'
  local currentTheme = themery.getCurrentTheme()

  require('lualine').setup { options = { theme = currentTheme and currentTheme.name or 'tokyonight' } }
end

return {
  {
    'zaldih/themery.nvim',
    lazy = false,
    priority = 1000,
    dependencies = {
      { 'ellisonleao/gruvbox.nvim' },
      { 'folke/tokyonight.nvim' },
      { 'rose-pine/neovim', name = 'rose-pine' },
      { 'catppuccin/nvim', name = 'catppuccin' },
      { 'Mofiqul/dracula.nvim' },
      { 'shaunsingh/nord.nvim' },
      { 'ishan9299/nvim-solarized-lua' },
      { 'navarasu/onedark.nvim' },
      { 'EdenEast/nightfox.nvim' },
      { 'sainnhe/everforest' },
      { 'sainnhe/sonokai' },
      { 'sainnhe/edge' },
    },
    config = function()
      require('themery').setup {
        themes = {
          'tokyonight',
          'gruvbox',
          'rose-pine',
          'dracula',
          'dracula-soft',
          'nord',
          'solarized',
          'onedark',
          'nightfox',
          'catppuccin-frappe',
          'catppuccin-macchiato',
          'catppuccin-mocha',
          'catppuccin-latte',
          'everforest',
          'sonokai',
          'edge',
        },
        -- globalAfter = [[ _G.UpdateLualine() ]],
      }
    end,
  },
}

3. open the file lua/plugins/colors.lua
4. see that the globalAfter is commented. Keep it like this for now
5. test :Themery and see that it changes themes normally. Run :lua UpdateLualine() and see that this function also updates lualine theme normally
6. uncomment the globalAfter line, restart editor and try :Themery again. See that it hangs and gives a weird behaviour when trying to change themes
7. comment globalAfter line again and restart neovim
8. open neovim, see this error:

Failed to run `config` for themery.nvim
/Users/bruno.mello/.config/nvim/lua/plugins/colors.lua:2: loop or previous error loading module 'themery'
# stacktrace:
  - ~/.config/nvim/lua/plugins/colors.lua:2 _in_ **UpdateLualine**
  - _G.UpdateLualine() :1 _in_ **fn**
  - /themery.nvim/lua/themery/persistence.lua:58 _in_ **execute**
  - /themery.nvim/lua/themery/persistence.lua:91 _in_ **loadState**
  - /themery.nvim/lua/themery/controller.lua:255 _in_ **bootstrap**
  - /themery.nvim/lua/themery/init.lua:7
  - ~/.config/nvim/lua/plugins/colors.lua:28 _in_ **config**
  - ~/.config/nvim/lua/plugins.lua:1
  - init.lua:12
Failed to run `config` for lualine.nvim
/Users/bruno.mello/.config/nvim/lua/plugins/lualine.lua:10: loop or previous error loading module 'themery'
# stacktrace:
  - ~/.config/nvim/lua/plugins/lualine.lua:10 _in_ **config**
  - ~/.config/nvim/lua/plugins.lua:1
  - init.lua:12

here is a video showcasing these steps:

Screen.Recording.2025-01-02.at.11.10.16.mov

[zaldih]

Thank you so much for your time in sharing all the details. I'm going to keep an eye on it these days!

Regarding the cache, indeed Themery saves the code in the ~/.local/share/nvim/themery/state.json file and keeps it updated with the config, but it is something I would like to re-do to make it more robust, because sometimes if something fails (as it is the case) it might not load the rest of the plugins until the file is deleted, and themery will fail updating itselve.

[brunobmello25]

no problem at all! let me know if there is something else I can do to help