Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

E539: Illegal character <,> #1201

Open
rickalex21 opened this issue Feb 29, 2024 · 3 comments
Open

E539: Illegal character <,> #1201

rickalex21 opened this issue Feb 29, 2024 · 3 comments
Labels
bug Something isn't working

Comments

@rickalex21
Copy link

rickalex21 commented Feb 29, 2024

Self Checks

  • [X ] I'm using the latest lualine.
  • [X ] I didn't find the issue in existing issues or PRs.

How to reproduce the problem

Using fzf.vim with ripgrep when this line of code is in the config causes the error.
The commented out line does not cause the error:

" let spec = {'options': ['--phony', '--query', query, '--bind', 'change:reload:'.reload_command]}
	let spec = {'options': ['--preview-window','up,75%,border-bottom,+{2}+3/3,~3','--phony', '--query', query, '--bind', 'change:reload:'.reload_command]}
	call fzf#vim#grep(initial_command, 1, fzf#vim#with_preview(spec), fullscreen)

Expected behaviour

No errors

Actual behaviour

It's giving an error about a comma. Not sure what lualine has to do with fzf?
A lot of it mentions nvim_win_set_option and vim.schedule.

Error executing vim.schedule lua callback: ...vim/plugged/lualine.nvim/lua/lualine/utils/nvim_opts.lua:77: E539: Illegal character <,>             
stack traceback:                                                                                                                                   
        [C]: in function 'nvim_win_set_option'                                                                                                     
        ...vim/plugged/lualine.nvim/lua/lualine/utils/nvim_opts.lua:77: in function 'setter_fn'                                                    
        ...vim/plugged/lualine.nvim/lua/lualine/utils/nvim_opts.lua:50: in function 'set_opt'                                                      
        ...vim/plugged/lualine.nvim/lua/lualine/utils/nvim_opts.lua:74: in function 'set'                                                          
        ...itchie/.config/nvim/plugged/lualine.nvim/lua/lualine.lua:432: in function 'refresh'                                                     
        ...itchie/.config/nvim/plugged/lualine.nvim/lua/lualine.lua:353: in function <...itchie/.config/nvim/plugged/lualine.nvim/lua/lualine.lua:3
52>                           
Press ENTER or type command to continue                                                                                                            
Error executing vim.schedule lua callback: ...vim/plugged/lualine.nvim/lua/lualine/utils/nvim_opts.lua:77: E539: Illegal character <,>             
stack traceback:                                                                                                                                   
        [C]: in function 'nvim_win_set_option'                                                                                                     
        ...vim/plugged/lualine.nvim/lua/lualine/utils/nvim_opts.lua:77: in function 'setter_fn'                                                    
        ...vim/plugged/lualine.nvim/lua/lualine/utils/nvim_opts.lua:50: in function 'set_opt'                                                      
        ...vim/plugged/lualine.nvim/lua/lualine/utils/nvim_opts.lua:74: in function 'set'                                                          
        ...itchie/.config/nvim/plugged/lualine.nvim/lua/lualine.lua:432: in function 'refresh'                                                     
        ...itchie/.config/nvim/plugged/lualine.nvim/lua/lualine.lua:353: in function <...itchie/.config/nvim/plugged/lualine.nvim/lua/lualine.lua:3
52>    
@rickalex21 rickalex21 added the bug Something isn't working label Feb 29, 2024
@sudomyju
Copy link

sudomyju commented Mar 12, 2024

I don't use fzf, but I have the bug as well, it started to pop up after configuring in bufferline.nvim to second lualine.

This is the usual pattern in logs after the lualine become absolutely useless ...

Error executing vim.schedule lua callback: ...e/nvim/lazy/lualine.nvim/lua/lualine/utils/nvim_opts.lua:77: E539: Illegal character < >
stack traceback:
        [C]: in function 'nvim_win_set_option'
        ...e/nvim/lazy/lualine.nvim/lua/lualine/utils/nvim_opts.lua:77: in function 'setter_fn'
        ...e/nvim/lazy/lualine.nvim/lua/lualine/utils/nvim_opts.lua:50: in function 'set_opt'
        ...e/nvim/lazy/lualine.nvim/lua/lualine/utils/nvim_opts.lua:74: in function 'set'
        ...e/su/.local/share/nvim/lazy/lualine.nvim/lua/lualine.lua:432: in function 'refresh'
        ...e/su/.local/share/nvim/lazy/lualine.nvim/lua/lualine.lua:353: in function <...e/su/.local/share/nvim/lazy/lualine.nvim/lua/lualine.lua:352>
Error executing vim.schedule lua callback: ...share/nvim/lazy/lualine.nvim/lua/lualine/utils/utils.lua:211: lualine: Failed to refresh statusline:
...e/nvim/lazy/lualine.nvim/lua/lualine/utils/nvim_opts.lua:77: E539: Illegal character < >
stack traceback:
        [C]: in function 'error'
        ...share/nvim/lazy/lualine.nvim/lua/lualine/utils/utils.lua:211: in function ''
        vim/_editor.lua: in function <vim/_editor.lua:0>

@sudomyju
Copy link

is there some way to restart lualine and perhaps some easy way to debug it?

@LordMZTE
Copy link

LordMZTE commented Apr 26, 2024

I also managed to reproduce this with a custom component, but it's not consistent unfortunately. I'm unsure what exactly causes it.

Update: I've found out that this is caused by an invalid percent escape sequence such as %, being returned by a component. This means that I believe this to be a bug in the implementation of the respective component.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

3 participants