vimpostor / vim-tpipeline

Embed your vim statusline in tmux
GNU General Public License v3.0
369 stars 11 forks source link

Build hook failure on first install #47

Closed guruor closed 1 year ago

guruor commented 1 year ago

Describe the bug

Just installed the plugin and seeing this build hook failure error, not sure what is the impact of this, re-running the vim doesn't show any of these:

Error detected while processing function <SNR>6_nvim_cb[1]..<SNR>6_job_cb[4]..<SNR>6_job_exit_cb[4]..<SNR>6_tick[6]..<SNR>6_update_finish[56]..<SNR>6_finish[9]
..plug#end[89]..<SNR>6_reload_plugins[2]..<SNR>6_load_plugin[1]..<SNR>6_source[4]..script /Users/govind.r/.config/nvim/plugged/vim-tpipeline/plugin/tpipeline.v
im[6]..function tpipeline#initialize[53]..tpipeline#init_statusline[2]..tpipeline#build_hooks:
line    9:
E121: Undefined variable: s:has_modechgd

Post hitting any key on error, seeing this:

Error detected while processing CursorHold Autocommands for "*"..function tpipeline#update:
line   34:
E121: Undefined variable: s:channel

To reproduce

Clean installed the plugin

Expected behavior

Should install without any error

Terminal emulator

kitty

Debug output

{'right': [''], 'native_str': ' COMMAND   TRADXP-442-instant-offer-fee-out-api   3  15                                                              utf-8
     python  70%  349:75 ', 'version_info': '{   api_compatible = 0,   api_level = 11,   api_prerelease = true,   major = 0,   minor = 9,   patch = 0,
prerelease = true }', 'tmux': 'tmux 3.3a', 'left': [''], 'plugin_version': '1.0', 'native_highlights': [{'group': 'lualine_a_command', 'start': 0}, {'group': '
lualine_transitional_lualine_a_command_to_lualine_b_command', 'start': 9}, {'group': 'lualine_b_command', 'start': 12}, {'group': 'lualine_b_command', 'start':
 57}, {'group': 'lualine_b_diagnostics_error_command', 'start': 57}, {'group': 'lualine_b_diagnostics_warn_command', 'start': 64}, {'group': 'lualine_transitio
nal_lualine_b_diagnostics_warn_command_to_lualine_c_command', 'start': 71}, {'group': 'lualine_c_command', 'start': 74}, {'group': 'lualine_c_command', 'start'
: 134}, {'group': 'lualine_c_command', 'start': 144}, {'group': 'lualine_x_filetype_DevIconPy_command', 'start': 152}, {'group': 'lualine_c_command', 'start':
156}, {'group': 'lualine_transitional_lualine_b_command_to_lualine_c_command', 'start': 164}, {'group': 'lualine_b_command', 'start': 167}, {'group': 'lualine_
transitional_lualine_a_command_to_lualine_b_command', 'start': 172}, {'group': 'lualine_a_command', 'start': 175}], 'os': 'MacOS', 'brand': 'neovim'}
vimpostor commented 1 year ago

Which plugin manager do you use? The error you are seeing, shouldn't appear again if you close vim and start it again.

To fix the error message on install, I need to figure out how your plugin manager hot reloads plugins on install.

guruor commented 1 year ago

re-running the vim doesn't show any of these:

Post restart it worked as mentioned above. This issue is not a blocker, just created it to understand what is causing this.

@vimpostor I am using vim-plug

vimpostor commented 1 year ago

Thanks for reporting, this warning during first install should be fixed now.

guruor commented 1 year ago

Still seeing some error, now it is not the same error:

Error detected while processing function <SNR>5_nvim_cb[1]..<SNR>5_job_cb[4]..<SNR>5_job_exit_cb[4]..<SNR>5_tick[6]..<SNR>5_update_finish[56]..<SNR>5_finish[9]
..plug#end[89]..<SNR>5_reload_plugins[2]..<SNR>5_load_plugin[1]..<SNR>5_source[4]..script /Users/govind.r/.config/nvim/plugged/vim-tpipeline/plugin/tpipeline.v
im[6]..function tpipeline#initialize[78]..tpipeline#init_statusline[22]..tpipeline#update:
line    2:
E5108: Error executing lua ...config/nvim/plugged/vim-tpipeline/lua/tpipeline/main.lua:1: attempt to concatenate field 'tpipeline_fillchar' (a nil value)
stack traceback:
        ...config/nvim/plugged/vim-tpipeline/lua/tpipeline/main.lua:1: in main chunk
        [C]: in function 'require'
        [string "luaeval()"]:1: in main chunk
guruor commented 1 year ago

Verified, it is no longer an issue. Thanks for quick fix.