xclip VS dust

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

Try using dust https://github.com/bootandy/dust

Folks open to using gdu might like to try dust (6k stars), or even erdtree (1.4k stars) which is too recent to show up on lists like this and still a bit behind on stars. A lot of people seem to use starship (33k stars) though I'm personally oldschool on prompts. There are many other items on that list I'm not motivated to check.

The first thought I had was to use rayon for this. And looking at some prior art that does pretty much the exact same thing, it does indeed use rayon.

The dust CLI command (made with Rust) can do this too.

How does this compare to dust?

Happened to me this morning, something filled up my drive in minutes. I used dust[1] to look for large files while it was happening but knowing what was doing it would've been a big help.

[1] https://github.com/bootandy/dust

dust is also really nice.