Proton-Caller VS xclip

Since I couldn't get get with Proton 8 to work with Proton-Caller, I went with this standalone script:

Yeah pretty much. Check out Proton Caller: https://github.com/caverym/proton-caller

It's funny, I spent the time to get a windows app launching in proton as I was having some issues with the Linux version that I didn't have the time/patience to diagnose and fix myself.

The launcher is called proton-call ... I changed Steam to use the version of proton to match what the app expected, and it worked pretty cleanly. All said, I do wish it were easier for a separate launcher or third party to include proton as a separate package.

https://github.com/caverym/proton-caller

This tool can be installed through package manager in any Debian and Arch based distros. Also, it can be manually built and complied from source code. (here's the github link if you want to check it now: https://github.com/caverym/Proton-Caller/)

Run it through proton-caller instead of steam itself

As someone who owns a crap ton of games, Proton-GE works for every single game that are supposed to be working on Linux for me. I use it in conjunction with proton-caller, they just work. Not sure where this things are likely to break in subtle ways comes from.

Proton is not inseparably tied to Steam; you can easily run it outside that environment, and projects like proton-caller make it dead simple.

proton-caller https://github.com/caverym/proton-caller

i use proton-caller and find it easier to manage non-steam games that way. heroic game launcher and bottles should be easier though.

Yes it is. But it's not recommended.

I find it so annoying that these only work with plain text and RTF. On X11 there is `xclip`[0] and on Wayland there is `wl-clipboard`[1] both of which support binary file formats either through parsing the header or explicitly setting the MIME type.

This means you can do things like copy an image from the terminal and paste it into a graphical program like a browser or chat client and vice-versa. Also can be very useful in shell scripts for desktop automation.

The workaround on MacOS is to use AppleScript via `osascript` to `set the clipboard to...`.

[0] https://github.com/astrand/xclip

This reminds me of xclip.

I haven't used it in a while but xclip is a thing for X11 and you can create your own keyboard shortcuts and present a window with zenity or something.

This is apparently an issue with xclip, not Neovim: https://github.com/astrand/xclip/issues/38

Lately I've become a big fan of Micro. It's as portable as Nano. By default it uses the same shortcuts as typical desktop programs: Ctrl-S for save, Ctrl-Q for quit, Ctrl-C/Ctrl-V for copy/paste, etc. It integrates well with Linux desktops' clipboards by optionally using xclip. Just like Nano, it can have multiple files open for easy copy/pasting between files. But the best thing of all is that its scripting/plugin system is plain old Lua 5.1.

Requires: xclip

> How do you select text in your virtual terminal with the keyboard?

with xsel(1x) or xclip(1)

https://github.com/kfish/xsel

https://github.com/astrand/xclip