description: `che` is a modern, blazing-fast dual-pane terminal file manager written in Rust. It combines the speed, efficiency, and dual-pane workflow of classic file managers (Total Commander, Double Commander, Midnight Commander) with an async architecture, Lua plugin system, and rich media preview capabilities.
upstream-relation: I am the author and maintainer of the project.
supported-category: terminal emulators, multiplexers and shells
reasoning: che-fm is an enhanced dual-pane terminal file manager based on yazi. Like yazi, its fundamental functionality is to manage arbitrary files across the entire system (not just $HOME or removable-media) and launch user-configured host utilities ($EDITOR, vim, nvim, openers, and shell scripts). It shares the identical architecture and
requirements that led to classic confinement being approved for yazi.
I understand that strict confinement is generally preferred over classic.
I’ve tried the existing interfaces to make the snap to work under strict confinement.
These two do not match, the category is for things like tmux, screen or even something like xterm but not covering file managers or any other applications running inside a terminal
Well, that was apparently a special case of a Canonical employee asking for it (and it was based on the premise that the person is a long standing contributor to the OS itself already (who could as well have uploaded the package as a deb to the distribution instead)).
Even after the discussion in the above request took place there was no “file manager” category added to the list of supported categories, but you can indeed hope for an architect to override it…
In this case, @ogra is correct, the mentioned request for Yazi was approved due to the specified, trusted, context it was published under. Unfortunately, as this project is a much younger fork from a new publisher, fitting in a supported category is a hard requirement for classic. As such, I do not believe che-fm meets the requirements for classic at this time.