xclip VS bottom

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

bottom

I'd suggest Bottom as a TUI alternative to the in-built task managers - https://github.com/ClementTsang/bottom

It works on Windows also.

If anyone is looking for a "top" like, written in Rust, might have a look at https://github.com/ClementTsang/bottom

Looks like bottom with another theme

bottom - A cross-platform graphical process/system monitor with a customizable interface and a multitude of features.

As a macOS user, it boils my brain whenever I've to type in something like ~/Library/Application Support/org.rust-lang.Cargo/config.toml. macOS users have been begging CLI tools to support XDG variables on macOS too. Setting defaults is a strong indication to the community what should be the "preferred" locations. The defaults defined in your article will invariably lead to some authors saying that if that path is good enough for cargo, then it is good enough for their tool. Even the latest draft RFC acknowledges that macOS should use XDG variables too. I've written more about this here.