dragon VS fish-shell

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

Reminds of the note at the bottom of Fish's releases. It's there because the build system cannot determine the current version for some reason. Hopefully that will go away now that they have switched to a different language / build system. The custom tarball is used by Arch Linux at the very least.

https://github.com/fish-shell/fish-shell/releases/tag/3.7.1

https://github.com/fish-shell/fish-shell/issues/7772#issueco...

https://gitlab.archlinux.org/archlinux/packaging/packages/fi...

A recent practical example of the former: the fish shell re-wrote incrementally from C++ to Rust, and is almost finished https://github.com/fish-shell/fish-shell/discussions/10123

An example of the latter: c2rust, which is a work in progress but is very impressive https://github.com/immunant/c2rust

It currently translates into unsafe Rust, but the strategy is to separate the "compile C to unsafe Rust" steps and the "compile unsafe Rust to safe Rust" steps. As I see it, as it makes the overall task simpler, allows for more user freedom, and makes the latter potentially useful even for non-transpiled code. https://immunant.com/blog/2023/03/lifting/

And this discussion from November has an update on the progress: https://github.com/fish-shell/fish-shell/discussions/10123

We're using bash as our terminal shell for now (it is standard in many distros) but it is not the only one out there. If you want to test out zsh, fish or oh-my-zsh, you will see that there are a few differences and the features are usually the main differentiator. Try that, poke around.

They have a variety of reasons to move to rust, as outlined in their original rust discussion[1]. Mostly around finding other contributors, and adding an async/parallel mode they're comfortable with.

[1] https://github.com/fish-shell/fish-shell/pull/9512