dragon VS bottom

https://www.reddit.com/r/suckless/comments/13hr5zy/comment/jmlxizk https://github.com/mwh/dragon

https://github.com/mwh/dragon https://github.com/nik012003/ripdrag

Have a look at dragon

I write a lot of extremely simple but handy shell functions.

This one lets me drag/and drop things out of a terminal session (kind of) into applications with https://github.com/mwh/dragon and i use it way too often!

I'm used on a terminal workflow (ranger fm in the past, switched to lf) on a desktopless wm. I prefer it that way, the only thing missing is drag 'n' drop functionality, mainly for web apps. There is dragon but I'm considering installing a light gui fm for the job.

Yeah, some amount of extra explanation would have helped. I'm using this with a local program (https://github.com/mwh/dragon) that creates a pop-up GUI window (independent of Emacs) for "drag and drop" functionality. It only works with files on the local system, so the purpose of super-buffer-file is to create a local file associated with a buffer if one doesn't already exist, and return the name of that file.

Not a direct answer, but maybe still useful… They way I handle this is using a drag and drop tool.

I know there is dragon and the feature would require a terminal that supports it, but being able to simply select files and drag-and-drop them into a browser upload without requiring an additional window would be awesome.

You can use Dragon

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.