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

running shell: exit status 134 #6

Open
MichaelC001 opened this issue Dec 17, 2023 · 3 comments
Open

running shell: exit status 134 #6

MichaelC001 opened this issue Dec 17, 2023 · 3 comments

Comments

@MichaelC001
Copy link

MichaelC001 commented Dec 17, 2023

CleanShot_2023_12_17_135003

This plugin is great, I use it to sync Neovim register and system clipboard even over SSH, and it works perfectly.
but I have a little problem with it

I use LF file manager in a terminal. every time I finish editing a text file with Neovim, it says "running shell: exit status 134"
I'm pretty sure this is caused by deferred-clipboard.nvim
How to hide this annoying message?

@EtiamNullam
Copy link
Owner

Thank you, I'm glad the plugin is helpful for you.

The issue might be related to the problem in the core, when hooking up to VimLeave or VimLeavePre - which I do in this plugin:

neovim/neovim#21856

Is the message about the exit code displayed every single time?

You might try branch fix/prevent-exitcode-134 to see if it will fix the problem. Seems like you're using lazy.nvim, so I believe adding this will work for you:

branch = 'fix/prevent-exitcode-134',

I will also link here the related issue you've raised on your file manager's repository:

gokcehan/lf#1550

@MichaelC001
Copy link
Author

MichaelC001 commented Dec 19, 2023

c1004468-290e-4c29-90a4-8d9ddcfc08f3
I am new to Neovim, I am not sure if I switch branch ccorrectly. With the config above:
"running shell: exit status", error message no longer shown.
copy and paste in tmux, works good locally, not work in SSH.
Thank you.

@EtiamNullam
Copy link
Owner

Thank you for the information. Yes, I believe you've switched it properly. You can also run :Lazy update deferred-clipboard.nvim to be sure.

This will probably be fixed at some point in the neovim's core, but let's find a good workaround for now and put it as an configuration option. I will prepare another branch for you to test with a slightly different solution.

I will let you know when the branch with an alternative solution is ready.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants