Asa Jay

Chiming in... @wellle do you know https://github.com/justinmk/TextObjectify ? Your plugin is very similar, but each of you have exclusive features. I tell this to you, because I don't understand why...

I will adress this in the future with a variable like f.e. `visual_select_high_contrast', when I've decided how to implement options in general.

I witnessed the same today and have some further input: - First time I started CopyQ in the session of the installation it worked just fine! - Next day after...

If you supply the vimrc lines for the default ; and , keys then it will be fine I guess!

As per documentation, I've added the extra configs to make the most of emacs/vterm integration by adding these lines to my zshrc: ``` if [[ "$INSIDE_EMACS" = 'vterm' ]] \...

I was thinking of copy & pasting as well. But I like the idea of getting upstream changes to this file on updating vterm, that's why I was thinking towards...

Came across the same issue. This is due to the fact that you are using flatpak - it runs VGrive in a container which doesn't have access to this part...

I can confirm that deleting the "rnnlm" folder resulted in a considerable decrease of "the" errors, but they're not entirely gone.

Forgot to mention, I was using 0.4.8 downloaded 2016.07.30 from https://mridgers.github.io/clink/ on both Win 7 and Win 10. I think this is a different issue then.

I can confirm `pip install -U transformers` fixed this issue for me. Had v4.24 running before. @sweetramen whats your transformers version? ``` $ pip show transformers Name: transformers Version: 4.37.2...